On Thu, Mar 20, 2008 at 09:48:23AM +0100, Raphael Hertzog <[EMAIL PROTECTED]> was heard to say: > 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.
Raphael, This isn't terribly important, but I figured I'd clarify what I meant in case this comes up again. apt is an unusual library. Instead of having packages libapt0, libapt1, libapt3-libc6.7-blah, apt has a single package "apt" that provides the virtual package libapt-pkg-SONAME and the apt library libapt-pkg.so.SONAME. The consequence is that there's no way to avoid transient breakage when apt is upgraded: if you unpack apt first, all the old frontends can't find the old libapt-pkg and break; if you unpack the frontends first, they can't find the new libapt-pkg. If there is a bug here, I think it's probably in apt (but IIRC I've discussed this in the past and there were good reasons for this quirk, I think that it prevents a situation where there are no apt utilities at all that work). > > 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. That's kind of what I figured. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
