On Mon, Jun 12, 2023 at 5:48 AM Bastien Durel
<bastien+debian-u...@geekwu.org> wrote:
>
> Hello,
>
> During bookworm upgrade, I ran into some usrmerge failures, which led
> to an hard-to-fix situation
>
> Paramétrage de usrmerge (35) ...
>
> FATAL ERROR:
> Both /lib/x86_64-linux-gnu/libidn.so.11 and
> /usr/lib/x86_64-linux-gnu/libidn.so.11 exist.
>
> You can try correcting the errors reported and running again
> /usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
> Do not install or update other Debian packages until the program
> has been run successfully.
>
> E: usrmerge failed.
>
> root@corrin:/root # /usr/lib/usrmerge/convert-usrmerge
> /usr/bin/perl: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not
> found (required by /usr/bin/perl)
> /usr/bin/perl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not
> found (required by /usr/bin/perl)
> /usr/bin/perl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not
> found (required by /usr/bin/perl)
> /usr/bin/perl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not
> found (required by /usr/bin/perl)
> /usr/bin/perl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not
> found (required by /lib/x86_64-linux-gnu/libcrypt.so.1)
> /usr/bin/perl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not
> found (required by /lib/x86_64-linux-gnu/libcrypt.so.1)
> root@corrin:/root # rm /usr/lib/x86_64-linux-gnu/libidn.so.11
> Erreur de segmentation (core dumped)
> root@corrin:/root # ls -l /usr/lib/x86_64-linux-gnu/libidn.so.11
> ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required
> by ls)
> ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required
> by /lib/x86_64-linux-gnu/libselinux.so.1)
> ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.30' not found (required
> by /lib/x86_64-linux-gnu/libselinux.so.1)
> ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required
> by /lib/x86_64-linux-gnu/libselinux.so.1)
>
> As no system tool was usable in this situation (dpkg crashed too), I
> powered-off the machine and restored it from backup. I then installed
> usrmerge on bullseye, fixed the problems, then done the bookworm
> upgrade without any other problems.
>
> As usrmerge is mandatory on bookworm ; and usrmerge failure during
> upgrade leads to (could lead to ?) big problems ; shouldn't its
> installation be advised in 4.1 or 4.2 chapters of the upgrade guide ?
>
> I know 5.1.14 says merged-/usr is now required ; but it does not warn
> about failures, and I don't think I'm the only one who don't read the
> next chapter before starting upgrade ;)
I wonder if you have a bunch of stale symlinks...
Does symlinks report any dangling links for the problem shared libraries?
sudo symlinks -r / | grep dangling
If the list of dangling looks safe to clean-up, then you can run
sudo symlinks -r -d /
Jeff
