X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
X-VirusChecked:	Checked
X-Env-Sender:	JAnderson AT rocketsoftware DOT com
X-Msg-Ref:	server-8.tower-98.messagelabs.com!1252934524!5714457!1
X-StarScan-Version:	6.1.3; banners=-,-,-
From:	Judy Anderson <JAnderson AT rocketsoftware DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date:	Mon, 14 Sep 2009 09:21:51 -0400
Subject:	Strange tar error with --format=ustar: value 4294967295 out of gid_t range 0..2097151
Message-ID:	<6134CDF9E3C17546BE1C9D525BDEEF95F07EEBEDF0@HQMAIL.rocketsoftware.com>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I need to send a collection of files to a Z/OS machine from a windows machi=
ne.  When we were on Windows 2000, we just used "pax".  But apparently Micr=
osoft has discontinued pax in Win2003.  So we searched for a solution.  Cyg=
win tar SAID it would produce pax format files, but the Z/OS machine doesn'=
t like them if they contain long file names.  However, tar will ALSO produc=
e ustar format, and pax on the mainframe is able to read those.  So we were=
 cooking with gas.

Except on my usual development machine, where I get the error:

E:\yduJ> c:\cygwin\bin\tar cf foo.tar --format=3Dustar foo
/usr/bin/tar: value 4294967295 out of gid_t range 0..2097151
/usr/bin/tar: Exiting with failure status due to previous errors

It works FINE on the official build machine, just not MINE.  So I reran Cyg=
win setup and reinstalled and rebooted.  No help.  I started making all sor=
ts of wrong guesses about this.  Eventually I discovered a directory on my =
machine which DID tar up.  Then I realized what was different:  I had made =
or edited at least one file USING EMACS in all the other directories.  Yep,=
 added a file using emacs and the new directory couldn't be tarred either.

I went and got emacs version 23.1.1 from gnu hoping it would be better, but=
 it's not.  Tar is version 1.21.

I figured out a workaround, which is to say --group=3D1 to specify groups, =
so I'm OK now, but it would be nice not to need that, since it's only for m=
y development machine.  The build machine of course works only on the cvs c=
hecked out files and does not require this workaround.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -