[solved]Re: aptitude cli undocumented behaviour [was: aptitude cli options vs. apt-get ...]

[Michael Lange <klappnase@freenet.de>]

On Wed, 5 Oct 2016 22:37:40 +0200
Jörg-Volker Peetz <jvpeetz@web.de> wrote:

> You used '~U' in the first and the last command, not '~ahold'.
> This last command could also be written shorter:
> 
>   aptitude -y -v -s full-upgrade '~U' | ...

Thanks!!!
You are of course right, that was a copy and paste accident. (^.^);

I just tried it (i.e. what I actually wanted to try before) again on my
laptop (with stretch), where (much to my confusion) things worked as the
man page promised - now I know why!
Actually I already have been thinking about using (consciously this time)

    aptitude -y -v -s full-upgrade `aptitude -q=2 -F %p search ~U`

, but invoking it this way looks a lot like a pain in the neck (and btw
appears to be slower). I wasn't aware that you can pass a search pattern
like ~U to full-upgrade. This seems to do exactly what I want.

> 
> There's also the switch '--remove-user-tag':
> 
>   aptitude -y -v -s --remove-tag hold full-upgrade | ...

This does not seem to have any effect. Isn't this used rather like

    aptitude remove-user-tag hold pkgname

which at least with "hold" as tag does not have any effect either, I
suppose it's meant for custom user-defined tag names?

Anyway, "aptitude -y -v -s --allow-untrusted full-upgrade '~U'" seems to
be what I want.

Thanks for your help!

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Men of peace usually are [brave].
		-- Spock, "The Savage Curtain", stardate 5906.5