[Aptitude-devel] Bug#816781: aptitude: Can not cancel pending upgrade actions

[Andrei Demekhov]

On Sat, 5 Mar 2016 14:36:00 +0000 "Manuel A. Fernandez Montecelo" 
<manuel.montezelo at gmail.com> wrote:
> 2016-03-05 14:10 GMT+00:00 å¼  敬强 <zh_jq at outlook.com>:
> > 在 2016å¹´3月5日星期å
­ CST 下午1:00:25，Manuel A. Fernandez Montecelo 写道：
> >> The behaviour has been changed recently, so that when one goes ahead
> >> with the installation, the state is saved to more places than aptitude's
> >> internal state (e.g. dpkg), on which other tools feed.
> >>
> >> Since some parts of this state cannot be undone, and since there were
> >> other problems associated with this (e.g. removing "hold" state which
> >> had been set in previous sessions), "Cancel pending actions" has been
> >> changed in 0.7.6 to just cancel pending (as in "not confirmed/saved")
> >> actions, rather than marking all packages as "keep" and destroying other
> >> things in the way.
> >>
> >> Perhaps we should change the name of the menu entry to reflect the
> >> change of behaviour, but sadly the name fits much better the new
> >> behaviour, and the previous behaviour's menu entry should have been
> >> named instead "Keep all packages in its current state" or "Reset state
> >> of all packages".
> >>
> >>
> >> If you want to go back to the state before confirming the upgrade
> >> intentions, you have to mark the packages to be upgraded as "keep".
> >>
> > Thank you for the explanation, and it's acceptable for me.
> > So this bug can be closed.
>
> I think that it's better to leave it open for a while in the case that
> people find the same problem.
>
> Thanks for the feedback.
>
>
> Cheers.
> --
> Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
>
>

Hello, Manuel,

I cannot cancel pending actions which were scheduled by parsing the 
output from debsecan in this way:

# debsecan --only-fixed --suite sid|fgrep urgency |fgrep -v low|awk 
'{print $2}'|sort -u|xargs aptitude --schedule-only install

This behaviour might be related to the bug in question, and I find it 
inconvenient. Do we still have any opportunity of one-touch cancelling 
some scheduled actions in aptitude?

Best regards
Andrei Demekhov