[Aptitude-devel] Bug#419501: aptitude: Strange conflict resolution

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo


Hi Christoph,

2007-04-23 15:05 Christoph Pleger:
>Hello,
>
>On Fri, 20 Apr 2007 07:03:00 -0700
>Daniel Burrows <dburrows at debian.org> wrote:
>
>> On Fri, Apr 20, 2007 at 09:31:31AM +0200, Christoph Pleger
>> <Christoph.Pleger at cs.uni-dortmund.de> was heard to say:
>> > Hello Daniel,
>> >
>> > On Thu, 19 Apr 2007 20:37:16 -0700
>> > Daniel Burrows <dburrows at debian.org> wrote:
>> >
>> > >   It looks like the problem is that aptitude is noticing that you
>> > >   have a
>> > > pile of unresolved recommendations and fixing them for you.  The
>> > > weird thing, to me, is that there are no candidates to resolve the
>> > > recommendations, which I bet is why aptitude insists on removing
>> > > the packages.
>> >
>> > When I add cupsys-bsd to the package list which I set by "dpkg
>> > --set-selections", all desired packages are installed. But I do not
>> > want do that, see below.
>>
>>   What I mean by that is that aptitude can't find any way to resolve
>>   the
>> recommendations, other than removing the recommenders.  Eliminating
>> all hard dependency conflicts "fixes" the problem because aptitude
>> doesn't have to resolve dependencies at all (it only notices broken
>> recommendations when it's kicked into dependency resolution).
>>
>>   Have you tried turning down the penalty for leaving recommendations
>> unsatisfied?
>
>That helped, but I think that aptitude should never let packages
>uninstalled only because of recommendations that cannot be fulfilled.

I am not aware of such problems for a long time, and there are no other
similar bug reports.

Are you aware of this still happening nowadays?

I can try to reproduce it, but for that I have to find such a package or
create an artificial one... might take a bit to get around doing it.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>