Comment 79 for bug 831768

Maybe I misunderstand the meaning of the "importance" bit. I thought it was importance to the functioning of this package, so that availability of other package managers is irrelevant to its setting.

While changing the bug's importance doesn't change anyone's priorities in fixing aptitude, it does accurately reflect the status of this bug for the usage of aptitude in current ubuntu: for those using multiarch, it makes aptitude just about useless, if not worse (when silly enough to listen to its' recomendations of what to change/delete).

I personally decided to remove it until this is fixed, despite having used it in preference to apt-get etc. for several years as I find it easier to get a good idea of dependencies (and especially conflicts) for packages.

But right now starting aptitude means waiting for it to go through a mass of conflict resolution to reach a faulty end-solution., and then having to look through the false positive conflicts/brokenness information, and discarding those (remove xx pagackes - and then most of the rest of the system thanks to dependencies? no thanks) before being able to do anything. So high does seem on the low side, and critical is more accurate.