severity 410695 important thanks On Sun, Mar 04, 2007 at 09:31:33AM +0100, Josselin Mouette wrote: > > As the recommended upgrade path from sarge->etch is aptitude rather than > > apt, the main reason I've left this as 'serious' is concern that the cause > > is common to both apt-get and aptitude and just triggers sooner with apt-get > > (which seems to be the case if the problem is the dependency loop bug), and > > that, in the absence of clear understanding of the origin of the bug, there > > could be a significant number of other upgrade scenarios where apt would > > fail.
> > But if this only affects circular dependencies, that seems unlikely. > In all cases it seems unlikely to affect aptitude. If it is capable to > handle dependencies for prerm's in the circular loop case, it is most > probably capable to do the same in simpler cases like this one. I don't know if it's true that aptitude does this, or if some other difference between apt-get and aptitude means that aptitude tends to be "luckier". Anyway, downgrading this bug, it does seem to be a one-off problem at the moment. > > > An acceptable workaround would be to upload a dummy zope2.7 package, > > > which doesn't depend on python2.3, and would make the transition to > > > zope2.9. At least, such upgrades wouldn't fail. > > Based on discussions on the -python list, where users insist that it's > > unacceptable even for zope2.7's removal to be forced on upgrade to etch, it > > seems unlikely that this would be accepted either. > Are you suggesting to re-upload python2.3 and zope2.7 to etch? The suggestion was to find a way that python doesn't need to conflict with python2.3. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
