On Wed, Oct 21, 2009 at 01:30:11PM +0300, Eugene V. Lyubimkin wrote: > Hello Gabor, > > Gabor Gombas wrote: > > On Wed, Oct 21, 2009 at 12:01:51PM +0300, Eugene V. Lyubimkin wrote: > > > >> 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. > > > > Hmm. "remove old libc6-i686, upgrade libc6, install new libc6-i686" > > seems to be a sequence where the Pre-Depends never breaks. Since > > libc6-i686 is not needed for the system to function properly > Good idea, but the package manager doesn't know this. Ok, I can add the list > option to libcupt to list the packages allowed to 'remove old ... install new' > instead of 'upgrade old -> new', with the first value is 'libc6-i686'. I will > implement this for the next version if nothing better appears.
Gabor's suggestion looks similar to the first thing I suggested in #543365 and sounds like it should work generally for the Pre-Depends situation. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <james...@debian.org>
signature.asc
Description: Digital signature
