Hello James, James Vega wrote: > Package: cupt > Version: 1.0.0 > Severity: critical > > Running "cupt -R --purge safe-upgrade" today, ended up breaking the > system because of an incorrect upgrade order. Partway through the > process, dpkg segfaulted and most other tools also segfaulted due to > mis-matching libc package versions. Running "apt-get upgrade" worked > fine after I rebooted to a rescue cd and downgraded the libc packages to > 2.9-27. Firstly, I am sorry about the troubles you had. > Here's the information I have from another computer that I can deal with > being broken for a few days (hand-typed so apologies for typos and > truncation of non-libc6 information). > > The upgrade was from 2.9-27 to 2.10.1-1. The 5 binary packages from the > eglibc source package that were being considered for upgrade were: > libc-bin, libc-dev-bin, libc6-dev, libc6-i686, and libc6. > > $ cupt -R --purge safe-upgrade > ... > W: the pre-dependency(ies) 'libc6 (= 2.9-27)' will be broken during the actions, the packages involved: 'libc6', 'libc6-i686' > W: the pre-dependency(ies) 'libc6 (= 2.10.1-1)' will be broken during the actions, the packages involved: 'libc6-i686', 'libc6' However, this is another side of already archived http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543365 (ironically, reported by you too). On i386 we have the issue: libc6-i686 strictly Pre-Depends on libc6 (= ...), and whatever package from this two cupt tries to upgrade first, the pre-dependency will be broken. Let me try to add libc maintainers to the loop to know the correct upgrade path. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer
Attachment:
signature.asc
Description: OpenPGP digital signature