On 2020-03-25 10:21, Jörg Sommer wrote: > jnqnfe@gmail.com hat am Mi 25. Mär, 09:03 (+0000) geschrieben: > > Package: libc6 > > Version: 2.30-3 > > > > sudo aptitude upgrade just now: > > > > ``` > > Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ... > > Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ... > > Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ... > > Unpacking libc-dev-bin (2.30-3) over (2.30-2) ... > > Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ... > > Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ... > > Preparing to unpack .../libc6_2.30-3_amd64.deb ... > > > > A copy of the C library was found in an unexpected directory: > > '/usr/lib/x86_64-linux-gnu/ld-2.30.so' > > It is not safe to upgrade the C library in this situation; > > please remove that copy of the C library or get it out of > > '/usr/lib/x86_64-linux-gnu' and try again. > > I'm having the same problem. It's caused by the package *usrmerge*, that > installed the symlinks: > > ``` > % ls -l /*(@) > lrwxrwxrwx 1 root root 7 Mär 7 2019 /bin -> usr/bin > lrwxrwxrwx 1 root root 7 Mär 7 2019 /lib -> usr/lib > lrwxrwxrwx 1 root root 9 Mär 7 2019 /lib32 -> usr/lib32 > lrwxrwxrwx 1 root root 9 Mär 7 2019 /lib64 -> usr/lib64 > lrwxrwxrwx 1 root root 10 Mär 7 2019 /libx32 -> usr/libx32 > lrwxrwxrwx 1 root root 8 Mär 7 2019 /sbin -> usr/sbin > ``` It happens that the checks in the libc6.preinst were broken, and that the fix for #954374 just fixed them. It also means that usrmerge broke those checks but we didn't notice it until now... I wonder if the best is to just remove all those checks in libc6.preinst. After all they haven't been useful all those years, although we also got a few bugs report about broken systems for which we don't know the cause and that might have been prevented by working checks. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
Attachment:
signature.asc
Description: PGP signature