Could you verify that you see this behavior in the squeeze version
of aptitude as well? Also, I suspect it would be useful if you ran
aptitude with --log-level=info --log-file=aptitude.log' and sent the
log file to this bug report.
Thanks,
Daniel
--
To UNSUBSCRIBE, email to
On 2009-11-17 17:22 +0100, Daniel Burrows wrote:
Could you verify that you see this behavior in the squeeze version
of aptitude as well?
Does not seem to happen with it, but safe-upgrade in aptitude 0.4.11.x
is broken differently by bug #466228. I tried a locally built version
of aptitude
It appears that the problem is that aptitude is trying to fix soft
dependencies (recommendations) that were broken to start with. I think
this can be avoided with a fairly simple check.
Daniel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Package: aptitude
Version: 0.6.0.1-1
Severity: normal
The following does not seem right to me:
,
| % aptitude -s -V -D safe-upgrade
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| Reading extended state information... Done
|
4 matches
Mail list logo
