Yep, I ran into this issue long ago on AIX, which is due to the filenames in the TAR, not the tar filename.

-Donald


Kevan Miller wrote:

On Aug 13, 2008, at 7:15 AM, Johannes Weberhofer, Weberhofer GmbH wrote:

It's not the filename but the content, I guess. I get the following error message on unpacking on linux.

# tar -xzf geronimo-tomcat6-javaee5-2.1.2-bin.tar.gz
tar: A lone zero block at 199022



I have got a similar message with version 2.1.1, too.

Johannes,
Thanks for pointing this out. Mal's error message looked different (because it's AIX, perhaps?). So, we may have gotten distracted. Or perhaps there is an issue with tar on AIX... Donald, have you tried untarring on AIX?

The "long zero block" error messages can be ignored. There's a Maven bug -- http://jira.codehaus.org/browse/MASSEMBLY-302 (I believe) which causes these. We should put a note about this on our Download site.

As far as I know, there's no content difference between our tar.gz and zip formats. We used to change EOL-characters depending on the archive format. I don't believe we do this any longer.

--kevan


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to