Skip Menu |

This queue is for tickets about the Apache-Singleton CPAN distribution.

Report information
The Basics
Id: 68532
Status: resolved
Priority: 0/
Queue: Apache-Singleton

People
Owner: Nobody in particular
Requestors: shay [...] cpan.org
Cc:
AdminCc:

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



Subject: Tarball doesn't extract properly on Win32 using WinZip
Apache-Singleton-0.12-tar.gz does not extract into its proper folder structure on Windows using the popular WinZip software. Instead, all the files are extracted into a single folder. The attached images show what folders WinZip (version 11.1) thinks are in the respective .tar.gz files (look at the 'Path' column -- enitrely blank in version 0.12), and they are extracted accordingly. The tarball can still be extracted using more UNIXish tools (e.g. Cygwin's "gzip -cd ... | tar xf -" worked for me), so I'm not sure what's at fault here. Presumably WinZip itself doesn't fully support certain .tar.gz formats, but given how ubiquitous it is on Windows it would be helpful if the tarball was in a format that WinZip does understand, as it was up to version 0.11. (I realize this is not a bug in Apache-Singleton; it's just the innocent victim of a bug somewhere else. Maybe it's the packaging tools; more likely it's WinZip. However, I wouldn't want to wait around for WinZip to be fixed, and since in the meantime it is possible to create .tar.gz files that it does understand it seems preferable to use such formats for the sake of Windows users, unless there are good reasons for using the other format that WinZip doesn't understand. If the difference in the .tar.gz format introduced in version 0.12 is the result of switching to Dist::Zilla (which I see mentioned in the Changes file) then perhaps you could report this problem on that CPAN RT queue?)
Subject: Apache-Singleton-0.12.png
Apache-Singleton-0.12.png
Subject: Apache-Singleton-0.11.png
Apache-Singleton-0.11.png
The problem is in fact WinZip. It apparently does not properly handle archives created with GNU tar v1.25, which is the default tar in Ubuntu 11.04. You are likely to have this problem with many more CPAN dists in the future until WinZip fixes this problem. I tested on winzip 15.0 and the problem still persists there. The only workaround is to create the tarball with something like -- format=v7 to force old format in the meantime. I will upload a v0.13 in this format in the meantime.
Correction. Archive::Tar is the culprit. This bug has the details: https://rt.cpan.org/Ticket/Display.html?id=18720 You will likely continue to experience problems for any tarball created with Archive::Tar unless the DO_NOT_USE_PREFIX option is set (its not by default). I'm uploading v0.13 to cpan right now, and WinZip does handle it properly.. This possibly breaks things on Solaris and Irix though. I do not have access to those OS's for testing so I can't be sure. The only place this could be fixed is in Archive::Tar, and it does not seem like there is an easy solution. Try v0.13 and let me know if it works for you.
On Sun May 29 15:38:39 2011, MSCHOUT wrote: Show quoted text
> Correction. > > Archive::Tar is the culprit. This bug has the details: > > https://rt.cpan.org/Ticket/Display.html?id=18720
[...] Show quoted text
> Try v0.13 and let me know if it works for you.
Thanks for looking into this. Seems like quite a tricky problem to solve unless/until the WinZip guys pull their fingers out :-( Anyway, I confirm that version 0.13 works for me.