Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues when extracting with OSX Archive #24

Closed
paulgoldbaum opened this issue Jun 30, 2016 · 7 comments
Closed

Issues when extracting with OSX Archive #24

paulgoldbaum opened this issue Jun 30, 2016 · 7 comments

Comments

@paulgoldbaum
Copy link

When extracting zip files generated with yazl 2.4.0 using the Archive app, a filename.zip.cpgz is generated instead of the contents. Zipfiles generated with 2.3.1 work as expected.

I'm using yazl through gulp-zip so it might not be an issue with yazl itself.

@mkalish
Copy link

mkalish commented Jun 30, 2016

+1

@Sryther
Copy link

Sryther commented Jun 30, 2016

+1

If you rename the file into .rar it works..

@thejoshwolfe
Copy link
Owner

sorry about this guys. i lost my mac test machine recently, and i didn't suspect that changing the Version Needed To Extract would break anything so i published without testing that on Mac. if one if you would be willing to try out some test case zipfiles i upload in a few minutes, that would be most appreciated...

@thejoshwolfe
Copy link
Owner

Could someone on Mac please try extracting these four zipfiles:

http://wolfesoftware.com/tests.zip

(the zip contains 4 zips, which each contain a single empty file.)

Please tell me which zip files extract, if any, and which cause the .cpgz behavior. This will determine if the Version Made By and Version Needed To Extract are the culprits. I suspect only the Version Needed To Extract will be the problem.

@mkalish
Copy link

mkalish commented Jun 30, 2016

1 and 2 both worked
3 and 4 did not

@mkalish
Copy link

mkalish commented Jun 30, 2016

👍

@thejoshwolfe
Copy link
Owner

thanks @mkalish for your help.

yazl version 2.4.1 is published and should fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants