Bug#351592:
(Oops- I've recently changed my default editor from vim to emacs and it
seems that emacs doesn't line wrap in the way I'd hoped! Hopefully this
re-send should be much more readable)
During an install on a mostly sarge system of newer "x-window-system-core"
from testing, apt-get warns of dependency problems but doesn't prompt for
permission to proceed or suggest any solution.
I'd expect the dependency resolution to either remove the packages which
no longer have their dependencies met or to upgrade them so that they
depend on the newer packages being installed. I'd thought the dependency
problems would be recognised in the initial stages and resolved in the
solution presented before the "Do you want to continue? [Y/n]". Failing
this automation, should there not be a warning and some opportunity to
abort the install?
My example is below. Is this expected behaviour? Any advice appreciated.
Thanks,
Andrew Archibald (andrew@choppywater.net)
Reply to: