Re: what's up with python3.11 on arm?

[Matthias Klose <doko@debian.org>]

On 16.03.24 18:41, Steven Robbins wrote:
> This recent transition has really illuminated how little I know of the dark
> corners of Debian infrastructure...
>
> Some packages (e.g. libcdk5/experimental) aren't buildable on the armel/armhf
> because the build-deps don't install, and in particular:
>
> The following packages have unmet dependencies:
>   libpython3.11 : Depends: libpython3.11-stdlib (= 3.11.8-1) but 3.11.8-3+b1 is
> to be installed
>
> What I can't figure out is: the same python3.11 sources build both
> libpython3.11 and libpython3.11-stdlib - so where does this version skew come
> from?

libpython3.11 is not built anymore, libpython3.11t64 is now built.

> The python build logs for armel/armhf are mysterious in that no buildd nor
> logs are listed.  I presume that's a signal these were manually built somehow?
> Do they just need rebuilding with the dependency version numbers fixed up?  Who
> needs to be notified to fix this?

nobody. it will take a while until everything is rebuilt for 
libpython3.11t64.