auditwheel track pytorch issue https://github.com/pytorch/pytorch/pull/149471

pytorch has reported an issue on aarch64 where they use auditwheel to repair wheels. After 6.3.0, they've reported https://github.com/pytorch/pytorch/pull/149471.

While we're also using auditwheel to repair torch wheels, this do not break our release.

I might be able to look into this later.

Mar 23 '25 13:03 oraluben

I might be able to look into this later.

Mar 27 '25 04:03 pythonpirate963

I've ran into this, but cannot reproduce stably

May 08 '25 02:05 oraluben

The reason is when we have two dependencies: a.so -> b.so -> c.so and a.so -> c.so.

The order to precess dependencies of a.so is random (for from a set): https://github.com/pypa/auditwheel/blob/ff5b63713a98182a5f4c97abb709f47bcc9e3bec/src/auditwheel/lddtree.py#L518

When b.so do not have correct rpath for c.so, and if we process b.so first, _all_libs["c.so"] would not have the path and not updated later.

May 09 '25 09:05 oraluben