On Thu, Mar 13, 2008 at 11:36:54PM +0000, Alan Mackenzie <[EMAIL PROTECTED]>
was heard to say:
> My aptitude has entered a catastrophic state: it wants to delete an
> infinite number of system critical packages. I naturally wish to clear
> this state and start from fresh. [Incidentally, PLEASE don't tell me to
> upgrade my aptitude first. I can't, at the moment. ;-]
Ok, well, then I can't help you get at the menu command that would fix
it (introduced in version 0.4.2) or point you to the documentation of how
to use that command.
In version 0.3.4, I added a "keep-all" command line action. That also
isn't in your version. (BTW, I'm mentioning this not to be obnoxious,
but in case someone stumbles onto the bug via Google)
Luckily, version 0.2.15 (2004) got a package action called "keep",
activated by pressing ":". If you select each of the top-level package
groups and press ":", the actions should be cleared. You can also run
aptitude keep '!~akeep'
and the actions should be cleared.
> The normal expedient here, of course, would be to quit the program and
> start again. However, aptitude "helpfully" preserves this catastrophe in
> some state file for the next time you run it. ;-( The fine manual
> doesn't identify this file - otherwise, I could simply delete it. THIS
> IS A BUG!!!! The man page doesn't have a FILES section identifying the
> file. THIS IS ALSO A BUG!!!! C-c'ing out of the program, as suggested
> by the FM, doesn't help.
I like the idea of adding a FILES section. Should be easy enough to
add.
Since the other requests in this bug exist already, I'll close it once
that's done.
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
