Bug #3962 for Archive-Tar: Corrupt tar dumped to screen in V 0.23

Thu Oct 02 07:28:55 2003 Guest - Ticket created

Subject:

Corrupt tar dumped to screen in V 0.23

When I run Archive::Tar on the 1.3Mb corrupt file: http://savage.net.au/Bin1.tgz I get a minute's worth of bells, suggesting the file is being dumped in binary to the screen. I would prefer nothing be written to the screen, actually, a la Archive::Zip. It is sufficient that new() returns undef on failure. Code: my($tgz) = Archive::Tar -> new($_, 1); print "Invalid tgz file: $File::Find::name. \n" if (! $tgz);

Thu Oct 02 12:03:43 2003 kane [...] dwim.org - Correspondence added

Date:	Thu, 2 Oct 2003 09:08:13 -0700 (PDT)
From:	"Jos I. Boumans" <kane [...] dwim.org>
To:	Guest via RT <bug-Archive-Tar [...] rt.cpan.org>
Subject:	Re: [cpan #3962] Corrupt tar dumped to screen in V 0.23
RT-Send-Cc:

Show quoted text

> When I run Archive::Tar on the 1.3Mb corrupt file: > http://savage.net.au/Bin1.tgz > I get a minute's worth of bells, suggesting the file is being dumped in binary to the screen. > I would prefer nothing be written to the screen, actually, a la Archive::Zip. It is sufficient that new() returns undef on failure.

try this again with the latest version, 1.05 and see if the problem persists.B Show quoted text

> Code: > my($tgz) = Archive::Tar -> new($_, 1); > print "Invalid tgz file: $File::Find::name. \n" if (! $tgz);

this code will not actually run though...

Sun Oct 05 08:45:04 2003 kane [...] cpan.org - Correspondence added

If you don't want the output, as requested, please set the global variable: $Archive::Tar::WARN = 0; and it will not warn about corrupt chunks/checksums. I've added an extra check before the checksum check that investigates the magic string, which will catch this slightly earlier. As this is really a non-bug, i consider this issue closed.

Sun Oct 05 08:45:06 2003 kane [...] cpan.org - Status changed from 'new' to 'resolved'