-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to David Mastronarde on 2/18/2006 10:55 PM:
With CYGWIN set to binmode, tar fails on the archive of DOS files
created under nobinmode.
With CYGWIN set to nobinmode, tar fails on the archives of DOS files
created under either mode.
This happens on both a Windows 2000 machine with cygwin 1.5.19-4 and
a Windows XP machine with 1.5.18-1.
In fact, the archive of DOS files created under nobinmode must be bad
since it fails to untar under Linux and OSX also. All the other
archives are OK by this test.
Well, nobinmode is documented as opening pipes in text mode
(http://cygwin.com/cygwin-ug-net/using-cygwinenv.html), and tar uses a
pipe to the compression program, so I'm not surprised (text mode has the
nasty habit of corrupting binary data, and tar uses binary data). I
personally never use nobinmode (making pipes non-binary is just ASKING for
problems, as you just proved), but I will see about trying to pinpoint yet
one more location in tar where I should consider forcing binary mode. But
don't expect it to be my highest priority - you should be using binmode
(or nothing at all, since $CYGWIN defaults to binmode).
tar 1.15.1-2
BTW, tar is at 1.15.1-3, consider upgrading (although it won't help for
your particular testcase).
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
volunteer cygwin tar maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD+fid84KuGfSFAYARApHWAJ4yAC0wIf/InE8sCLbc92nE4oIJXwCfQVcZ
4AqufY340uhBuK/QIeVHcFU=
=jhnP
-----END PGP SIGNATURE-----