Skip Menu |

This queue is for tickets about the HTML-Scrubber CPAN distribution.

Report information
The Basics
Id: 11096
Status: resolved
Priority: 0/
Queue: HTML-Scrubber

People
Owner: Nobody in particular
Requestors: mateo [...] littleredbat.net
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Date: Wed, 19 Jan 2005 14:58:36 -0600
From: Mateo Kellog <mateo [...] littleredbat.net>
To: bug-HTML-Scrubber [...] rt.cpan.org
Subject: improperly formed tar file
Hi. I've just downloaded HTML::Scrubber version .08 and discovered that the tar file is misformed. Instead of putting all the contents of the file (README, *.t, etc) into HTML-Scrubber-0.08/, it puts those file in the current directory. This also breaks installation using CPAN.pm. Cheers, Matt +--------------------------------------------------------------------------+ | Mateo Kellog : mateo @ littleredbat.net | | | | Use PGP : http://www.gnupg.org | | My Key : http://www.littleredbat.net/~mk/pgp.html | +--------------------------------------------------------------------------+
Download (untitled)
application/pgp-signature 187b

Message body not shown because it is not plain text.

From: Matt
I'm seeing this problem on FreeBSD but not on linux. Here's my console log on FreeBSD: mk@h2o ~/tmp> tar -xvzf HTML-Scrubber-0.08.tar.gz HTML-Scrubber-0.08 Changes LICENSE Makefile.PL MANIFEST MANIFEST.SKIP META.yml README Scrubber.pm t 01_use.t 02_basic.t 03_more.t 04_style_script.t 05_pi_comment.t 06_scrub_file.t 07_booleans.t mk@h2o ~/tmp> ll total 188 -rw-r--r-- 1 mk mk 286 Oct 29 2003 01_use.t -rw-r--r-- 1 mk mk 4728 Oct 29 2003 02_basic.t -rw-r--r-- 1 mk mk 1203 Oct 31 2003 03_more.t -rw-r--r-- 1 mk mk 770 Oct 31 2003 04_style_script.t -rw-r--r-- 1 mk mk 742 Oct 31 2003 05_pi_comment.t -rw-r--r-- 1 mk mk 1868 Nov 2 2003 06_scrub_file.t -rw-r--r-- 1 mk mk 1508 Apr 1 2004 07_booleans.t -rw-r--r-- 1 mk mk 1557 Apr 1 2004 Changes drwxr-xr-x 2 mk mk 512 Apr 1 2004 HTML-Scrubber-0.08 -rw-r--r-- 1 mk mk 17073 Apr 1 2004 HTML-Scrubber-0.08.tar.gz -rw-r--r-- 1 mk mk 20928 Aug 24 2003 LICENSE -rw-r--r-- 1 mk mk 271 Mar 18 2004 MANIFEST -rw-r--r-- 1 mk mk 247 Apr 18 2003 MANIFEST.SKIP -rw-r--r-- 1 mk mk 425 Apr 1 2004 META.yml -rw-r--r-- 1 mk mk 811 Mar 18 2004 Makefile.PL -rw-r--r-- 1 mk mk 499 Oct 29 2003 README -rw-r--r-- 1 mk mk 20268 Apr 1 2004 Scrubber.pm drwxr-xr-x 2 mk mk 512 Apr 1 2004 t [mateo@littleredbat.net - Wed Jan 19 16:36:51 2005]: Show quoted text
> Hi. > > I've just downloaded HTML::Scrubber version .08 and discovered that
the tar Show quoted text
> file is misformed. Instead of putting all the contents of the file
(README, Show quoted text
> *.t, etc) into HTML-Scrubber-0.08/, it puts those file in the current > directory. This also breaks installation using CPAN.pm. > > Cheers, > Matt > >
+--------------------------------------------------------------------------+ Show quoted text
> | Mateo Kellog : mateo @ littleredbat.net
| Show quoted text
> |
| Show quoted text
> | Use PGP : http://www.gnupg.org
| Show quoted text
| Show quoted text
>
+--------------------------------------------------------------------------+ Show quoted text
>
I don't know what to tell you, works for me :( I'd contact someone at FreeBSD , someone who works on tar
From: m.nooning [...] comcast.net
On Wed Jan 19 21:54:04 2005, guest wrote: Show quoted text
> I don't know what to tell you, works for me :( > I'd contact someone at FreeBSD , someone who works on tar
The mystery deepens. I have the exact same problem when in a Windows Command prompt box, using the command "tar -xf". That is, it outputs all to the current directory instead of to an HTML-Scrubber-0.08 directory. That never happened before. I use the tar from UnxUtils, and I have used it with many dozens of modules without a problem. The problem does not lie with the tar.exe program .... .... or does it? I also have cygwin installed, which I rarely use since I caught on to UnxUtils. I went to a cygwin shell and issued the same command. It worked perfectly. I have no idea why one tar would work but not the other. Neither have ever failed before. .... there is always something, isn't there? ...
New packaging in next release will fix this (appears to be down to an odd windows packager that the previous maintainer was using).