On Sat, Sep 03, 2005 at 01:35:49PM -0400, Anthony DeRobertis wrote: > 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? For the record, the only two packages in sarge/etch that depend on libterm-readline-gnu-perl are soundgrab and adduser-ng. The impact of adding such a versioned conflicts to libc6, in terms of packages whose removal could be forced on upgrade as a result, appears to be acceptably small. Although the breakage on upgrade should be transient (installing the new version of libterm-readline-gnu-perl should be enough to allow all packages to finish configuring), I think it's worth making this change to help our users of the debconf readline frontend. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature