On Mon, May 01, 2006 at 01:16:05PM -0600, Jeremy Nickurak <[EMAIL PROTECTED]> was heard to say: > Package: aptitude > Version: 0.4.1-1experimental1 > Severity: normal > > Running aptitude with sid+experimental (although the dependancy problem is > the same under just sid). > > Emacs21-common 21.4a-3.1 hit mirror before emacs21 and emacs21-bin-common. > > Aptitude decides, instead of holding the packages at their current state, to > try to upgrade, which breaks emacs21's dependancies, which causes it to > remove all three packages. > > If attempting to upgrade a package would require that package's removal, > there's no point in trying to upgrade it :) > > > --\ Packages being removed because they are no longer used > > idA emacs21-common -35.5MB 21.4a-3 21.4a-3.1 > > --\ Packages being deleted due to unsatisfied dependencies > > id emacs21 -6042kB 21.4a-3 21.4a-3 > > idA emacs21-bin-common -342kB 21.4a-3 21.4a-3 > > --\ Packages being held back > > i A libgdl-1-0 0.6.0-3 0.6.0-3+b1ih > > pan 0.14.2.91- 0.94-1
Unfortunately, the interactions between the dependency resolver and the auto-removal code are not trivial. I used to have code in there that tried to detect and avoid this case, but it was demonstrated to me (sadly I've forgotten the demonstration now, but it was quite convincing) that this could not work and caused even more surprising and hard to diagnose problems. Daniel
signature.asc
Description: Digital signature
