Changes
Page history
give another example command for obsolete package
authored
Jun 27, 2025
by
anarcat
Show whitespace changes
Inline
Side-by-side
howto/upgrades.md
View page @
ee5a2a4c
...
@@ -190,15 +190,23 @@ If you want to know which packages are marked as obsolete, you can use the
...
@@ -190,15 +190,23 @@ If you want to know which packages are marked as obsolete, you can use the
following two commands:
following two commands:
apt list "?obsolete"
apt list "?obsolete"
# The following will mainly print the same list as above, but there might be
apt list "?narrow(?installed, ?not(?codename($(lsb_release -c -s | tail -1))))"
# some more in its list.
The authoritative source for the alert, however, is the
`apt_info`
collector, which might differ from the above:
DEBUG=1 /usr/share/prometheus-node-exporter-collectors/apt_info.py >/dev/null
DEBUG=1 /usr/share/prometheus-node-exporter-collectors/apt_info.py >/dev/null
Check the state of each package with
`apt policy $package`
to determine what
Check the state of each package with
`apt policy $package`
to determine what
needs to be done with it. If most cases, the packages can just be purged, but
needs to be done with it. If most cases, the packages can just be purged, but
maybe not if they are obsolete because an apt source was lost. In that latter
maybe not if they are obsolete because an apt source was lost.
case, you may want to check out why the source was removed and make sure to
bring it back.
In that latter case, you may want to check out why the source was
removed and make sure to bring it back. Sometimes it means downgrading
the package to an earlier version, in case we used an incorrect
backport (
`apt.postgresql.org`
packages, suffixed with
`pgdg`
are in
that situation, as their version is higher than
`debian.org`
packages).
## Out of date package lists
## Out of date package lists
...
...
...
...