for gnu tar this command
tar --numeric-owner -tvf your-archive
shows
-rwxrwxrwx 63018/4294967295 24597 2009-09-04 19:58:57 ./bug.sh
^^^^^^^^^^
that gid corresponds to the header bytes
200 \0 \0 \0 377 377 377
which is not a valid ascii octal number
gnu tar merrily convert that anyway and fails, showing -1
so I'm not interested that I didn't get your gid
I'm interested in knowing how the bytes for gid got corrupted
was it the gnu tar write, or the posting process, or unposting process
why? because if the is a widespread gnu tar bug then I will have to
add a workaround to ast pax to handle it (with a warning)
I know this is off course for your ksh bug
thanks for following up
On Thu, 10 Sep 2009 10:21:10 -0400 wrote:
> That was a simple tar cvf TAR_FILE TARRED_FILE, but not as the root user
> (as my own ID). I would not expect my UID or GID to necessarily be
> present on your server, but that doesn't normally cause a problem when
> running tar -x as an unprivileged user.
_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers
