[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: apt-get dist-upgrade keeping back some packets



On 23/09/2022 00:33, Greg Wooledge wrote:
On Fri, Sep 23, 2022 at 01:04:26AM +0200, Gionatan Danti wrote:
root@localhost:/var/log/apt# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
   grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed libnss-mymachines
libnss-systemd libpam-systemd libpython3-dev libpython3-stdlib libpython3.10
libpython3.10-dev libpython3.10-minimal libpython3.10-stdlib libsystemd0
libudev1
   python3 python3-dev python3-distutils python3-gdbm python3-lib2to3
python3-minimal python3-tk python3.10 python3.10-dev python3.10-minimal
systemd systemd-container systemd-sysv systemd-timesyncd udev
The following packages will be upgraded:
   bind9-dnsutils bind9-host bind9-libs libpcre2-8-0 python3-oauthlib

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.

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.

Peter HB


Reply to: