apt-upgrade (Bullseye) shows 1 pkg not upgraded

[Jim Popovitch]

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.


-Jim P.

[Lance Simmons]

apt list --upgradeable

[Jim Popovitch]

On Tue, 2021-08-10 at 12:37 -0500, Lance Simmons wrote:
> apt list --upgradeable

:(

~$ apt list --upgradeable
Listing... Done


Thanks for suggesting that though.

-Jim P.

[john doe]

$ apt-get -sV full-upgrade


-s = simulate
-V = verbose

--
John Doe

[Jim Popovitch]

Thanks, unfortunately still nothing. :(

~$ apt-get -sV full-upgrade

Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

I'm beginning to wonder if this is just a bug in apt-get, I know of
nothing on this small server that has a pending upgrade.

-Jim P.

[Greg Wooledge]

On Tue, Aug 10, 2021 at 01:57:13PM -0400, Jim Popovitch wrote:
> ~$ apt-get -sV full-upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Have you tried Google yet?

https://unix.stackexchange.com/questions/615676/0-upgraded-0-newly-installed-0-to-remove-and-1-not-upgraded-how-can-i-upgrade

https://www.linuxquestions.org/questions/debian-26/%271-package-not-upgraded%27-conundrum-4175620661/

Perhaps one of those will point the way. (What do you have pinned,
and what third-party repositories do you have configured?)

[Jim Popovitch]

Nothing pinned. I did see the first link you posted, but not the 2nd
one, although neither seems to apply to what I'm experiencing. No
pinning, no custom apt settings, etc.

$ cat /etc/apt/sources.list
deb [trusted=yes] http://ftp.us.debian.org/debian bullseye main
deb [trusted=yes] http://ftp.us.debian.org/debian bullseye-updates main
deb [trusted=yes] http://security.debian.org bullseye-security main

$ apt-get clean && apt-get update && apt-get upgrade && apt-get -sV
full-upgrade
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.us.debian.org/debian bullseye InRelease

Hit:3 http://ftp.us.debian.org/debian bullseye-updates InRelease
Reading package lists... Done

Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Thanks for at least offering suggestings, etc.

-Jim P.

[john doe]

As the cmd works for me I'm not sure this is a bug in 'apt-get' but
maybe a pkg on 'hold'.

--
John Doe

[Jim Popovitch]

No pining, nothing on hold that I can see, no custom config, etc. apt-
get works for me, i can install and --purge remove, etc, just that one
dangling "not upgraded" status that befuddles me.

Thanks,

-Jim P.

[didier gaumet]

Hello,

If for example you have set up unattended-upgrades and installed apt-
listbugs, then when unattended-upgrades runs, apt-listbugs
automatically pins (-30000) upgradable packages that are affected by
bugs in order for them to be hold until a fix. They are automatically
de-pinned when bugs are fixed. Such pinned packages appear in
/etc/apt/preferences.d/apt-listbugs
(look at apt-listbugs manpage for details)

[David]

On Wed, 11 Aug 2021 at 03:32, Jim Popovitch <j...@k4vqc.com> wrote:

> apt-upgrade (Bullseye) shows 1 pkg not upgraded

> How can I determine what the "1 not upgraded" package might be?

Hi, I dunno if this message will be of any use, because other
suggestions indicate that this might be due to pinning or other
issues that I have no knowledge of.

But something simple that I would check in this situation would
be that I would run interactive 'aptitude' as root.

If it starts up with its "Upgradeable Packages" top line
highlighted then you could press the '[' key to expand that
line and it will show the packages in question.

If not then just press 'q' to close the tab and quit.

By the way, I'm giving the keyboard hints in case you have
not used it before, to save you reading the manual,

[Greg Wooledge]

On Wed, Aug 11, 2021 at 08:27:03AM +1000, David wrote:
> On Wed, 11 Aug 2021 at 03:32, Jim Popovitch <j...@k4vqc.com> wrote:
>
> > apt-upgrade (Bullseye) shows 1 pkg not upgraded
>
> > How can I determine what the "1 not upgraded" package might be?
>
> Hi, I dunno if this message will be of any use, because other
> suggestions indicate that this might be due to pinning or other
> issues that I have no knowledge of.

The OP claimed they have nothing pinned, but presented no evidence to
support this claim. Perhaps they thought that because they didn't
explicitly *pin* anything themselves, there must not be anything
pinned on their system. So why bother looking?

They should at least look.

grep -ri pin /etc/apt

would be a reasonable starting point.

(Also, catting /etc/apt/sources.list is not sufficient to show the
absence of third-party repositories. There's also a sources.list.d
directory.)

[Jim Popovitch]

On Tue, 2021-08-10 at 18:59 -0400, Greg Wooledge wrote:
> On Wed, Aug 11, 2021 at 08:27:03AM +1000, David wrote:
> > On Wed, 11 Aug 2021 at 03:32, Jim Popovitch <j...@k4vqc.com> wrote:
> >
> > > apt-upgrade (Bullseye) shows 1 pkg not upgraded
> >
> > > How can I determine what the "1 not upgraded" package might be?
> >
> > Hi, I dunno if this message will be of any use, because other
> > suggestions indicate that this might be due to pinning or other
> > issues that I have no knowledge of.
>
> The OP claimed they have nothing pinned, but presented no evidence to
> support this claim. Perhaps they thought that because they didn't
> explicitly *pin* anything themselves, there must not be anything
> pinned on their system. So why bother looking?
>
> They should at least look.

I did.

>
> grep -ri pin /etc/apt

That's exactly how I did look.

>
> would be a reasonable starting point.
>
> (Also, catting /etc/apt/sources.list is not sufficient to show the
> absence of third-party repositories. There's also a sources.list.d
> directory.)

If there was anything in sources.list.d I would have showed it.

Absence of absence is something no one should ponder.

-Jim P.

[David Wright]

On Tue 10 Aug 2021 at 14:09:27 (-0400), Jim Popovitch wrote:
> On Tue, 2021-08-10 at 14:00 -0400, Greg Wooledge wrote:
> > On Tue, Aug 10, 2021 at 01:57:13PM -0400, Jim Popovitch wrote:
> > > ~$ apt-get -sV full-upgrade
> > > Reading package lists... Done
> > > Building dependency tree... Done
> > > Calculating upgrade... Done
> > > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> >
> > Have you tried Google yet?
> >
> > https://unix.stackexchange.com/questions/615676/0-upgraded-0-newly-installed-0-to-remove-and-1-not-upgraded-how-can-i-upgrade
> >
> > https://www.linuxquestions.org/questions/debian-26/%271-package-not-upgraded%27-conundrum-4175620661/
> >
> > Perhaps one of those will point the way. (What do you have pinned,
> > and what third-party repositories do you have configured?)
> >
>
> Nothing pinned. I did see the first link you posted, but not the 2nd
> one, although neither seems to apply to what I'm experiencing. No
> pinning, no custom apt settings, etc.
>
> $ cat /etc/apt/sources.list
> deb [trusted=yes] http://ftp.us.debian.org/debian bullseye main
> deb [trusted=yes] http://ftp.us.debian.org/debian bullseye-updates main
> deb [trusted=yes] http://security.debian.org bullseye-security main

deb [trusted=yes] http://security.debian.org/debian-security bullseye-security main

is what I would expect to see here. (I don't have a system availble to
test the effect of omitting debian-security)

> $ apt-get clean && apt-get update && apt-get upgrade && apt-get -sV
> full-upgrade
> Hit:1 http://security.debian.org bullseye-security InRelease
> Hit:2 http://ftp.us.debian.org/debian bullseye InRelease
> Hit:3 http://ftp.us.debian.org/debian bullseye-updates InRelease
> Reading package lists... Done
> Reading package lists... Done
> Building dependency tree... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> Reading package lists... Done
> Building dependency tree... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
>
> Thanks for at least offering suggestings, etc.

Cheers,
David.

[Cindy Sue Causey]

On 8/10/21, Jim Popovitch <j...@k4vqc.com> wrote:
> On Tue, 2021-08-10 at 18:59 -0400, Greg Wooledge wrote:
>>
>> The OP claimed they have nothing pinned, but presented no evidence to
>> support this claim. Perhaps they thought that because they didn't
>> explicitly *pin* anything themselves, there must not be anything
>> pinned on their system. So why bother looking?
>>
>> They should at least look.
>
> I did.
>
>>
>> grep -ri pin /etc/apt
>
> That's exactly how I did look.

What about something that didn't fully upgrade for whatever reason? I
haven't encountered that in a few weeks so I'd already forgotten
whether it was "apt(-get)" or "dpkg". Quick search brought up this
[0]:

"dpkg --configure -a" configure all partially installed packages

If that has already been tried, my apologies.

[0] https://www.debian.org/doc/manuals/debian-reference/ch02.en.html
See under "2.4.1. Advanced package management operations with commandline"

Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

[Andrei POPESCU]

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

Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser

[Jim Popovitch]

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.