Bug#984533: libc6: upgrade from 2.28-10 to 2.31-9 breaks system
On 2021-03-05 14:41 +0100, Aurelien Jarno wrote:
> control: notfound -1 libc6/2.28-10
> control: found -1 libc6/2.31-9
> control: severity -1 grave
>
> On 2021-03-04 19:26, Thomas Hahn wrote:
>> Package: libc6
>> Version: 2.28-10
>> Severity: normal
>> X-Debbugs-Cc: thahn01@t-online.de
>>
>> Dear Maintainer,
>>
>> installed buster, then apt upgrade was also fine,
>> but the following dist-upgrade put the system in a broken state.
>>
>> Preparing to unpack .../62-locales_2.31-9_all.deb ...
>> Unpacking locales (2.31-9) over (2.28-10) ...
>> Preparing to unpack .../63-openssh-server_1%3a8.4p1-4_amd64.deb ...
>> Unpacking openssh-server (1:8.4p1-4) over (1:7.9p1-10+deb10u2) ...
>> Preparing to unpack .../64-libc6_2.31-9_amd64.deb ...
>> whiptail: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not
>> found (required by /lib/x86_64-linux-gnu/libslang.so.2)
>
> This seems to show that libslang2 has been wrongly unpacked before
> libc6. Do you happen to have the beginning of the log? You can find it
> in /var/log/apt/term.log.*
>
>> debconf: whiptail output the above errors, giving up!
>> Checking for services that may need to be restarted...dpkg: error
>> processing archive
>> /tmp/apt-dpkg-install-I51xYx/64-libc6_2.31-9_amd64.deb (--unpack):
>> new libc6:amd64 package pre-installation script subprocess returned error exit status 255
>> Selecting previously unselected package libcrypt1:amd64.
>> dpkg: considering deconfiguration of libc6:amd64, which would be broken by installation of libcrypt1:amd64 ...
>> dpkg: yes, will deconfigure libc6:amd64 (broken by libcrypt1:amd64)
>> Preparing to unpack .../65-libcrypt1_1%3a4.4.17-1_amd64.deb ...
>> De-configuring libc6:amd64 (2.28-10) ...
>> Unpacking libcrypt1:amd64 (1:4.4.17-1) ...
>> Errors were encountered while processing:
>> /tmp/apt-dpkg-install-I51xYx/64-libc6_2.31-9_amd64.deb
>> Error: Timeout was reached
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> To unbreak your system the best would be to unpack libc6 manually using
> the following command:
> dpkg -x /var/cache/apt/libc6_2.31-9_amd64.deb /
No, never do that! This command actually runs "dpkg-deb -x" which,
unlike "dpkg -i", will silently overwrite symlinks to directories on the
filesystem with directories contained in the package. This is very bad
if /lib is a symlink to /usr/lib (the "usrmerge" layout).
Cheers,
Sven
Reply to: