From atler at pld-linux.org Wed May 14 20:06:17 2025 From: atler at pld-linux.org (Jan Palus) Date: Wed, 14 May 2025 20:06:17 +0200 Subject: git: No space left on device Message-ID: pushing to remote fails with: Writing objects: 100% (3/3), 399 bytes | 16.00 KiB/s, done. Total 3 (delta 1), reused 0 (delta 0), pack-reused 0 (from 0) remote: fatal: write failure on standard output: No space left on device remote: close log failed: No space left on device remote: error: hook declined to update refs/heads/master From atler at pld-linux.org Fri May 16 12:27:34 2025 From: atler at pld-linux.org (Jan Palus) Date: Fri, 16 May 2025 12:27:34 +0200 Subject: SSE2 required for i686 targets in rust >= 1.86 Message-ID: Starting with rust 1.86 binaries built for i686 (including rustc itself) require SSE2 instructions (refer to release notes for rationale). The question is how we'd like to handle this: 1. Change target to i586-unknown-linux-gnu for i686. i586-unknown-linux-gnu is "Tier 2 platform without host tools" so we'd need to build both i686-unknown-linux-gnu for tools which would require SSE2 as well as i586-unknown-linux-gnu. 2. Put "Requires: cpuinfo(sse2)" possibly through some %rust_req macro in every package utilizing rust 3. Change our baseline for i686 so SSE2 is mandatory and do nothing. Any other ideas are welcome. From atler at pld-linux.org Sun May 25 15:44:32 2025 From: atler at pld-linux.org (Jan Palus) Date: Sun, 25 May 2025 15:44:32 +0200 Subject: [packages/nodejs] - 22.16.0 fails during python3-furo build for me In-Reply-To: References: <941e51b8400243b6924379c0ab65f589bba768dd_refs_heads_master@pld-linux.org> Message-ID: On 25.05.2025 14:00, qboosh wrote: > commit ea33a400c9375558d4233848e66c52679884b302 > Author: Jakub Bogusz > Date: Sun May 25 13:12:38 2025 +0200 > > - 22.16.0 fails during python3-furo build for me > > nodejs.spec | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > --- > diff --git a/nodejs.spec b/nodejs.spec > index 3a5477a..84a01ee 100644 > --- a/nodejs.spec > +++ b/nodejs.spec > @@ -30,7 +30,8 @@ Name: nodejs > # Maintenance start: October 2025 > # Maintenance end: April 2027 > Version: 22.16.0 > -Release: 1 > +# FIXME: with 22.16.0 yarn (1.22.10 and 1.22.22 tested) hangs during python3-furo build; nodejs 22.15.1 works > +Release: 0.1 > License: BSD and MIT and Apache v2.0 and GPL v3 > Group: Development/Languages > Source0: https://nodejs.org/download/release/latest-v22.x/node-v%{version}.tar.xz Wanted to give it a shot but it builds fine for me with nodejs 22.16.0, yarn both 1.22.10 and 1.22.22 and on all archs I have access to (x86_64/aarch64/armv6/armv7). Mind sharing strace? Although not sure if would contain anything useful. From arekm at maven.pl Mon May 26 12:09:39 2025 From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=C5=9Bkiewicz?=) Date: Mon, 26 May 2025 12:09:39 +0200 Subject: [packages/nodejs] - 22.16.0 fails during python3-furo build for me In-Reply-To: References: <941e51b8400243b6924379c0ab65f589bba768dd_refs_heads_master@pld-linux.org> Message-ID: On 25/05/2025 15:44, Jan Palus wrote: >> Version: 22.16.0 >> -Release: 1 >> +# FIXME: with 22.16.0 yarn (1.22.10 and 1.22.22 tested) hangs during python3-furo build; nodejs 22.15.1 works >> +Release: 0.1 >> License: BSD and MIT and Apache v2.0 and GPL v3 >> Group: Development/Languages >> Source0: https://nodejs.org/download/release/latest-v22.x/node-v%{version}.tar.xz > > Wanted to give it a shot but it builds fine for me with nodejs 22.16.0, > yarn both 1.22.10 and 1.22.22 and on all archs I have access to > (x86_64/aarch64/armv6/armv7). Mind sharing strace? Although not sure if > would contain anything useful. qt5-qtwebengine-5.15.18-2.src.rpm got stuck on nodejs, too: https://ixion.pld-linux.org/~arekm/nodejs-20250526-1.txt -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) From atler at pld-linux.org Mon May 26 14:41:23 2025 From: atler at pld-linux.org (Jan Palus) Date: Mon, 26 May 2025 14:41:23 +0200 Subject: [packages/nodejs] - 22.16.0 fails during python3-furo build for me In-Reply-To: References: <941e51b8400243b6924379c0ab65f589bba768dd_refs_heads_master@pld-linux.org>

Message-ID: On 26.05.2025 12:09, Arkadiusz Mi?kiewicz via pld-devel-en wrote: > On 25/05/2025 15:44, Jan Palus wrote: > > > > Version: 22.16.0 > > > -Release: 1 > > > +# FIXME: with 22.16.0 yarn (1.22.10 and 1.22.22 tested) hangs during python3-furo build; nodejs 22.15.1 works > > > +Release: 0.1 > > > License: BSD and MIT and Apache v2.0 and GPL v3 > > > Group: Development/Languages > > > Source0: https://nodejs.org/download/release/latest-v22.x/node-v%{version}.tar.xz > > > > Wanted to give it a shot but it builds fine for me with nodejs 22.16.0, > > yarn both 1.22.10 and 1.22.22 and on all archs I have access to > > (x86_64/aarch64/armv6/armv7). Mind sharing strace? Although not sure if > > would contain anything useful. > > > qt5-qtwebengine-5.15.18-2.src.rpm got stuck on nodejs, too: > > https://ixion.pld-linux.org/~arekm/nodejs-20250526-1.txt That's a different problem occurring on regular basis with previous nodejs versions too. Thread creation under unknown circumstances (but seems dependant on number of parallel jobs) returns -EAGAIN and nodejs cannot recover. To workaround the issue I send webengine jobs limited to 8 parallel jobs but as you can see I sometimes forget to do that. When it comes to qtwebengine I'd be more interested in knowing why i686 buildlogs are missing (I got some really unexpected errors in mail from builder) From qboosh at pld-linux.org Mon May 26 18:24:56 2025 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Mon, 26 May 2025 18:24:56 +0200 Subject: [packages/nodejs] - 22.16.0 fails during python3-furo build for me In-Reply-To: References: <941e51b8400243b6924379c0ab65f589bba768dd_refs_heads_master@pld-linux.org>

Message-ID: <20250526162456.GA32027@mail> On Mon, May 26, 2025 at 12:09:39PM +0200, Arkadiusz Mi?kiewicz via pld-devel-en wrote: > On 25/05/2025 15:44, Jan Palus wrote: > > >> Version: 22.16.0 > >>-Release: 1 > >>+# FIXME: with 22.16.0 yarn (1.22.10 and 1.22.22 tested) hangs during > >>python3-furo build; nodejs 22.15.1 works > >>+Release: 0.1 > >> License: BSD and MIT and Apache v2.0 and GPL v3 > >> Group: Development/Languages > >> Source0: > >> https://nodejs.org/download/release/latest-v22.x/node-v%{version}.tar.xz > > > >Wanted to give it a shot but it builds fine for me with nodejs 22.16.0, > >yarn both 1.22.10 and 1.22.22 and on all archs I have access to > >(x86_64/aarch64/armv6/armv7). Mind sharing strace? Although not sure if > >would contain anything useful. > > > qt5-qtwebengine-5.15.18-2.src.rpm got stuck on nodejs, too: > > https://ixion.pld-linux.org/~arekm/nodejs-20250526-1.txt That's different issue. In my case nodejs is in some livelock or busy waiting state (3 or 4 threads eating CPU in v8 structure methods, other waiting on different epoll, mutex or semaphore calls). -- Jakub Bogusz http://qboosh.pl/ From qboosh at pld-linux.org Fri May 30 18:14:53 2025 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Fri, 30 May 2025 18:14:53 +0200 Subject: ENOSPC on ftp [Re: [all] builder queue problem] In-Reply-To: References: Message-ID: <20250530161453.GA6756@mail> On Fri, May 30, 2025 at 04:06:18PM +0000, PLD all builder wrote: > there were problems sending files from queue /home/users/builderth/pld-builder.new/spool/ftp: > problems: > [src: /home/users/builderth/pld-builder.new/spool/ftp/5b7d29e8-3047-499b-b9ce-632dbc4f6d3b] > > sending incremental file list > 5b7d29e8-3047-499b-b9ce-632dbc4f6d3b > rsync: [receiver] mkstemp "/home/pld/admins/th/ftp/.incoming/i686/.ka6-yakuake-debuginfo-25.04.1-1.i686.rpm.imyJo4" failed: No space left on device (28) [...] -- Jakub Bogusz http://qboosh.pl/