>>>>> "BM" == Bob McConnell <r...@cbord.com> writes:

  BM> From: Uri Guttman
  >> i will assume the tarball from cpan is in good shape. so the issues
  >> seems to be you have a broken unzipping of a tar.gz file. can you try
  >> unzipping another cpan module or any tgz file? this would verify my
  >> conjecture or not. can you install a gnu or other real tar utility?
  >> cygwin? does winblows unzip handle tarballs correctly in general?

  BM> Camelbox installed the GNU tar and gzip. Both appear to be working
  BM> correctly with Test-Harness-3.17.tar.gz and earlier builds.

  BM> I went directly to cpan.org and have downloaded each Test-Harness
  BM> tarball back to 3.17. That is the last one with valid path information
  BM> in it. 3.17_01 through 3.21 all come up with no paths in both WinZip and
  BM> these GNU utilities. But neither tool has a problem with
  BM> Test-Harness-3.17.tar.gz, Bundle-CPAN-1.858.tar.gz, CPAN-1.9402.tar.gz
  BM> or Net-Pcap-0.16.tar.gz.

  BM> It is obvious that something has changed. But how do I determine what?

i just downloaded and unzipped harness 3.17 and 3.21 and both have full
trees. so the tarballs are fine as i expected. the question is why is
your tar and gzip failing on the recent harness modules but not
others. try this command on a know working tarball and one that breaks:

        tar zxvf Test-Harness-3.17.tar.gz

the output should show all the paths as the files are extracted. i am
assuming the camelbones tools work the same as the normal gnu ones. if
you don't get a nice looking listing of the paths, something very odd is
happening. the only last idea is to upgrade camelbones itself.

uri

-- 
Uri Guttman  ------  u...@stemsystems.com  --------  http://www.sysarch.com --
-----  Perl Code Review , Architecture, Development, Training, Support ------
---------  Gourmet Hot Cocoa Mix  ----  http://bestfriendscocoa.com ---------

-- 
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/


Reply via email to