Skip Menu |

This queue is for tickets about the CatalystX-Component-Traits CPAN distribution.

Report information
The Basics
Id: 91922
Status: resolved
Worked: 15 min
Priority: 0/
Queue: CatalystX-Component-Traits

People
Owner: Nobody in particular
Requestors: chisel [...] chizography.net
Cc:
AdminCc:

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



Subject: Using bsdtar confuses gnutar and CPAN

Message body is not shown because it is too large.

Subject: Re: [rt.cpan.org #91922] Using bsdtar confuses gnutar and CPAN
Date: Tue, 7 Jan 2014 10:29:34 -0800
To: bug-CatalystX-Component-Traits [...] rt.cpan.org
From: Rafael Kitover <rkitover [...] gmail.com>

Message body is not shown because it is too large.

Message body is not shown because it is too large.

Subject: Re: [rt.cpan.org #91922] Using bsdtar confuses gnutar and CPAN
Date: Tue, 7 Jan 2014 10:39:22 -0800
To: bug-CatalystX-Component-Traits [...] rt.cpan.org
From: Rafael Kitover <rkitover [...] gmail.com>

Message body is not shown because it is too large.

Message body is not shown because it is too large.

On Tue Jan 07 18:39:39 2014, rkitover@gmail.com wrote: Show quoted text
> > I have one question, who the fuck is NETAPORTER and why is he > > releasing my > > fucking module?
Thank you for your polite enquiry. NETAPORTER is an online fashion retail website. They are not 'releasing your fucking module'. Instead they have an internal process that builds perl and internally used CPAN distributions into an easily installed RPM package on our internal systems that require it. The original author of this process chose (for the sake of convenience I presume, he's not here to ask) to use CPAN::Site to build a local mirror for this process and modify the author *only* when storing the tarball in the generated, local CPAN repository. This only affects the path used and in no way modifies the content of the distribution; all contents and attributions are left untouched. I hope this answers your question and that we can now return to the strange behaviour we're seeing and was described in my original report.
My apologies for the rudeness, just too many weird things happening lately (like me not getting any email from RT for months) so sometimes I'm a bit paranoid. Anyway, I converted the dist to dzil and am using Archive::Tar (and NOT Archive::Tar::Wrapper) so the next release should fix this problem, I cannot upload right now because PAUSE is down. What I suspect is the reason for people sometimes using bsdtar is building dists on Mac OS X, where /usr/bin/tar is bsdtar due to having a FreeBSD userland. I overrode mine with gnutar from macports, just for good measure, but any dist I build with dzil should just use Archive::Tar.
Subject: Re: [rt.cpan.org #91922] Using bsdtar confuses gnutar and CPAN
Date: Thu, 9 Jan 2014 08:16:17 +0000
To: bug-CatalystX-Component-Traits [...] rt.cpan.org
From: Chisel <chisel [...] chizography.net>
That's brilliant. Thank you. On 9 Jan 2014 05:55, "Rafael Kitover via RT" < bug-CatalystX-Component-Traits@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=91922 > > > My apologies for the rudeness, just too many weird things happening lately > (like me not getting any email from RT for months) so sometimes I'm a bit > paranoid. > > Anyway, I converted the dist to dzil and am using Archive::Tar (and NOT > Archive::Tar::Wrapper) so the next release should fix this problem, I > cannot upload right now because PAUSE is down. > > What I suspect is the reason for people sometimes using bsdtar is building > dists on Mac OS X, where /usr/bin/tar is bsdtar due to having a FreeBSD > userland. I overrode mine with gnutar from macports, just for good measure, > but any dist I build with dzil should just use Archive::Tar. >
Repackaged with dzil.