Re: how to make dselect "forgot" what it wants to remove

[Clive Menzies <clive@clivemenzies.co.uk>]

On (03/08/05 11:47), H. S. wrote:
> If I do an update using dselect and it reports that n packages will be
> installed and nnn will be removed, and I abort dselect (thinking to do
> it later hoping newer packages will resolve the issue), I notice that
> the next time if I start dselect it still remembers which packages it
> wanted to uninstall earlier(assuming newer updates haven't affected
> that). And if I do nothing, just choose to removing pending packages, it
> removes all of these (which, I guess, is expected).
> 
> How do I tell dselect to forgot what it wanted to do in the previous
> update session and start anew the next time?

It's been a long time since I used dselect but I recall that something
like Ctl-X would undo.

There is a quick help which should give you the correct combination.

Otherwise, use aptitude instead.   I long delayed changing on the basis
of 'the devil you know' but since switching I've had far fewer
dependency problems.  You may see a few initially but use '=' or ':' to
hold packages that you don't want removed or upgraded.

= holds packages indefinitely
: holds packages for this upgrade only

To find broken packages search (/) ~b

Help is provided and as someone else suggested recently, install the
aptitude-doc-en.

Regards

Clive

-- 
www.clivemenzies.co.uk ...
...strategies for business