On Wed, 19 Mar 2008, Daniel Burrows wrote: > This is not a bug in aptitude. Upgrading apt removes the old library > that aptitude links against, and until the new aptitude is installed > there's no way it will be able to link. Vice versa (and what's indicated > above), upgrading aptitude causes it to link against a new apt library, > and it won't work until the new version of apt is installed.
Daniel, the new aptitude will only be unpacked after the new apt has been unpacked. So there's no "dpkg" bug either AFAIK. The only problem is that the call to ldconfig happens only when apt is configured and thus between apt's unpacking and apt's configuration, any usage of the upgraded libapt might fail (as the aptitude call showed). If we really want to fix this, we must make sure that libapt users pre-depend on it instead of simply depending on it (unless we add an ldconfig somewhere else in the process, like in aptitude's preinst but I'm not sure it's a great idea either). > Please confirm that aptitude worked after the upgrade so I can assign > this to dpkg only (or close it, if Raphael thinks that's more > appropriate). I don't think assigning it to dpkg makes sense. There are possible work-arounds on aptitude's side but I'm not sure the cost they imply outweighs the benefits. If you decide to not implement one of the work-around, then please simply close the bug. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
