Dear Maintainer,
* What led up to the situation?
The relatively new --update option is quite great, thanks for adding that!
It is nice to have compose-ability on options, and the list --upgradable is likely a good candidate for an exception.
# apt list --upgradable --update
Error: Command line option --update is not understood in combination with the other options
It would be nice to have support for running metadata updates on list.
There may be some updates between the last automated update, and the time of running the command.
* What exactly did you do (or not do) that was effective (or ineffective)?
The full shell session may be useful to grasp why this could be a good idea: when running before the metadata updates, 5 packages were identified for update, and after, there there 9.
# apt list --upgradable --update
Error: Command line option --update is not understood in combination with the other options
# apt list --upgradable
firefox-esr-l10n-es-ar/stable-security 140.3.1esr-1~deb13u1 all [upgradable from: 140.3.0esr-1~deb13u1]
firefox-esr-l10n-es-cl/stable-security 140.3.1esr-1~deb13u1 all [upgradable from: 140.3.0esr-1~deb13u1]
firefox-esr-l10n-es-es/stable-security 140.3.1esr-1~deb13u1 all [upgradable from: 140.3.0esr-1~deb13u1]
firefox-esr-l10n-es-mx/stable-security 140.3.1esr-1~deb13u1 all [upgradable from: 140.3.0esr-1~deb13u1]
firefox-esr/stable-security 140.3.1esr-1~deb13u1 amd64 [upgradable from: 140.3.0esr-1~deb13u1]
# apt update
Get:1 https://security.debian.org/debian-security trixie-security InRelease [43,4 kB]
Hit:2 https://deb.debian.org/debian trixie InRelease
Get:3 https://deb.debian.org/debian trixie-updates InRelease [47,3 kB]
Get:4 https://security.debian.org/debian-security trixie-security/main amd64 Packages [47,7 kB]
Fetched 138 kB in 1s (122 kB/s)
9 packages can be upgraded. Run 'apt list --upgradable' to see them.
# apt list --upgradable
firefox-esr-l10n-es-ar/stable-security 140.3.1esr-1~deb13u1 all [upgradable from: 140.3.0esr-1~deb13u1]
firefox-esr-l10n-es-cl/stable-security 140.3.1esr-1~deb13u1 all [upgradable from: 140.3.0esr-1~deb13u1]
firefox-esr-l10n-es-es/stable-security 140.3.1esr-1~deb13u1 all [upgradable from: 140.3.0esr-1~deb13u1]
firefox-esr-l10n-es-mx/stable-security 140.3.1esr-1~deb13u1 all [upgradable from: 140.3.0esr-1~deb13u1]
firefox-esr/stable-security 140.3.1esr-1~deb13u1 amd64 [upgradable from: 140.3.0esr-1~deb13u1]
gimp-data/stable-security 3.0.4-3+deb13u1 all [upgradable from: 3.0.4-3]
gimp/stable-security 3.0.4-3+deb13u1 amd64 [upgradable from: 3.0.4-3]
gir1.2-gimp-3.0/stable-security 3.0.4-3+deb13u1 amd64 [upgradable from: 3.0.4-3]
libgimp-3.0-0/stable-security 3.0.4-3+deb13u1 amd64 [upgradable from: 3.0.4-3]
* What was the outcome of this action?
A manual apt update was needed to get the right status.
* What outcome did you expect instead?
Doing it all it one command would be so nice, e.g. apt list --upgradable --update, could run metadata updates, and then list the set of packages for upgrade, so the status is current at the listing time.