From baggins at pld-linux.org  Sat Jan  1 09:55:29 2022
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sat, 1 Jan 2022 09:55:29 +0100
Subject: PLD Th 2021 snapshot released
Message-ID: <YdAXAalW//XKS6ZJ@starbug.lan>

2021 snapshot of PLD/Linux Th has been released.
It is available on ftp://ftp.pld-linux.org/dists/th/2021/PLD/ and as poldek sources th-2021.

The main highlights of this release are:

    kernels 5.15.12, 5.10.89, 5.4.169, 4.19.223, 4.14.260, 4.9.295 and 4.4.297 (4.4 and 4.9 have vserver enabled)
    RPM 4.16.1.3
    OpenSSL 3.0.1
    GCC 11.2.0
    LLVM 13.0.0
    glibc 2.34
    GNOME 41
    KDE5 5.89 / 21.12
    MATE Desktop Environment 1.26

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From baggins at pld-linux.org  Sat Jan  1 23:41:21 2022
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sat, 1 Jan 2022 23:41:21 +0100
Subject: Update on PLD Th snapshots
Message-ID: <YdDYkeZhYD+GSUx+@tachikoma.lan>

Hi,

I'm going to delete old snapshots from ftp.

By old I mean older than 3 years (2012-2018).

There is no value in keepeing them, and the promise was that we keep
the last 3 years worth.

If you need the old packages, you have time till the end of January 2022
to get them. After that everything older than 2018 will be deleted,

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From glen at pld-linux.org  Tue Jan  4 09:35:54 2022
From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=)
Date: Tue, 4 Jan 2022 10:35:54 +0200
Subject: [packages/greetd] include explicit target during install on x32
In-Reply-To: <fdd1f34fd3fc3d656d911259d6bf45d156673813_refs_heads_master@pld-linux.org>
References: <2f148bcb6ea73c4a80f4bf4c545b831a24c98548_refs_heads_master@pld-linux.org>
 <fdd1f34fd3fc3d656d911259d6bf45d156673813_refs_heads_master@pld-linux.org>
Message-ID: <720e788d-403d-38d0-ce83-72ad18f963e2@pld-linux.org>


On 04.01.2022 01:28, atler wrote:
> commit fdd1f34fd3fc3d656d911259d6bf45d156673813
> Author: Jan Palus <atler at pld-linux.org>
> Date:   Tue Jan 4 00:27:35 2022 +0100
>
>      include explicit target during install on x32
>
>   greetd.spec | 8 +++++++-
>   1 file changed, 7 insertions(+), 1 deletion(-)
> ---
> diff --git a/greetd.spec b/greetd.spec
> index 50b039e..e214165 100644
> --- a/greetd.spec
> +++ b/greetd.spec
> @@ -29,6 +29,12 @@ Requires:	greetd(greeter)
>   Provides:	user(greetd-greeter)
>   BuildRoot:	%{tmpdir}/%{name}-%{version}-root-%(id -u -n)
>   
> +%ifarch x32
> +%define		cargo_outdir	target/x86_64-unknown-linux-gnux32
> +%else
> +%define		cargo_outdir	target
> +%endif


maybe instead update macros to have symmetric output dir for all targets?



 ??????? --target <TRIPLE>...???????? Build for the target triple
 ??????? --target-dir <DIRECTORY>???? Directory for all generated artifacts





From atler at pld-linux.org  Wed Jan  5 19:22:23 2022
From: atler at pld-linux.org (Jan Palus)
Date: Wed, 5 Jan 2022 19:22:23 +0100
Subject: [packages/perl-IO-Socket-SSL] Rel 2; use system default ssl
 version and cipher list (from fc).
In-Reply-To: <d393768d64437bb1a9054fb07de0cb32f7395a2d_refs_heads_master@pld-linux.org>
References: <128e916df21fff0a7d8c2619a78786b6a8b0a7f1_refs_heads_master@pld-linux.org>
 <d393768d64437bb1a9054fb07de0cb32f7395a2d_refs_heads_master@pld-linux.org>
Message-ID: <20220105182223.kqurtvkpizmblnzj@pine>

On 16.12.2021 13:41, arekm wrote:
> commit d393768d64437bb1a9054fb07de0cb32f7395a2d
> Author: Arkadiusz Mi?kiewicz <arekm at maven.pl>
> Date:   Thu Dec 16 13:40:41 2021 +0100
> 
>     Rel 2; use system default ssl version and cipher list (from fc).
> 
...
> diff --git a/IO-Socket-SSL-2.068-use-system-default-cipher-list.patch b/IO-Socket-SSL-2.068-use-system-default-cipher-list.patch
> new file mode 100644
> index 0000000..800ab64
> --- /dev/null
> +++ b/IO-Socket-SSL-2.068-use-system-default-cipher-list.patch
> @@ -0,0 +1,101 @@
> +--- lib/IO/Socket/SSL.pm
> ++++ lib/IO/Socket/SSL.pm
> +@@ -202,77 +202,17 @@ my %DEFAULT_SSL_ARGS = (
> +     SSL_npn_protocols => undef,    # meaning depends whether on server or client side
> +     SSL_alpn_protocols => undef,   # list of protocols we'll accept/send, for example ['http/1.1','spdy/3.1']
> + 
> +-    # https://wiki.mozilla.org/Security/Server_Side_TLS, 2019/03/05
> +-    # "Old backward compatibility" for best compatibility
> +-    # .. "Most ciphers that are not clearly broken and dangerous to use are supported"
> +-    # slightly reordered to prefer AES since it is cheaper when hardware accelerated
> +-    SSL_cipher_list => 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:DES-CBC3-SHA:HIGH:SEED:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!RSAPSK:!aDH:!aECDH:!EDH-DSS-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA:!SRP',
> ++    # Use system-wide default cipher list to support use of system-wide
> ++    # crypto policy (#1076390, #1127577, CPAN RT#97816)
> ++    # https://fedoraproject.org/wiki/Changes/CryptoPolicy
> ++    SSL_cipher_list => 'PROFILE=SYSTEM',

Where is this PROFILE SYSTEM defined in PLD? With this patch ddclient
started to fail on every https call:

Failed to set SSL cipher list error:0A0000B9:SSL routines::no cipher match


From arekm at maven.pl  Wed Jan  5 20:35:03 2022
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Wed, 5 Jan 2022 20:35:03 +0100
Subject: [packages/perl-IO-Socket-SSL] Rel 2; use system default ssl
 version and cipher list (from fc).
In-Reply-To: <20220105182223.kqurtvkpizmblnzj@pine>
References: <128e916df21fff0a7d8c2619a78786b6a8b0a7f1_refs_heads_master@pld-linux.org>
 <d393768d64437bb1a9054fb07de0cb32f7395a2d_refs_heads_master@pld-linux.org>
 <20220105182223.kqurtvkpizmblnzj@pine>
Message-ID: <5caa65b7-f406-ea03-c69c-c8834aed7f61@maven.pl>

On 05.01.2022 19:22, Jan Palus wrote:

>> ++    # Use system-wide default cipher list to support use of system-wide
>> ++    # crypto policy (#1076390, #1127577, CPAN RT#97816)
>> ++    # https://fedoraproject.org/wiki/Changes/CryptoPolicy
>> ++    SSL_cipher_list => 'PROFILE=SYSTEM',
> 
> Where is this PROFILE SYSTEM defined in PLD? With this patch ddclient
> started to fail on every https call:
> 
> Failed to set SSL cipher list error:0A0000B9:SSL routines::no cipher match

It's some fedora thing. I guess we should just use system default (not
sure how to tell that there).

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From atler at pld-linux.org  Sat Jan  8 11:09:24 2022
From: atler at pld-linux.org (Jan Palus)
Date: Sat, 8 Jan 2022 11:09:24 +0100
Subject: PLD Th 2021 snapshot released
In-Reply-To: <YdAXAalW//XKS6ZJ@starbug.lan>
References: <YdAXAalW//XKS6ZJ@starbug.lan>
Message-ID: <20220108100924.sfikd4qzs46fcsne@pine>

On 01.01.2022 09:55, Jan R?korajski wrote:
> 2021 snapshot of PLD/Linux Th has been released.

On a related note, perhaps it would be good to resurrect pld-announce
and start posting announcements like this one to dedicated mailing list
(with cc to devel/users of course)?


From drmarwat at gmail.com  Sat Jan  8 18:04:48 2022
From: drmarwat at gmail.com (Saleem Ceann Khan Marwat)
Date: Sat, 8 Jan 2022 22:04:48 +0500
Subject: PLD Th 2021 snapshot released
In-Reply-To: <20220108100924.sfikd4qzs46fcsne@pine>
References: <YdAXAalW//XKS6ZJ@starbug.lan>
 <20220108100924.sfikd4qzs46fcsne@pine>
Message-ID: <CAOV1EpG43y0wZkhZgJABoUNPJP6wfKL-eJRj=-zi6H_5+wuCSw@mail.gmail.com>

is a new rescue ISO released as well?

On Sat, Jan 8, 2022, 3:09 PM Jan Palus <atler at pld-linux.org> wrote:

> On 01.01.2022 09:55, Jan R?korajski wrote:
> > 2021 snapshot of PLD/Linux Th has been released.
>
> On a related note, perhaps it would be good to resurrect pld-announce
> and start posting announcements like this one to dedicated mailing list
> (with cc to devel/users of course)?
> _______________________________________________
> pld-devel-en mailing list
> pld-devel-en at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
>


From atler at pld-linux.org  Sat Jan  8 20:59:15 2022
From: atler at pld-linux.org (Jan Palus)
Date: Sat, 8 Jan 2022 20:59:15 +0100
Subject: freshness report not updating
Message-ID: <20220108195915.e6fibl6sjmmn5wf5@pine>

Report at http://ep09.pld-linux.org/~pldth/qa.php?q=freshness stopped
receiving updates despite timestamp claiming it was ran recently.
For example uriparser or libsigsegv are missing.


From baggins at pld-linux.org  Sun Jan  9 10:11:29 2022
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sun, 9 Jan 2022 10:11:29 +0100
Subject: freshness report not updating
In-Reply-To: <20220108195915.e6fibl6sjmmn5wf5@pine>
References: <20220108195915.e6fibl6sjmmn5wf5@pine>
Message-ID: <YdqmwSLRrVLW/Qnp@starbug.lan>

On Sat, 08 Jan 2022, Jan Palus wrote:

> Report at http://ep09.pld-linux.org/~pldth/qa.php?q=freshness stopped
> receiving updates despite timestamp claiming it was ran recently.
> For example uriparser or libsigsegv are missing.

Fixed.
Client repo desync.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From qboosh at pld-linux.org  Sun Jan 16 21:41:05 2022
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Sun, 16 Jan 2022 21:41:05 +0100
Subject: PLD mail/requests problems
Message-ID: <20220116204105.GA31583@stranger.qboosh.pl>

- distfiles fetch request don't seem to be handled (since a few days) or no
  mail report is sent (both for requester nor pld-commit list)

- I don't get any build logs since yesterday

- only some (http) build requests are handled (one per ? hours)


-- 
Jakub Bogusz    http://qboosh.pl/


From qboosh at pld-linux.org  Mon Jan 17 18:37:33 2022
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Mon, 17 Jan 2022 18:37:33 +0100
Subject: PLD mail/requests problems
In-Reply-To: <20220116204105.GA31583@stranger.qboosh.pl>
References: <20220116204105.GA31583@stranger.qboosh.pl>
Message-ID: <20220117173733.GA31655@mail>

On Sun, Jan 16, 2022 at 09:41:05PM +0100, Jakub Bogusz wrote:
> - distfiles fetch request don't seem to be handled (since a few days) or no
>   mail report is sent (both for requester nor pld-commit list)

It seems distfiles are not fetching anything new at all (both by git or
manual mail requests), and reports are not sent.

> - I don't get any build logs since yesterday
> 
> - only some (http) build requests are handled (one per ? hours)

This one seems partially solved: ignored requests fail because of
missing files on distfiles - but again, I don't get any mail reports
about failed build from src builder.


-- 
Jakub Bogusz    http://qboosh.pl/


From atler at pld-linux.org  Tue Jan 18 11:42:33 2022
From: atler at pld-linux.org (Jan Palus)
Date: Tue, 18 Jan 2022 11:42:33 +0100
Subject: qt4 broken on i686
In-Reply-To: <YR1u6OgNZ0H07bxm@tachikoma>
References: <YR1u6OgNZ0H07bxm@tachikoma>
Message-ID: <20220118104233.zlsxouylaycsdjov@pine.grzadka>

On 18.08.2021 22:34, Jan R?korajski wrote:
> New builds of qt4 on i686 exhibit crashes (ex. linguist in avogadro), or
> infinite looping (ex. meinproc4 in kde4-kig).
> 
> I'm running out of ideas[1] and time to troubleshoot this and would
> appreciate if anyone would be willing to try and figure out WTF is
> broken there.
> 
> [1] neither -O0, nor -std=gnu98 seem to do the trick, it could be a
> glibc 2.34 issue, but I don't have resources at hand to validate it.

Looks like kde4-kig is causing issues again. Could someone check what's
the binary name that's hanging and kill it? Perhaps it's something that
needs a rebuild with workaround since avogadro built just fine.


From j.rekorajski at gmail.com  Tue Jan 18 15:56:42 2022
From: j.rekorajski at gmail.com (=?UTF-8?Q?Jan_R=C4=99korajski?=)
Date: Tue, 18 Jan 2022 15:56:42 +0100
Subject: qt4 broken on i686
In-Reply-To: <20220118104233.zlsxouylaycsdjov@pine.grzadka>
References: <YR1u6OgNZ0H07bxm@tachikoma>
 <20220118104233.zlsxouylaycsdjov@pine.grzadka>
Message-ID: <CAKY5yHyd=icsc4DHz1J57nwBDSgqXOS2bcfjbsSsVbAw1DBzoQ@mail.gmail.com>

16652 builder+  20   0   59.2m  14.5m 99.34 0.036   1196:11 R
/usr/bin/meinproc4 --check --cache /tmp/B.helc_nsl/BUI+
16653 builder+  20   0   59.2m  14.4m 99.34 0.036   1196:10 R
/usr/bin/meinproc4 --stylesheet /usr/share/apps/ksgmlt+

meinproc4 is consistently hanging on i686 to the point I've been
disabling docs in kde4 packages.
Killed

On Tue, Jan 18, 2022 at 11:42 AM Jan Palus <atler at pld-linux.org> wrote:
>
> On 18.08.2021 22:34, Jan R?korajski wrote:
> > New builds of qt4 on i686 exhibit crashes (ex. linguist in avogadro), or
> > infinite looping (ex. meinproc4 in kde4-kig).
> >
> > I'm running out of ideas[1] and time to troubleshoot this and would
> > appreciate if anyone would be willing to try and figure out WTF is
> > broken there.
> >
> > [1] neither -O0, nor -std=gnu98 seem to do the trick, it could be a
> > glibc 2.34 issue, but I don't have resources at hand to validate it.
>
> Looks like kde4-kig is causing issues again. Could someone check what's
> the binary name that's hanging and kill it? Perhaps it's something that
> needs a rebuild with workaround since avogadro built just fine.
> _______________________________________________
> pld-devel-en mailing list
> pld-devel-en at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en



-- 
Jan R?korajski | SysAdm | PLD/Linux | http://www.pld-linux.org/
baggins<at>pld-linux.org


From arekm at maven.pl  Tue Jan 18 18:38:34 2022
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Tue, 18 Jan 2022 18:38:34 +0100
Subject: PLD mail/requests problems
In-Reply-To: <20220117173733.GA31655@mail>
References: <20220116204105.GA31583@stranger.qboosh.pl>
 <20220117173733.GA31655@mail>
Message-ID: <615d7dd6-44b6-5df3-a448-af4dedde1642@maven.pl>

On 17.01.2022 18:37, Jakub Bogusz wrote:
> On Sun, Jan 16, 2022 at 09:41:05PM +0100, Jakub Bogusz wrote:
>> - distfiles fetch request don't seem to be handled (since a few days) or no
>>   mail report is sent (both for requester nor pld-commit list)
> 
> It seems distfiles are not fetching anything new at all (both by git or
> manual mail requests), and reports are not sent.
> 
>> - I don't get any build logs since yesterday
>>
>> - only some (http) build requests are handled (one per ? hours)
> 
> This one seems partially solved: ignored requests fail because of
> missing files on distfiles - but again, I don't get any mail reports
> about failed build from src builder.

disk was fully filled on MX due to some spammers.

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From baggins at pld-linux.org  Tue Jan 18 19:25:16 2022
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Tue, 18 Jan 2022 19:25:16 +0100
Subject: PLD mail/requests problems
In-Reply-To: <615d7dd6-44b6-5df3-a448-af4dedde1642@maven.pl>
References: <20220116204105.GA31583@stranger.qboosh.pl>
 <20220117173733.GA31655@mail>
 <615d7dd6-44b6-5df3-a448-af4dedde1642@maven.pl>
Message-ID: <YecGDNIdTPS02YQw@starbug.lan>

On Tue, 18 Jan 2022, Arkadiusz Mi?kiewicz via pld-devel-en wrote:

> On 17.01.2022 18:37, Jakub Bogusz wrote:
> > On Sun, Jan 16, 2022 at 09:41:05PM +0100, Jakub Bogusz wrote:
> >> - distfiles fetch request don't seem to be handled (since a few days) or no
> >>   mail report is sent (both for requester nor pld-commit list)
> > 
> > It seems distfiles are not fetching anything new at all (both by git or
> > manual mail requests), and reports are not sent.
> > 
> >> - I don't get any build logs since yesterday
> >>
> >> - only some (http) build requests are handled (one per ? hours)
> > 
> > This one seems partially solved: ignored requests fail because of
> > missing files on distfiles - but again, I don't get any mail reports
> > about failed build from src builder.
> 
> disk was fully filled on MX due to some spammers.

There is still something wrong. I'm not getting any response from
failed(?) requests.

Ex. trying to build the kernel from head does not yield any response, not
even build failure. Like the build request went to /dev/null.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From qboosh at pld-linux.org  Tue Jan 18 20:16:27 2022
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Tue, 18 Jan 2022 20:16:27 +0100
Subject: PLD mail/requests problems
In-Reply-To: <YecGDNIdTPS02YQw@starbug.lan>
References: <20220116204105.GA31583@stranger.qboosh.pl>
 <20220117173733.GA31655@mail> <615d7dd6-44b6-5df3-a448-af4dedde1642@maven.pl>
 <YecGDNIdTPS02YQw@starbug.lan>
Message-ID: <20220118191627.GA10278@mail>

On Tue, Jan 18, 2022 at 07:25:16PM +0100, Jan R?korajski wrote:
> On Tue, 18 Jan 2022, Arkadiusz Mi?kiewicz via pld-devel-en wrote:
> 
> > On 17.01.2022 18:37, Jakub Bogusz wrote:
> > > On Sun, Jan 16, 2022 at 09:41:05PM +0100, Jakub Bogusz wrote:
> > >> - distfiles fetch request don't seem to be handled (since a few days) or no
> > >>   mail report is sent (both for requester nor pld-commit list)
> > > 
> > > It seems distfiles are not fetching anything new at all (both by git or
> > > manual mail requests), and reports are not sent.
> > > 
> > >> - I don't get any build logs since yesterday
> > >>
> > >> - only some (http) build requests are handled (one per ? hours)
> > > 
> > > This one seems partially solved: ignored requests fail because of
> > > missing files on distfiles - but again, I don't get any mail reports
> > > about failed build from src builder.
> > 
> > disk was fully filled on MX due to some spammers.
> 
> There is still something wrong. I'm not getting any response from
> failed(?) requests.
> 
> Ex. trying to build the kernel from head does not yield any response, not
> even build failure. Like the build request went to /dev/null.

404 Not Found (/distfiles/by-md5/d/5/d571392436365678b420e4dece216514/patch-5.16.1.xz)

(I've just sent fetchsrc request for kernel.spec to fix it)

But why src builder doesn't send failure notifications?


-- 
Jakub Bogusz    http://qboosh.pl/


From arekm at maven.pl  Tue Jan 18 21:42:38 2022
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Tue, 18 Jan 2022 21:42:38 +0100
Subject: PLD mail/requests problems
In-Reply-To: <20220118191627.GA10278@mail>
References: <20220116204105.GA31583@stranger.qboosh.pl>
 <20220117173733.GA31655@mail> <615d7dd6-44b6-5df3-a448-af4dedde1642@maven.pl>
 <YecGDNIdTPS02YQw@starbug.lan> <20220118191627.GA10278@mail>
Message-ID: <95112b50-be12-0b69-ae70-a31184d66a44@maven.pl>

On 18.01.2022 20:16, Jakub Bogusz wrote:
> On Tue, Jan 18, 2022 at 07:25:16PM +0100, Jan R?korajski wrote:
>> On Tue, 18 Jan 2022, Arkadiusz Mi?kiewicz via pld-devel-en wrote:
>>
>>> On 17.01.2022 18:37, Jakub Bogusz wrote:
>>>> On Sun, Jan 16, 2022 at 09:41:05PM +0100, Jakub Bogusz wrote:
>>>>> - distfiles fetch request don't seem to be handled (since a few days) or no
>>>>>   mail report is sent (both for requester nor pld-commit list)
>>>>
>>>> It seems distfiles are not fetching anything new at all (both by git or
>>>> manual mail requests), and reports are not sent.
>>>>
>>>>> - I don't get any build logs since yesterday
>>>>>
>>>>> - only some (http) build requests are handled (one per ? hours)
>>>>
>>>> This one seems partially solved: ignored requests fail because of
>>>> missing files on distfiles - but again, I don't get any mail reports
>>>> about failed build from src builder.
>>>
>>> disk was fully filled on MX due to some spammers.
>>
>> There is still something wrong. I'm not getting any response from
>> failed(?) requests.
>>
>> Ex. trying to build the kernel from head does not yield any response, not
>> even build failure. Like the build request went to /dev/null.
> 
> 404 Not Found (/distfiles/by-md5/d/5/d571392436365678b420e4dece216514/patch-5.16.1.xz)
> 
> (I've just sent fetchsrc request for kernel.spec to fix it)
> 
> But why src builder doesn't send failure notifications?
> 
> 

To nie to?

Jan 18 20:11:30 b postfix/cleanup[22147]: CD0C749BA03:
message-id=<16169.1642533305 at distfiles.pld-linux.org>
Jan 18 20:11:30 b postfix/local[22186]: B1EFA49BA01:
to=<qboosh at pld-linux.org>, relay=local, delay=3.3, delays=3.3/0/0/0.03,
dsn=2.0.0, status=sent (forwarded as CD0C749BA03)
Jan 18 20:11:30 b postfix/qmgr[20373]: CD0C749BA03:
from=<dfadm at cvs.pld-linux.org>, size=1215, nrcpt=1 (queue active)
Jan 18 20:11:31 b postfix/smtp[30218]: CD0C749BA03: to=<pld at qboosh.pl>,
orig_to=<qboosh at pld-linux.org>, relay=mail.qboosh.pl[217.73.31.61]:25,
delay=0.59, delays=0.03/0.06/0.36/0.14, dsn=2.0.0, status=sent (250
2.0.0 Ok: queued as D20EB1A26DA9)
Jan 18 20:11:31 b postfix/qmgr[20373]: CD0C749BA03: removed

(data te??by?a rozjechana o kilka minut wstecz na mxie)

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From baggins at pld-linux.org  Sun Jan 23 23:17:19 2022
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sun, 23 Jan 2022 23:17:19 +0100
Subject: cargo(?)/rust(?) broken on x32
Message-ID: <Ye3T79VxUQS/UMI/@tachikoma.lan>

cargo does not pass --target down to rust on x32 again.

http://buildlogs.pld-linux.org//index.php?dist=th&arch=x32&ok=0&name=dssim2&id=2684320f-141d-452b-8608-4959b7d844e0&action=tail

Could it be related to http://git.pld-linux.org/gitweb.cgi?p=packages/rust.git;a=commit;h=62473c9552f86f55f6f591df14ca1755ecdb5cd6
or just new rust breaking cross compilation again for the sake of it?

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From atler at pld-linux.org  Mon Jan 24 12:10:33 2022
From: atler at pld-linux.org (Jan Palus)
Date: Mon, 24 Jan 2022 12:10:33 +0100
Subject: cargo(?)/rust(?) broken on x32
In-Reply-To: <Ye3T79VxUQS/UMI/@tachikoma.lan>
References: <Ye3T79VxUQS/UMI/@tachikoma.lan>
Message-ID: <20220124110851.c4bkfrcm52lt26zv@pine>

On 23.01.2022 23:17, Jan R?korajski wrote:
> cargo does not pass --target down to rust on x32 again.
> 
> http://buildlogs.pld-linux.org//index.php?dist=th&arch=x32&ok=0&name=dssim2&id=2684320f-141d-452b-8608-4959b7d844e0&action=tail
> 
> Could it be related to http://git.pld-linux.org/gitweb.cgi?p=packages/rust.git;a=commit;h=62473c9552f86f55f6f591df14ca1755ecdb5cd6
> or just new rust breaking cross compilation again for the sake of it?

Mentioned commit should result in exactly same spec file after parsing
as before for all archs but armv7hnl. Actually rust on x32 predated
it anyway at the time of mentioned build.

target is passed down correctly:
- rustc invocations that lack it are for build scripts that are built
  for host
- other rustc invocations have target passed down correctly

Objects that are built incorrectly are not coming from rust sources,
these are compiled from assembler files which seem to be simply
miscompiled for x32. Fixed on master now.


From baggins at pld-linux.org  Mon Jan 24 23:45:18 2022
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Mon, 24 Jan 2022 23:45:18 +0100
Subject: cargo(?)/rust(?) broken on x32
In-Reply-To: <20220124110851.c4bkfrcm52lt26zv@pine>
References: <Ye3T79VxUQS/UMI/@tachikoma.lan>
 <20220124110851.c4bkfrcm52lt26zv@pine>
Message-ID: <Ye8r/mB1dywrTHIO@tachikoma.lan>

On Mon, 24 Jan 2022, Jan Palus wrote:

> On 23.01.2022 23:17, Jan R?korajski wrote:
> > cargo does not pass --target down to rust on x32 again.
> > 
> > http://buildlogs.pld-linux.org//index.php?dist=th&arch=x32&ok=0&name=dssim2&id=2684320f-141d-452b-8608-4959b7d844e0&action=tail
> > 
> > Could it be related to http://git.pld-linux.org/gitweb.cgi?p=packages/rust.git;a=commit;h=62473c9552f86f55f6f591df14ca1755ecdb5cd6
> > or just new rust breaking cross compilation again for the sake of it?
> 
> Mentioned commit should result in exactly same spec file after parsing
> as before for all archs but armv7hnl. Actually rust on x32 predated
> it anyway at the time of mentioned build.
> 
> target is passed down correctly:
> - rustc invocations that lack it are for build scripts that are built
>   for host
> - other rustc invocations have target passed down correctly
> 
> Objects that are built incorrectly are not coming from rust sources,
> these are compiled from assembler files which seem to be simply
> miscompiled for x32. Fixed on master now.

Thanks a lot.

I wonder what's wrong with my local setup. I have x32 builder
environment with the same packages installed, yet cargo tries
to build 64bit stuff in x32 environment...

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From arekm at maven.pl  Wed Jan 26 15:23:42 2022
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Wed, 26 Jan 2022 15:23:42 +0100
Subject: lwn.net 3 years subscription and missing Szymon Siwek <sls@pld-...>
Message-ID: <f697c352-af60-48ed-6b23-5e03e8a9045a@maven.pl>

Hello.

Does anyone have contact with Szymon Siwek <sls at pld-....> ?

Our lwn.net subscription is going to expire and we want to renew it. He
was participating but it seems that he doesn't use it since 2019.

In case we won't be able to contact him we are looking for one person
who is interested in 3 years lwn.net subcription for ~148PLN (1$/month).

Deadline is tomorrow.

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From baggins at pld-linux.org  Thu Jan 27 09:18:43 2022
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Thu, 27 Jan 2022 09:18:43 +0100
Subject: lwn.net 3 years subscription and missing Szymon Siwek
 <sls@pld-...>
In-Reply-To: <f697c352-af60-48ed-6b23-5e03e8a9045a@maven.pl>
References: <f697c352-af60-48ed-6b23-5e03e8a9045a@maven.pl>
Message-ID: <YfJVYxAdAgcFlWFn@starbug.lan>

On Wed, 26 Jan 2022, Arkadiusz Mi?kiewicz via pld-devel-en wrote:

> Hello.
> 
> Does anyone have contact with Szymon Siwek <sls at pld-....> ?
> 
> Our lwn.net subscription is going to expire and we want to renew it. He
> was participating but it seems that he doesn't use it since 2019.
> 
> In case we won't be able to contact him we are looking for one person
> who is interested in 3 years lwn.net subcription for ~148PLN (1$/month).
> 
> Deadline is tomorrow.

Just in case, I'm interested.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From krzysztof at mrozowicz.eu  Thu Jan 27 10:06:16 2022
From: krzysztof at mrozowicz.eu (Krzysztof Mrozowicz)
Date: Thu, 27 Jan 2022 09:06:16 +0000
Subject: lwn.net 3 years subscription and missing Szymon Siwek
 <sls@pld-...>
In-Reply-To: <YfJVYxAdAgcFlWFn@starbug.lan>
References: <f697c352-af60-48ed-6b23-5e03e8a9045a@maven.pl>
 <YfJVYxAdAgcFlWFn@starbug.lan>
Message-ID: <20220127090616.0d8e2058@oko>

Dnia 2022-01-27, o godz. 09:18:43
Jan R?korajski <baggins at pld-linux.org> napisa?(a):

> On Wed, 26 Jan 2022, Arkadiusz Mi?kiewicz via pld-devel-en wrote:
> 
> > Hello.
> > 
> > Does anyone have contact with Szymon Siwek <sls at pld-....> ?
> > 
> > Our lwn.net subscription is going to expire and we want to renew
> > it. He was participating but it seems that he doesn't use it since
> > 2019.
> > 
> > In case we won't be able to contact him we are looking for one
> > person who is interested in 3 years lwn.net subcription for ~148PLN
> > (1$/month).
> > 
> > Deadline is tomorrow.  
> 
> Just in case, I'm interested.
> 
I don't mind to take it either.


-- 
Krzysiek