Python not yet updated to 3.11, breaking all python packages not on ALHP mirrors #180

New Issue

Closed

opened 2023-05-05 09:29:24 +02:00 by phundrak · 4 comments

phundrak commented

2023-05-05 09:29:24 +02:00

Arch Linux updated a few days ago to Python 3.11, updating in the process the dependency of all python packages not contained in the ALHP mirrors to Python 3.11.

However, none of the x86-64-v3 mirrors package it, staying at Python 3.10.10 and breaking all python packages contained only in the vanilla mirrors.

Arch Linux updated a few days ago to Python 3.11, updating in the process the dependency of all python packages not contained in the ALHP mirrors to Python 3.11. However, none of the x86-64-v3 mirrors package it, staying at Python 3.10.10 and breaking all python packages contained only in the vanilla mirrors.

BertalanD commented

2023-05-05 10:53:47 +02:00

Contributor

To add to this: there are some packages which had their pkgrel bumped for being rebuilt against Python 3.11. Some of these seem to have been already rebuilt on ALHP even though Python itself hasn't been updated here:

capstone
cython
dtc
i2c-tools
libftdi
libibus
libnewt
libvirt-python
ninja
probably a lot of other packages; these are just the ones that show up as updated in community-x86-64-v3 for me

To add to this: there are some packages which had their `pkgrel` bumped for being rebuilt against Python 3.11. Some of these seem to have been already rebuilt on ALHP even though Python itself hasn't been updated here: - `capstone` - `cython` - `dtc` - `i2c-tools` - `libftdi` - `libibus` - `libnewt` - `libvirt-python` - `ninja` - probably a lot of other packages; these are just the ones that show up as updated in `community-x86-64-v3` for me

anonfunc commented

2023-05-05 12:48:58 +02:00

Owner

Arch Linux updated a few days ago to Python 3.11, updating in the process the dependency of all python packages not contained in the ALHP mirrors to Python 3.11.

However, none of the x86-64-v3 mirrors package it, staying at Python 3.10.10 and breaking all python packages contained only in the vanilla mirrors.

ALHP builds after Arch releases packages. So this is quite normal and expected, see #77 for example of the last 3.10 rebuild. We still have ~300 packages left, see the package status page for more details.

To add to this: there are some packages which had their pkgrel bumped for being rebuilt against Python 3.11. Some of these seem to have been already rebuilt on ALHP even though Python itself hasn't been updated here:

capstone

cython

dtc

i2c-tools

libftdi

libibus

libnewt

libvirt-python

ninja

probably a lot of other packages; these are just the ones that show up as updated in community-x86-64-v3 for me

This happens if Arch packagers release the package in the repo source tree without it being actually released to it. Sadly some packagers seem to do that quite often. Need to filter those out manually after the first rebuild is finished.

> Arch Linux updated a few days ago to Python 3.11, updating in the process the dependency of all python packages not contained in the ALHP mirrors to Python 3.11. > > However, none of the x86-64-v3 mirrors package it, staying at Python 3.10.10 and breaking all python packages contained only in the vanilla mirrors. ALHP builds after Arch releases packages. So this is quite normal and expected, see https://somegit.dev/ALHP/ALHP.GO/issues/77 for example of the last 3.10 rebuild. We still have ~300 packages left, see the package status page for more details. > To add to this: there are some packages which had their `pkgrel` bumped for being rebuilt against Python 3.11. Some of these seem to have been already rebuilt on ALHP even though Python itself hasn't been updated here: > - `capstone` > - `cython` > - `dtc` > - `i2c-tools` > - `libftdi` > - `libibus` > - `libnewt` > - `libvirt-python` > - `ninja` > - probably a lot of other packages; these are just the ones that show up as updated in `community-x86-64-v3` for me This happens if Arch packagers release the package in the repo source tree without it being actually released to it. Sadly some packagers seem to do that quite often. Need to filter those out manually after the first rebuild is finished.