[Aptitude-devel] Bug#721818: Bug#721818: Should allow to install/remove packages even when dependencies are broken

Yuri D'Elia yuri.delia at eurac.edu
Wed Sep 4 11:07:45 UTC 2013


On 09/04/2013 01:04 PM, Axel Beckert wrote:
> Huh? I use aptitude on a lot of Sid/Experimental machines daily and I
> need that only in very, very seldom cases. And if so, it's usually
> easily to solve with a "dpkg --remove --force-depends" before running
> aptitude at all.

I also need it very rarely.

But right now I want to install a newer version of a package and break
some other dependencies (without uninstalling them as aptitude recommends).

I dropped to dpkg in the past, but in some situations it's just way
easier to use aptitude.

> But since aptitude saves your current state of planned actions (unless
> you quit it with Ctrl-C), it's easy to call "dpkg --remove
> --force-depends" without losing your planned actions.

Does running dpkg --force-depends keep the auto state of the packages in
this case?



More information about the Aptitude-devel mailing list