[Bug 441059] Re: incorrect problem resolution

[Rolf Leggewie]

Daniel, thank you for keeping an eye on this.  I apologize for the late
response.  Here is my test-case.

1) add "deb http://oss.leggewie.org/LP441059 ./" to sources.list
2) sudo aptitude update;sudo install a a-extensions

This should install version 1.1 of those "packages" (they are simply
empty packages with the dependencies set as described in the original
report).

3) sudo aptitude

Step 3 should now offer you to remove the a package when doing nothing
would be fine. Aptitude::ProblemResolver::Discard-Null-Solution is only
a second-best solution.  While it defaults to keeping the status quo, it
still bugs the admin unnecessarily every time.

My brain is not compatible with the scribbling from Mr Jidanni, I
usually have no clue what his babblings are about and this time it's no
exception, so I can't comment on whatever he was writing in the Debian
BTS.

** Changed in: aptitude (Ubuntu)
       Status: Expired => New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to aptitude in Ubuntu.
https://bugs.launchpad.net/bugs/441059

Title:
  incorrect problem resolution

Status in “aptitude” package in Ubuntu:
  New

Bug description:
  Binary package hint: aptitude

  Aptitude will incorrectly handle the following situation.  Let's say I
  have package A and package A-extensions installed.  Package A
  recommends package A-extensions.  Package A-extensions always depends
  on the same version of A as itself.  Currently, both A and
  A-extensions are at version 1.1.  The upstream repo has 1.2 of A, but
  is still at 1.1 of A-extensions.

  If there are other packages to be updated, aptitude will (correctly
  IMHO) suggest to hold both A and A-extensions at 1.1.  That is fine.
  If there are no other packages to be updated (after all other packages
  have been updated), aptitude's only automatic solution is to remove
  A-extensions.  That is definitely wrong, since keeping both packages
  at the installed version resolves the problem just fine.  IMHO, this
  is also preferred over needlessly removing a package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/441059/+subscriptions