[CI][Packaging] Manylinux tags mismatch between generated artifact and validation on `wheel-manylinux-2014-cp313`

[raulcd]

Describe the bug, including details regarding any error messages, version, and platform.

Our nightly jobs for:

• wheel-manylinux-2014-cp313-cp313-amd64
• wheel-manylinux-2014-cp313-cp313t-arm64

have started failing with a mismatch validating the uploaded artifact. There seems to be a difference between the name of the file for the uploaded artifact:

INFO:crossbow:Uploading asset `pyarrow-21.0.0.dev152-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl` with mimetype application/zip and size 42536300...

and the one we try to validate:

 [PENDING] wheel-manylinux-2014-cp313-cp313-amd64                 uploaded 0 / 1
 └ https://github.com/ursacomputing/crossbow/actions/runs/15387735681/job/43289946849
pyarrow-21.0.0.dev152-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl [PENDING]

+pyarrow-21.0.0.dev152-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
-pyarrow-21.0.0.dev152-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Component(s)

Continuous Integration, Packaging

[raulcd]

It seems we are generating the wrong name, the uploaded wheel for 20.0.0 on PyPI is:

• pyarrow-20.0.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

[raulcd]

Ok, this seems to be just an ordering issue with the platform tag due to a new version of auditwheel due to:

• feat: detect architecture/libc from wheel pypa/auditwheel#548

[kou]

Issue resolved by pull request 46705
#46705