Re: How to run 'pkg upgrade' as requested by apt?

[Chris Green <cl@isbd.net>]

Michael Kjörling <c9bc136c6063@ewoof.net> wrote:
> On 28 Oct 2024 14:36 +0000, from cl@isbd.net (Chris Green):
> > I recently did an 'apt update' and 'apt upgrade' on my bookworm system.
> > 
> > In the 'apt upgrade' output there is the following:-
> > 
> >     Setting up python (3.12.7-1) ...
> 
> Please double-check that it's really Bookworm.
> 
> If you believe it is, then show us the full and unmangled output of:
> 
> $ lsb_release -a
> $ sudo grep -rvh '^#' /etc/apt/sources.list* | grep -v '^$'
> 
> It looks like the Python versions shipped in various current Debian
> releases are:
> 
> - Bookworm: Python 3.11 (3.11.2-6+deb12u3) https://packages.debian.org/bookworm/python3.11
> 
> - Trixie: Python 3.12 (3.12.6-1) https://packages.debian.org/trixie/python3.12
> 
> - Sid: Python 3.12 (3.12.7-1 on all but ia64, mips64el, sparc64) https://packages.debian.org/sid/python3.12 
> 
> 
> So short of pulling such a package from elsewhere, the only way I can
> see that you'd get a 3.12.7-1 package version of Python is by running
> Sid. And even then I would expect the package name to be "python3.12",
> not just "python". (The "python3" package in Sid is, somewhat
> curiously, at 3.12.6-1, same as Trixie but different from Sid's
> "python3.12" package.)
> 
Ah, sorry, my mistake entirely.  I was running 'apt update' and 'apt
upgrade' on several systems nearly all of which are now running Debian
Bookworm.  But the message I reported here was on the odd one out, an
Android mobile phone running Termux.

I'll quickly disappear back under my stone.....

-- 
Chris Green
·