I'm wondering if anyone else has noticed this problem.
When devel/jdk/1.5 tries to extract the xalan-j_2_7_0-bin.tar.gz archive
using gtar, it actually fails but since gtar isn't kind enough to
actually return the error, the build continues.
$ make extract
...
>> (SHA256) jdk-1_5_0_13-fcs-src-b05-jrl-25_sep_2007.jar: OK
>> (SHA256) jdk-1_5_0_13-fcs-bin-b05-jrl-25_sep_2007.jar: OK
>> (SHA256) bsd-jdk15-patches-7.tar.bz2: OK
>> (SHA256) jdk-1_5_0_13-solaris-i586.tar.Z: OK
>> (SHA256) xalan-j_2_7_0-bin.tar.gz: OK
...
===> Extracting for jdk-1.5.0.13
/usr/local/bin/gtar: A lone zero block at 121752
The file itself is fine. It passes sha256 test as well as manual
verification via the pgp/gpg sig. And yes, I've tried redownloading a
few times from both available sources:
http://www.apache.org/dist/xml/xalan-j/binaries/
http://archive.apache.org/dist/xml/xalan-j/
Our tar(1) also dies but returns the error, so it kills the build.
# tar xzf xalan-j_2_7_0-bin.tar.gz
tar: Invalid header, starting valid header search.
tar: End of archive volume 1 reached
I've also tried using gtar 1.7 from -STABLE as well as the updated gtar
1.9 port from -CURRENT.
A more clear example of the return value problem:
# tar xzf xalan-j_2_7_0-bin.tar.gz && echo Hello Nurse!
tar: Invalid header, starting valid header search.
tar: End of archive volume 1 reached
#
# gtar xzf xalan-j_2_7_0-bin.tar.gz && echo Hello Nurse!
gtar: A lone zero block at 121752
Hello Nurse!
#
Is there some magic tar/gtar work-around to extract this archive
correctly?
