fix: extract project as current user on linux

[mayeut]

This allows git to work properly, e.g., versioneer/setuptools_scm with latest git versions.
c.f. pypa/manylinux#1309

e.g. for ninja which uses versioneer when built on quay.io/pypa/manylinux2014_x86_64:latest:

• ninja-0+unknown-py2.py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl without the fix
• ninja-1.10.2.3.post17.dev0+g3a8b005-py2.py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl with the fix

[henryiii]

The downstream projects can fix this too by specifying the git root explicitly, such as in pypa/setuptools-scm#708. But this seems like a good fix, the ownership should not be based on the contents of the tar file.

[henryiii]

This is a fix for main, or for using the latest manylinux manually? I’m assuming older pins in released versions have the older git and are fine?

[mayeut]

This is a fix for main, or for using the latest manylinux manually? I’m assuming older pins in released versions have the older git and are fine?

Pinned images in main are still using older git and are not affected (will be affected once updates kick-in).
Users that are specifying latest manylinux images or custom images are affected (the report in manylinux repo is a cibuildwheel user using custom image based on manylinux, or mayeut/patchelf-pypi#16 with a custom image which is now failing).

[joerick]

For anyone curious:

     --no-same-owner
             (x mode only) Do not extract owner and group IDs.  This is the
             reverse of --same-owner and the default behavior if tar is run as
             non-root.

It seems to me very reasonable ignore ownership here 👍 I guess the UIDs don't even match up between the host and container.