Bug#438586: Workaround/Fix Re: Bug#438586: libc6 upgrade renders etch unusable

["Nathan O. Siemers" <nosha@fiveprime.org>]

Hello Aurelien,

The only thing I had done up to that point was to run:

apt-get update; apt-get upgrade

within the chroot environment.  libc6 was one of the packages that was on the list to upgrade at that time.  The install failed which left me in the state below.

I now have a fix/workaround: 
    Upgrading libc6 on the Parent x86_64 distribution
    followed by a reboot
    then reinstall of libc6 withing the 32 bit chroot

     repairs the 32 bit system and now all is well.

    So it seems that the system (kernel?) did not like the mix of libcs on the system?  I have to think about why this would be a problem, as the architectures are of course different.

    Thanks for your quick responses.  I still regard this as a bug, but no longer critical as the workaround is straightforward (once you see the terror of a libc upgrade hosing one system and bite the bullet and run the same install on another ;) )

Nathan Siemers

Nathan Siemers - Fiveprime.org - http://www.fiveprime.org

Aurelien Jarno wrote:

Nathan O. Siemers a écrit :
  

Package: libc6
Version: latest pushed out as an update to etch.
Severity: critical

apt-get  update; apt-get install

using vanilla etch and security sources on a chrooted ia32 debian system 
is rendered unusable, with most binaries complaining of library errors:


line:/# apt-get upgrade
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
correct the problem.
    

What did you do to come up to this point? Do you have a log to this part?

  

line:/# dpkg --configure -a
dpkg: relocation error: /lib/libpthread.so.0: symbol errno, version 
GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

The system is now unusable, fortunately it is chrooted underneath a pure 
amd64 debian etch system.  I'm afraid to run the update there.
    

Could you please send us the output of ls -l /lib /lib/tls
/lib/tls/i686/cmov/ from your chroot (or prefix the path of your chroot
if it is too broken to run such commands).

  

Debian Etch.
amd64 host with emul-ia32 chroot environment (where the problem is so far).
    

What do you mean by emul-ia32 chroot? You mean that it is installed in
/emul/ia32-linux/ ?

 --
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net