given the legacy build chain I am inclined to assume that the issue lies there rather than in a Python packaging platform-dependency, but I could be wrong!
Seems that you're not @agoose77 as if you download this tar.gz
that is from the built Docker image that successfully installed the same distribution as a wheel, and then docker cp
it inside of Docker containers and try to install it there, I can get it to install as a wheel inside of gitlab-registry.cern.ch/linuxsupport/cc7-base:latest
but not inside of ubuntu:20.04
...where it was built.
My takeaway from this is that the while the tar.gz
file is technically a sdist
$ python -m pip install --upgrade pip twine
$ python -m pip download 'xrootd==5.4.2'
$ twine check xrootd-5.4.2.tar.gz
Checking xrootd-5.4.2.tar.gz: PASSED with warnings
WARNING `long_description_content_type` missing. defaulting to `text/x-rst`.
it needs to be revised to be more robust to the OS it is installed on. Though at this point you should just start shipping wheels.
Maybe someone on the XRootD team (I assume from the git
history that would be @simonmichal) can talk to @henryiii or someone else on the cibuildwheel
team. :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1