Bug#1065831: document package specifiers for `upgrade`
On Wed, Mar 13, 2024 at 09:44:02AM +0100, Miguel Angel Rojas wrote:
> Hi there,
>
> > If "apt upgrade" is saying that it removes packages, that is a bug, yes.
>
> @david: it is not a bug, apparently.
>
> To put everything in a nutshell:
>
> - "apt upgrade" can remove packages
No. Without a package as an argument it won't.
> - "apt upgrade" accepts specific packages to be upgraded
To be installed if not installed yet, removed, downgraded or upgraded if
already installed depending on your arguments. For example `apt upgrade foo-
bar+ baz=version toto/archive' will remove foo, add bar, install, up- or
downgrade baz and the same for toto and it will upgrade packages where it can.
> Therefore, this behaviour is expected and documentation needs to be
> modified.
>
> In the meantime, while the documentation is modified, can some developer
> provide some explanation to the current "apt upgrade" behaviour? (*)
Julian provided an explanation in #74, [🔎] 20240312113620.GA1944926@debian.org
> whereas `apt upgrade foo` first does the normal install argument handling and
> then runs an upgrade, so `foo` could also be a new package that is not
> currently installed to hint the solver if it is unable to find a solution.
> (*) I'm a bit confused because I don't know which of the people involved in
> this bug are actually a developer of the apt package ;)
I'm not a Debian developer, never been. Just someone who submitted a patch or
two.
Cheers,
Wesley
Reply to: