On Mon, 2021-08-30 at 21:53 +0300, Andrei POPESCU wrote: > On Ma, 10 aug 21, 13:32:09, Jim Popovitch wrote: > > How can I determine what the "1 not upgraded" package might be? > > > > > > ~$ apt-get update > > Hit:1 http://ftp.us.debian.org/debian bullseye InRelease > > Hit:2 http://security.debian.org bullseye-security InRelease > > Hit:3 http://ftp.us.debian.org/debian bullseye-updates InRelease > > Reading package lists... Done > > > > ~$ apt-get upgrade > > Reading package lists... Done > > Building dependency tree... Done > > Calculating upgrade... Done > > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. > > > > > > ~$ apt-get dist-upgrade > > Reading package lists... Done > > Building dependency tree... Done > > Calculating upgrade... Done > > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. > > A bit late to the party... > > If pinning is the issue, the definitive place to check that is always > the output of 'apt policy' (with no package)[1]. > > > If that doesn't provide any new information you could ask deity ;) > > https://lists.debian.org/deity/ > > > [1] It's also a very good way to check your pinning actually works
There was nothing pinned, but the issue did go away sometime in the week before Bullseye was released. I'm convinced it was a mirror/cache issue. -Jim P.
