Hi, Yuri D'Elia wrote: > But right now I want to install a newer version of a package and break > some other dependencies (without uninstalling them as aptitude recommends).
Ok, I never felt the urge to do that. In such cases I use either hold or forbid-version and don't install packages with broken dependencies. (Or build a package with fixed dependencies locally. And then I need dpkg anyway.) > > 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? If I remember correctly it does. But there are still some open bugs around the dpkg/aptitude states synchronisation. http://bugs.debian.org/137771 comes to my mind, but is probably not relevant here. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
