[Aptitude-devel] Bug#848011: Bug#848011: aptitude doesn't ask for confirmation of removal for "markauto", leading to surprise removals

[Alexey Kopytko]

> Every package from the list for which there's no "why" found will be silently, with no
> indications whatsoever, scheduled for removal. If you were doing this from a script, or
> just copying and pasting code from somewhere, you'll be in trouble. Next time you happen
> to install updates, unbeknownst to you some of the packages above will be removed

>> Manuel: In case you see any chance to add the old behaviour as
>> optional feature/backwards compatibility flag (e.g. --immediately),
>> feel free to remove the wontfix tag. (Then again, there's an easy
>> workaround to get the old behaviour as shown above...)

What I really care is not that aptitude removes a package now or
later. If it does it later I'll be just fine.
What I care is that it puts the package into pending-delete state
without any confirmation in complete silence.

If it would ask a user to whenever mark a package as such or not
(y/N), then there won't be an issue.

How does that sounds?

-Alexey