Description
I have a python package with a dependency on hfst==3.16.0.1, that I am unable to install on an old system.
The problem is essentially replicated as such:
(venv) [neahtta@gtdict neahtta]$ pip install hfst==3.16.0.1
ERROR: Could not find a version that satisfies the requirement hfst==3.16.0.1 (from versions: 3.12.0.2b0, 3.12.1.0b0, 3.12.1.1b0, 3.12.2.2b0, 3.12.2.3b0, 3.12.2.4b0)
ERROR: No matching distribution found for hfst==3.16.0.1The system I am running on:
(venv) [neahtta@gtdict neahtta]$ python --version
Python 3.9.16(venv) [neahtta@gtdict neahtta]$ cat /etc/centos-release
CentOS Linux release 7.9.2009 (Core)(venv) [neahtta@gtdict neahtta]$ uname -a
Linux gtdict.uit.no 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux(venv) [neahtta@gtdict neahtta]$ ldd --version
ldd (GNU libc) 2.17
[[ copyright and authors line cut from output here ]]So from what I understand, pip is correct in that I cannot install hfst==3.16.0.1, because the only built distributions for cpython 3.9 for linux on 64bit x86 are these:
hfst-3.16.0.1-cp39-cp39-manylinux_2_28_x86_64.whl
hfst-3.16.0.1-cp39-cp39-manylinux_2_17_i686.manylinux2014_i686.whl
Whereas what I would need would be something like
hfst-3.16.0.1-cp39-cp39-manylinux_2_17_x86_64.whl
...which does not exist.
Namely, a package would be needed for cpython 3.9, running on x86_64, which supports a glibc-version of maximum version 2.17.
Is my analysis of the problem correct? If so, are there any plans to build such a distribution? Are there any workarounds I could (easily) do? Could I build the distribution myself, and specify an alternate dependency path in pyproject.toml, for example?