[Aptitude-devel] Bug#632227: aptitude crashed during safe-upgrade operation

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo
Control: close -1

Hello Grzegorz,

2011-06-30 17:48 Grzegorz Andruszkiewicz:
>Package: aptitude
>Version: 0.6.3-4
>Severity: important
>
>I was running the aptitude safe-upgrade command to update the system after a
>while (there were about 1400 packages being updated). However after unpacking a
>couple of packages aptitude crashed with a message that there are too many
>errors. Presumably too many dependencies were broken.
>
>I think that aptitude should check if the operation will not cause too many
>dependencies being broken before it starts. After it crashed it failed to even
>start again (see bug 632125). I was forced to run apt-get -f dist-upgrade to
>get the system to some stable state, but I lost all the auto marks on packages.

Sorry that this bug was not handled in a more timely manner, but this
bug report is not very actionable as it is.

We would need to know at least some approximate message of what it
complained about, "too many errors" is not enough, there is nothing
matching "-i 'many.*broken'" in the source.  Also, using unstable and
doing big upgrades from time to time for more than a decade, I never
encountered such a message, so I have no clue about what might be the
problem.

Additionally, seeing the other bug report, it is not clear that "it
failed to even start again": in fact it did, and it was doing dependency
resolution (maybe the system was left in a state very difficult to
resolve and thus it was taking unreasonable long time; or needed too
much memory or other causes; aptitude bugs/problems or not).  But that
is different than failing/refusing to even start because e.g. the file
recording package states was corrupt, for example.

So I am going to close this bug report now, because I think that nothing
useful can be extracted from it.


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