On Wed, 28 Jul 1999, Chris Nandor wrote: > At 18.33 +0000 1999.07.20, Georg Bauer wrote: > >Hi! > > > >There is a problem with this file. When unpacking or installing, I get > >massive errors in Tar.pm. The output is attached (only part of it, this > >goes on and on until a "out of memory" happens - and I have my allocation > >on 40MB). Anyone any idea what happens? > > > >bye, Georg > > > ># Argument "" isn't numeric in eq. > >File 'Sonstiges:Development:MacPerl ü:site_perl:Archive:Tar.pm'; Line 567 > ># Argument "" isn't numeric in eq. > >File 'Sonstiges:Development:MacPerl ü:site_perl:Archive:Tar.pm'; Line 567 > > No, this appears to be a problem in the tar file. Arved, how did you build > it? The TYPE field in the tar file appears to be empty. There is just a > null where there should be a 0 (to denote that it is a file). > Since it's a .tgz extension, 'targzipme'. This has me confused. I remember downloading the module months ago to check it (something I do as a matter of course), and it was OK. And you'll note on CPAN Testers that Larry checked it out, too. ??? Speaking of which, I uploaded XML-Parser-2.26 a few days ago, I KNOW I used binary mode (because it's in the Perl FTP script I used), but it's corrupted also. Or appears to be. I wish I knew what was going on. :-) Right now I have no confidence that a distribution which unzips on my machine will do so once it's been uploaded, even if I know for certain that I uploaded in binary. Sounds impossible, but... Is it possible that the .tgz extension is allowing some app in the chain someplace to f**k stuff up? I use the profanity advisedly, as .tgz is Windows, and I've been having enough problems with that OS over the past few weeks not to feel very charitable about it. :-) Arved ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org