Bug 884655 – sys-apps/merge-usr-6 failed to merge /usr/sbin into /usr/bin?

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Majed 2022-12-07 08:39:43 UTC]

ls -l /
lrwxrwxrwx   1 root root     7 Dec  2 09:30 sbin -> usr/bin



The systemd ebuild currently expects sbin to point to usr/sbin not usr/bin and dies because of this mismatch.

Strangely enough, the merge-usr script contradicts this and sets what i have.

https://forums.gentoo.org/viewtopic-p-8763003.html#8763003

[Comment 1 Mike Gilbert 2022-12-07 16:45:45 UTC]

Sorry, but there's not enough info for me to confirm this as a bug. If you are able to reproduce the issue and provide more details, feel free to re-open.

[Comment 2 Majed 2022-12-08 06:38:47 UTC]

(In reply to Mike Gilbert from comment #1)
> Sorry, but there's not enough info for me to confirm this as a bug. If you
> are able to reproduce the issue and provide more details, feel free to
> re-open.

i have 4 gentoo machines, the one that was systemd from the start produced no errors. the other 3 migrated from init (rc), are stuck not updating, and systemd  won't emerge what more info is needed?

[Comment 3 Brian Evans (RETIRED) 2022-12-08 13:23:38 UTC]

I believe that the news instructions are missing a couple important steps.

The dry run should not be optional.
If there are any ERRORs in the dry run, then they need to be addressed or else "bad things" (like this, even if not a system stopper) happen.

This all assumes that the dry run will show duplicated file names between source and destination (I have not looked that deeply) as ERROR.

[Comment 4 Mike Gilbert 2022-12-08 16:20:07 UTC]

(In reply to Majed from comment #2)
> i have 4 gentoo machines, the one that was systemd from the start produced
> no errors. the other 3 migrated from init (rc), are stuck not updating, and
> systemd  won't emerge what more info is needed?

Did you run merge-usr --dryrun first? Did it output any errors?

If you did not run a dryrun first, I would at least like to see the error output from the *first time* you ran merge-usr on an affected system. Running it in the current state doesn't help much.

If you have a system backup from before you ran the merge, it would be helpful to inspect it for conflicting files in /bin, /sbin, /usr/sbin, and /usr/bin.

Alternatively, please provide exact steps to reproduce the problem from a known state (like a stage3 install).

[Comment 5 Larry the Git Cow 2022-12-08 16:55:54 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=5d869a12d47362055873f519a82313c6f40fdbdb

commit 5d869a12d47362055873f519a82313c6f40fdbdb
Author:     Mike Gilbert <[e-mail]>
AuthorDate: 2022-12-08 16:44:33 +0000
Commit:     Mike Gilbert <[e-mail]>
CommitDate: 2022-12-08 16:54:42 +0000

    2022-12-01-systemd-usrmerge: rework steps based on feedback
    
    Bug: https://bugs.gentoo.org/884655
    Signed-off-by: Mike Gilbert <[e-mail]>

 .../2022-12-01-systemd-usrmerge.en.txt                  | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

[Comment 6 Majed 2022-12-09 08:16:38 UTC]

(In reply to Mike Gilbert from comment #4)
> (In reply to Majed from comment #2)
> > i have 4 gentoo machines, the one that was systemd from the start produced
> > no errors. the other 3 migrated from init (rc), are stuck not updating, and
> > systemd  won't emerge what more info is needed?
> 
> Did you run merge-usr --dryrun first? Did it output any errors?
> 
> If you did not run a dryrun first, I would at least like to see the error
> output from the *first time* you ran merge-usr on an affected system.
> Running it in the current state doesn't help much.
> 
> If you have a system backup from before you ran the merge, it would be
> helpful to inspect it for conflicting files in /bin, /sbin, /usr/sbin, and
> /usr/bin.
> 
> Alternatively, please provide exact steps to reproduce the problem from a
> known state (like a stage3 install).

dry run produced some warnings but i didn't think that it would be critical.
install gentoo rc.d mode from 2015, switch to systemd (the one around 2020), run merge-usr update, in world update, systemd fails to install..!

[Comment 7 Sam James 2022-12-09 15:04:07 UTC]

Note that floppym has responded on the forum site with a view to getting your system sorted, it's just hard on the bug side to figure out what went wrong after-the-fact.