Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The latest release cannot be extracted with the --same-owner option #300

Open
Iksas opened this issue Sep 6, 2024 · 2 comments
Open

The latest release cannot be extracted with the --same-owner option #300

Iksas opened this issue Sep 6, 2024 · 2 comments

Comments

@Iksas
Copy link

Iksas commented Sep 6, 2024

Expected behavior:

The release tarball can be extracted with the --same-owner option. This works fine in release PPI-1.278:

wget https://cpan.metacpan.org/authors/id/O/OA/OALDERS/PPI-1.278.tar.gz
gzip -dk PPI-1.278.tar.gz
tar --same-owner -xvf PPI-1.278.tar

However, in release PPI-1.279, the following steps fail:

wget http://www.cpan.org/authors/id/M/MI/MITHALDU/PPI-1.279.tar.gz
gzip -dk PPI-1.279.tar.gz
tar --same-owner -xvf PPI-1.279.tar

Here's a sample of the resulting errors:

tar --same-owner -xvf PPI-1.279.tar
[...]
PPI-1.279/xt/DepReqs.pm
tar: PPI-1.279/xt/DepReqs.pm: Cannot change ownership to uid 197609, gid 197609: Operation not permitted
PPI-1.279/xt/meta.t
tar: PPI-1.279/xt/meta.t: Cannot change ownership to uid 197609, gid 197609: Operation not permitted
PPI-1.279/xt/pmv.t
tar: PPI-1.279/xt/pmv.t: Cannot change ownership to uid 197609, gid 197609: Operation not permitted
PPI-1.279/xt/release/
PPI-1.279/xt/release/changes_has_content.t
tar: PPI-1.279/xt/release/changes_has_content.t: Cannot change ownership to uid 197609, gid 197609: Operation not permitted
tar: PPI-1.279/xt/release: Cannot change ownership to uid 197609, gid 197609: Operation not permitted
tar: PPI-1.279/xt: Cannot change ownership to uid 197609, gid 197609: Operation not permitted
tar: PPI-1.279: Cannot change ownership to uid 197609, gid 197609: Operation not permitted
tar: Exiting with failure status due to previous errors

This leads to problems when pulling certain docker images with podman, as described in linuxserver/docker-smokeping#181.

@wchristian
Copy link
Member

Hm, seems there are some platform-specific aspects to the release process. I'll look into it tomorrow.

@wchristian
Copy link
Member

Ok, i looked at it and i need more explanations.

I compared the permissions on the files and the only thing in 1.279 that's missing is some files don't have world-read perms; and the owner names differ.

I don't understand how that leads to tar being unable to change ownership.

I am also baffled as to why you would try to unpack a tarball while retaining an ownership user that doesn't exist on your system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants