> 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
>
> Moreover, to reinstantiate it one should use install command but not markauto:
>
> aptitude markauto foo # has no effect
> aptitude install foo # really removes the flag
>
> Which is another source of confusion. See, there's more to the confusion now.
>
That should read unmarkauto:
aptitude u
On Tue, Dec 13, 2016 at 7:21 PM, Axel Beckert wrote:
> If you insist on the old behaviour, you can call e.g. "aptitude
> markauto … && aptitude install" ("aptitude install" without any
> further parameter) as a workaround.
Not nearly close to the previous behavior.
Even if I reject the uninstal
Control: severity -1 wishlist
Control: tag -1 + wontfix
Hi,
Alexey Kopytko wrote:
> Before 0.8.3 aptitude asked if one wants to remove a package if
> marked as autoinstalled.
It still does, as you reported yourself:
> $ sudo aptitude safe-upgrade
> Resolving dependencies...
> T
Package: aptitude
Version: 0.8.3-1+b2
Severity: important
Dear Maintainer,
Before 0.8.3 aptitude asked if one wants to remove a package if marked as
autoinstalled.
Since version 0.8.3 aptitude's behavior irreversible changed, breaking all
preexisting
assumptions. Now it doesn't ask at all, ev
5 matches
Mail list logo
