On Thu, 22 Sep 2022 19:33:20 -0400 Greg Wooledge wrote:
You've either got a Frankendebian system, or a pin. Or both.
Review your sources.list and sources.list.d/* and see if you've mixed
different branches, or different operating systems.
Or pick a package from the "kept back" list, and do an "apt-cache
policy
pkgname" on it. See whether it's pinned, or has a version that's ahead
of stable, and then try to remember what you did to achieve that state.
It was my thinking as well, but no source.list changes on this system,
no pinning, no apt-mark. Nothing.
Using libsystemd0 as an example, apt-cache policy shown the installed
packages with score 100, and an available update with score 500. Still,
the update was not installed until I manually specified the package on
the apt-get dist-upgrade command line.
Full disclosure: this specific system is an Ubuntu installation. I wrote
here because the issue seems with how apt-get identifies protected
packages, rather than distro-related.
On Fri, 23 Sep 2022 01:48:38 +0100, Peter Hillier-Brook
I've had a similar problem in the recent past with <sudo apt upgrade>.
I resolved it by running Synaptic, which solved the issue with no
reported errors.
I'm running pure Bullseye with no manually pinned packages.
Yep, the issue seems confined to apt-get: issuing aptitude full-upgrade
worked flawlessy.
Regards.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.da...@assyoma.it - i...@assyoma.it
GPG public key ID: FF5F32A8
