I am now running into another similar issue (some background in bug
1959485) where even with the snippet from comment 3 I am told there are
2 broken packages even after accepting a solution from aptitude resolver
to resolve all open issues.
--
You received this bug notification because you are a
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
Rolf, I think your report may have been the situation described here:
http://bugs.debian.org/511366
which applies to using full-upgrade when the only upgrades available
result in breakage.
** Bug watch added: Debian Bug tracker #511366
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511366
[Expired for aptitude (Ubuntu) because there has been no activity for 60
days.]
** Changed in: aptitude (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/4410
I will try to provide a test case in the next few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/441059
Title:
incorrect problem resolution
To manage notifications about this bug go to:
https:
Please state what action you are trying to perform. Instructing
aptitude to perform a dist-upgrade is different to safe-upgrade, and
different again to directly asking for a new version of "package A".
** Changed in: aptitude (Ubuntu)
Status: New => Incomplete
--
You received this bug n
> speaking in more general terms, aptitude generally fails to accept "keep
> everything as it is" when there are currently no unresolved conflicts but
> updates introduce irreconcilable conflicts. Aptitude will not present "hold
> all packages" as a solution.
You may find adding this to /etc/apt/a
actually, it's worse, aptitude actively creates problems :-(
I have acroread pinned to a self-compiled package that depends on
acroread-debian-files. The official package from the partner repository
conflicts with acroread-debian-files. All dependencies are resolved and
there are no conflicts.
speaking in more general terms, aptitude generally fails to accept "keep
everything as it is" when there are currently no unresolved conflicts
but updates introduce irreconcilable conflicts. Aptitude will not
present "hold all packages" as a solution.
** Tags added: lucid
--
incorrect problem r
