[Aptitude-devel] Bug#661678: aptitude: Command-line install conflicts cause stupid resolution attempts

[Daniel Hartwig]

On 29 February 2012 16:36, Matthias Urlichs <matthias at urlichs.de> wrote:
> Package: aptitude
> Version: 0.6.5-1
> Severity: minor
>
> On a long-not-updated system where installation requires a Perl update:
>
> $ aptitude install smurf-kde
> ## my metapackage which simply depends on a bunch of KDE stuff
> [ attempt to resolve the non-existing conflict which includes: ]
> 206)     smurf-kde [Not Installed]
>
> Uhh, what? When I explicitly want to install something, attempts to resolve
> the problem by not-installing that very package are stupid. Please pre-add
> these to the exclusion list, particularly if only one package is mentioned
> on the command line.
>
> Also, I'm astonished that attempts to not-install 200 packages get higher
> priority than updating ten packages.
>
> …
> APT prefers testing
> APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'),
> (550, 'experimental') Architecture: i386 (i686)

Hello

Does smurf-kde pull in anything from unstable or experimental?


Regards