Author lemburg
Recipients Dave_Anderson, lemburg
Date 2017-02-16.08:52:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487235133.83.0.168380059764.issue29574@psf.upfronthosting.co.za>
In-reply-to
Content
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 get access.

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.
History
Date User Action Args
2017-02-16 08:52:13lemburgsetrecipients: + lemburg, Dave_Anderson
2017-02-16 08:52:13lemburgsetmessageid: <1487235133.83.0.168380059764.issue29574@psf.upfronthosting.co.za>
2017-02-16 08:52:13lemburglinkissue29574 messages
2017-02-16 08:52:13lemburgcreate