#archlinux-ports | Logs for 2025-09-19
Back
[00:55:30] -!- marmis has quit [Quit: Bye!]
[00:56:39] -!- marmis has joined #archlinux-ports
[02:47:35] <bschnei> https://gitlab.archlinux.org
[02:47:36] <phrik> Title: Packages fail to build without LSE support (#6) · Issues · Arch Linux / Ports / AArch64 / project-management · GitLab (at gitlab.archlinux.org)
[02:49:17] <bschnei> gromit: thanks again for setting up this space!
[06:37:03] <Solskogen> bschnei: you can add chromium to that list as well
[08:04:31] <jelle> qt-webengine == chromium
[08:21:50] <Solskogen> I also have a feeling that the latest firefox might be an issue, but someone has to check that
[08:22:06] <Solskogen> (ld.lld was using about 60GB of memory)
[08:26:28] -!- gromit has quit [Read error: Connection reset by peer]
[08:26:46] -!- gromit has joined #archlinux-ports
[11:18:49] -!- gromit has quit [Ping timeout: 256 seconds]
[11:18:59] -!- gromit has joined #archlinux-ports
[11:28:36] -!- bschnei has quit [Ping timeout: 244 seconds]
[11:28:37] -!- marmis has quit [Ping timeout: 244 seconds]
[11:28:37] -!- nl6720 has quit [Ping timeout: 244 seconds]
[11:29:04] -!- nl6720 has joined #archlinux-ports
[11:34:57] <DrZee> question.... how long are new PKGs in -testing befor the are moved out of testing.... and how is it decided to move PKGs out? no bug reports for 24h? pull requests?
[11:35:15] -!- gromit has quit [Ping timeout: 256 seconds]
[11:35:26] -!- gromit has joined #archlinux-ports
[11:35:53] -!- Solskogen has quit [*.net *.split]
[11:36:08] <jelle> it depends
[11:36:31] <jelle> there are no set rules
[11:36:47] <tpkessler|M> DrZee: all depends on the complexity of the package/rebuild. A few days for bigger rebuilds, a few hours and sign-offs for critical fixes.
[11:37:27] <Antiz> DrZee: We have a "testing team" (quoted because it's not an actual staff role) which "vets" for packages in testing by given their "approval" (called "sign offs") that they tested the package from testing and that it works.
[11:37:43] <Antiz> The process is described here: https://wiki.archlinux.org
[11:37:44] <phrik> Title: Arch Testing Team - ArchWiki (at wiki.archlinux.org)
[11:37:44] <DrZee> like the issue with systemd 258 and how it breaks arch-chroot ... so that would move quickly I guess
[11:38:07] <Antiz> Packages in [core] **have to** go to testing first and needs at least 2 signoffs before being moved to stable
[11:38:17] <Antiz> There are no strict rules for the rest though
[11:38:44] -!- bschnei has joined #archlinux-ports
[11:38:50] <Antiz> Like they don't necessarilly needs 2 signoffs to be moved, nor they don't necessarilly need to enter the testing repo at all. It's all under the discretion of the package maintainer.
[11:39:18] <Antiz> s/given/giving
[11:40:20] -!- Solskogen has joined #archlinux-ports
[11:40:33] <Antiz> So systemd entered testing and got at least 2 sign offs by tester. But the arch-chroot issue may have slipped off I guess
[11:40:52] <DrZee> ok ... I spend the last 12 hours wondering why my build pipeline was failing until I this morning tracked it to systemd 258-1 ... I have tested 258-2 from testing and now pacstrap arch-chroot work fine again
[11:40:59] Solskogen is now known as Guest5403
[11:41:37] <Antiz> Well systemd 258-2 will enter the stable repo once it has 2 signoffs
[11:41:57] <DrZee> guess it's a mandatory test now to test systemd releases against arch-chroot ....
[11:42:16] <Antiz> Well, systemd is one of the difficult one
[11:42:26] <Antiz> difficult to test fully reliably that is
[11:42:50] <DrZee> lol ... that was the nicest thing I heard about systemd in a long time
[11:43:55] <Antiz> Well x) I mean... It basically have a hand on *mostly* everything. arch-chroot is far from being the only thing that can be impacted from it.
[11:44:27] <Antiz> It's a bit difficult to list and deeply test everything it can have an impact on. Fortunately the fix is there and 258-2 should enter [core] stable soon :D
[11:44:44] <Antiz> I'll give it a go right now and give it my signoff, so that's one out of the two required ;)
[11:45:40] Guest5403 is now known as Solskogen
[11:46:18] <Solskogen> it's in testing for aarch64 as well
[11:49:00] <DrZee> yeah I just tested it on aarch64 and everything is "fine" again ...
[11:54:31] <Antiz> I gave a test / signoff
[11:54:41] <Antiz> Hopefully that should speed things up :)
[11:58:09] <DrZee> no problem the next build for x86 images is not until the 1st October... but I was messing with aarch64 images builds and couldn't understand why the failed - eventually tested on x86 .... same error ....
[12:09:51] -!- drathir_tor has quit [Remote host closed the connection]
[12:54:35] -!- gromit has quit [Ping timeout: 256 seconds]
[12:55:13] -!- gromit has joined #archlinux-ports
[13:19:32] -!- rennod has quit [Remote host closed the connection]
[13:20:55] -!- rennod has joined #archlinux-ports
[13:41:29] -!- oliver-testing-i has joined #archlinux-ports
[13:44:06] -!- oliver-testing-i has quit [Client Quit]
[13:44:36] -!- oliver-testing-i has joined #archlinux-ports
[13:59:50] -!- oliver-testing-i has quit [Quit: leaving]
[16:27:42] -!- p71- has joined #archlinux-ports
[16:28:12] -!- p71 has quit [Ping timeout: 265 seconds]
[18:09:56] -!- moabeat has joined #archlinux-ports
[18:29:37] -!- Solskoge1 has joined #archlinux-ports
[18:52:04] -!- titus_livius has joined #archlinux-ports
[19:15:05] -!- wszqkzqk|M has quit [Server closed connection]
[19:15:13] -!- wszqkzqk|M has joined #archlinux-ports
[19:17:05] -!- archmatrix has quit [Server closed connection]
[19:17:26] -!- archmatrix has joined #archlinux-ports
[19:31:05] -!- phrik has quit [Server closed connection]
[19:31:15] -!- phrik has joined #archlinux-ports
[19:39:05] -!- orhun|M has quit [Server closed connection]
[19:39:15] -!- orhun|M has joined #archlinux-ports
[19:45:05] -!- qixiqaq|M has quit [Server closed connection]
[19:45:12] -!- qixiqaq|M has joined #archlinux-ports
[20:46:03] <Antiz> DrZee: New systemd is now in [core] ;)
[22:10:20] -!- titus_livius has joined #archlinux-ports