Package: libc6 Version: 2.3.5-6 Severity: serious -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I just did a glibc upgrade, and then many, many packages failed to configure, leaving the system quite broken. It turns out this is a bug in libterm-readline-gnu-perl which is exposed in the new glibc (see 304604 and 322746). While this is indeed not actually a bug in libc6, it still no less breaks the system, and will likely even break sarge -> etch upgrades. Also, testing is broken now, because the new libterm-readline-gnu-perl is not present. I think if libc6 were to declare a versioned conflict on old versions of libterm-readline-gnu-perl, this would prevent the problem from happening. If that's correct, could you please add it? - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (130, 'unstable'), (120, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-bohr Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDGd70+z+IwlXqWf4RAhueAJ9PVZWsAWG9SRJZrsvBubAy7EoD4wCcCp4q 5IMVYF9XTnS5RuWWpjpaV0s= =BuWU -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
