Summary: | sys-process/systemd-cron-2.3.4 - ERROR: sys-process/systemd-cron-2.3.4::gentoo failed (pretend phase), broken test for merged-usr | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Richard Freeman <rich0> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dilfridge, ionen, rich0, toralf |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
die.env emerge-history.txt etc.clang.tar.xz etc.portage.tar.xz logs.tar.xz qlist-info.txt sys-process:systemd-cron-2.3.4:20240407-153556.log |
Description
Toralf Förster
2024-04-07 16:07:15 UTC
Created attachment 889740 [details]
emerge-info.txt
Created attachment 889741 [details]
die.env
Created attachment 889742 [details]
emerge-history.txt
Created attachment 889743 [details]
etc.clang.tar.xz
Created attachment 889744 [details]
etc.portage.tar.xz
Created attachment 889745 [details]
logs.tar.xz
Created attachment 889746 [details]
qlist-info.txt
Created attachment 889747 [details]
sys-process:systemd-cron-2.3.4:20240407-153556.log
It is my understanding that the image is a valid 23.0 stage3 (merged-usr), right? tinderbox@mr-fox ~/run/23.0-20240407-113050/var/tmp/tb $ ls -l ~/run/23.0_desktop_plasma_systemd-20240406-051502/ total 20 lrwxrwxrwx 1 root root 7 Apr 1 01:17 bin -> usr/bin drwxr-xr-x 1 root root 48 Apr 7 02:41 boot drwxr-xr-x 1 root root 22 Apr 1 01:17 dev drwxr-xr-x 1 root root 2476 Apr 7 16:08 etc drwxr-xr-x 1 root root 18 Apr 6 05:16 home lrwxrwxrwx 1 root root 7 Apr 1 01:17 lib -> usr/lib lrwxrwxrwx 1 root root 9 Apr 1 01:17 lib64 -> usr/lib64 drwxr-xr-x 1 root root 0 Apr 1 01:17 media drwxr-xr-x 1 root root 4 Apr 6 05:15 mnt drwxr-xr-x 1 root root 156 Apr 7 14:48 opt drwxr-xr-x 1 root root 0 Apr 1 01:17 proc drwx------ 1 root root 126 Apr 7 08:43 root drwxr-xr-x 1 root root 0 Apr 1 01:17 run lrwxrwxrwx 1 root root 7 Apr 1 01:17 sbin -> usr/bin drwxr-xr-x 1 root root 0 Apr 6 05:38 srv drwxr-xr-x 1 root root 0 Apr 1 01:17 sys drwxrwxrwt 1 root root 0 Apr 6 05:38 tmp drwxr-xr-x 1 root root 122 Apr 1 01:18 usr drwxr-xr-x 1 root root 80 Apr 7 05:41 var run-parts belongs to debianutils, which recently got depcleaned in a lot of places. Not the best way to test for split/merged. fwiw it does depends on debianutils with USE=runparts, but can't rely on dependencies being installed during pkg_pretend so.. It'd probably be nicer to just mask the USE on split-usr profiles though, not that it's super straight forward because of the older profiles (e.g. base force split-usr, then 23.0 *and* features/merged-usr unforce it since features/split-usr is not used by older profiles that I can see). (In reply to Ionen Wolkens from comment #12) > It'd probably be nicer to just mask ... That is, unless the goal was to avoid having it happen without warning -- news item may have made more sense if that was the intend though. Not that I keep up with what been happening with systemd-cron. Looking at history this is at least the third way that testing for split-usr has been implemented - I haven't dug back enough to find where it was first tested (via checking symlink on /bin). An alternative might be to put IUSE=split-usr back in, then test: if use runparts && use split-usr ; then... (That is a little more similar to how systemd-9999 implements the check - this was the way systemd-cron did it, but when making it conditional on runparts it was switched to checking the path of run-parts, not catching the issue with pkg_pretend. I'm pretty confident I didn't think of that one on my own though I couldn't tell you where it came from.) Any preferences? Ok, if there are no objections I'll implement the IUSE=split-usr fix in a few days... Is there a compelling reason to not just depend on >=sys-apps/systemd-255[-split-usr(-)] and drop all the silly checks? (In reply to Sam James from comment #16) > Is there a compelling reason to not just depend on > >=sys-apps/systemd-255[-split-usr(-)] and drop all the silly checks? Very good point - the migration path for systemd itself makes sense, but at this point it is hard to imagine people are using systemd-cron and haven't made the migration... I'll make that change in a few days. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=641c536fe4afa656f34ebb656bf1e8bca8bd87bc commit 641c536fe4afa656f34ebb656bf1e8bca8bd87bc Author: Richard Freeman <rich0@gentoo.org> AuthorDate: 2024-04-16 15:14:12 +0000 Commit: Richard Freeman <rich0@gentoo.org> CommitDate: 2024-04-16 15:16:02 +0000 sys-process/systemd-cron: Require split-usr in deps and no longer die. Closes: https://bugs.gentoo.org/928893 Signed-off-by: Richard Freeman <rich0@gentoo.org> ...{systemd-cron-2.3.4.ebuild => systemd-cron-2.3.4-r1.ebuild} | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5674137a39abeaa635c087fec1019a6cbdc2d40b commit 5674137a39abeaa635c087fec1019a6cbdc2d40b Author: Sam James <sam@gentoo.org> AuthorDate: 2024-04-16 20:43:33 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-04-16 20:43:33 +0000 profiles: mask >=sys-process/systemd-cron-2.3.4-r1 on split-usr >=systemd-255 needs merged-usr. Bug: https://bugs.gentoo.org/928893 Signed-off-by: Sam James <sam@gentoo.org> profiles/features/merged-usr/package.mask | 3 ++- profiles/features/split-usr/package.mask | 3 ++- profiles/releases/17.0/package.mask | 3 ++- 3 files changed, 6 insertions(+), 3 deletions(-) |