Closed mgautierfr closed 2 months ago
I understand the problem as:
Possible solutions:
@mgautierfr I think it's up to you. I can't think of any strong reasons in favor of one or the other. Added this topic to the hackathon (broader topic) should we have not decided by then
The CD fails on this looks like, see https://github.com/kiwix/kiwix-build/actions/runs/9387683596/job/25851190286#step:6:325 ... and https://download.openzim.org/release/libzim/libzim_linux-x86_64-manylinux-9.2.1-1.tar.gz missing
@mgautierfr Can we please fis this regression?
This is a tracking issue to move out of bionic build.
We still need to build libzim on bionic because we need to compile on glibc <= 2.28. This is enforced by the python "platform" definition and the last available platform is
manylinux_2_28
(See original issue https://github.com/kiwix/kiwix-build/issues/595).However:
There was the deadsnake ppa (https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa) to install a "recent" python 3.8 on Bionic but it seems the repository for Bionic is no more (probably with Bionic's eol)
This means that kiwix-build is stuck with python 3.6, a 6 years old dead version.
A recent issue on manylinux is tracking the
manylinux_2_34
status : https://github.com/pypa/manylinux/issues/1585. Hopefully we will able to move to a more recent version of ubuntu soon.Another way is to build libzim directly using
manylinux_2_28
as the image contains python up to 3.12