* Package 'sys-apps/systemd-252.4' has internal collisions between non- * identical files (located in separate directories in the installation * image (${D}) corresponding to merged directories in the target * filesystem (${ROOT})): * * /usr/lib/systemd/libsystemd-core-252.so * /usr/lib/systemd/libsystemd-core-252.so * /usr/lib64/systemd/libsystemd-core-252.so * Differences: size, content * * /usr/lib/systemd/libsystemd-shared-252.so * /usr/lib/systemd/libsystemd-shared-252.so * /usr/lib64/systemd/libsystemd-shared-252.so * Differences: size, content * * Package 'sys-apps/systemd-252.4' NOT merged due to internal collisions * between non-identical files. If necessary, refer to your elog messages * for the whole content of the above message.
Created attachment 848378 [details] emerge --info output
What is /usr/lib on your system? Is it a symlink to /usr/lib64? Please also attach the full build.log.
Created attachment 848380 [details] systemd build log
(In reply to Sam James from comment #2) > What is /usr/lib on your system? Is it a symlink to /usr/lib64? /usr/lib is a directory, just as /usr/lib64. I ran merge-usr a while ago... > Please also attach the full build.log. Done.
The build system shouldn't be installing anything in /usr/lib64/systemd. I don't see any obvious reason it would do that. I can't reproduce the issue myself, and I suspect this is caused by something weird that is specific to your system. I'm highly suspicous of bashrc hooks or custom eclass functions here.
(In reply to Mike Gilbert from comment #5) Please disregard my previous comment. It seems my knowledge is outdated. On my system, /usr/lib/systemd/libsystemd-core-252.so, /usr/libx32/systemd/libsystemd-core-252.so, and /usr/lib64/systemd/libsystemd-core-252.so all exist as separate files. On your system, it seems that /usr/lib/systemd and /usr/lib64/systemd represent the same directory. It is likely that you have a symlink somewhere that should not exist.
(In reply to Mike Gilbert from comment #6) > [...] > > On your system, it seems that /usr/lib/systemd and /usr/lib64/systemd > represent the same directory. It is likely that you have a symlink somewhere > that should not exist. Hmm: zephyr ~ # ls -ld /usr/lib{,64}/systemd lrwxrwxrwx 1 root root 17 Feb 28 2022 /usr/lib64/systemd -> ../../lib/systemd drwxr-xr-x 16 root root 4096 Dec 13 12:09 /usr/lib/systemd zephyr ~ # So /usr/lib64/systemd is not meant to be a symlink? I'll remove it and try remerging systemd again :)
I removed /usr/lib64/systemd symlink and systemd emerged fine :-) Thank you, Mike! I have no idea where that symlink came from... m( The bug can be closed.
It looks like the behavior was changed in systemd-252, which is probably why that symlink did not cause problems with earlier versions. https://github.com/systemd/systemd/blob/v252/NEWS#L326 > * Private shared libraries (libsystemd-shared-nnn.so, > libsystemd-core-nnn.so) are now installed into arch-specific > directories to allow multi-arch installs.
(In reply to Mike Gilbert from comment #9) > It looks like the behavior was changed in systemd-252, which is probably why > that symlink did not cause problems with earlier versions. Thanks for your research!
