Marc-Andre Lemburg added the comment:
Indeed, there are two issue with the .tgz file:
* it uses "staff" as group for all files (which will likely exist on some
systems), but this appears unrelated in you case
* all subdirs have go-x set, which prevents changing into the dir if you're
not in the staff group, which is more of an issue
In your case, the system does not seem to have a staff group, but the numeric
IDs stored in the .tgz file map to another user/group. As a result, you don't
When creating .tgz files for redistribution, it's usually better to explicitly
set the owner and group to either something that's not likely to exist on
target machines or to root.root via --owner=root --group=root.
As user, you can work around this by using the options --no-same-owner
--no-same-permissions when extracting the archive.
Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list