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

There's a "kekatar" error when uncompressing files compressed with Keka, if "Exclude Mac resource forks" was unchecked #474

Open
MaxPower85 opened this issue Nov 1, 2019 · 3 comments
Assignees
Labels
Milestone

Comments

@MaxPower85
Copy link

@MaxPower85 MaxPower85 commented Nov 1, 2019

To replicate the bug (it seems to happen every time), do this:

Make sure that "Exclude Mac resource forks" isn't checked, then try to compress the Keka.app (not just any random file... put the Keka.app from the DMG somewhere... in the Downloads folder or wherever you want... and try compressing it) with Keka, using BZIP2, XZ or GZIP... then try to uncompress it with Keka... it uncompresses, but it shows an error:

Error code 1 using "kekatar"
Unknown error

This happened with v1.1.20 and it still happens with v1.1.21

I tried to just compress some random PDF using "ditto --hfsCompression" and then to compress it and uncompress it with Keka, to see is using HFS+ compression maybe causing an issue for Keka, but it didn't show an error

@aonez aonez self-assigned this Nov 1, 2019
@aonez aonez added bsdtar and removed bzip2 dmg gzip xz labels Nov 1, 2019
@aonez

This comment has been minimized.

Copy link
Owner

@aonez aonez commented Nov 1, 2019

Reproduced, although not consistently. I did found this issue a few weeks ago (in a Parallels VM running a macOS Catalina beta) and discarded it since wasn't able to reproduce it.

@aonez

This comment has been minimized.

Copy link
Owner

@aonez aonez commented Nov 1, 2019

Without looking deeply at the issue, I remember the extraction error was about not being able to apply the resource forks, that's why this flag is important to reproduce the issue. Although the difference is obviously in the compression process. The extracted package runs properly, though.

Thanks @MaxPower85!

@aonez aonez added this to the Look at milestone Nov 1, 2019
@MaxPower85

This comment has been minimized.

Copy link
Author

@MaxPower85 MaxPower85 commented Nov 7, 2019

About reproducing it... it seems like it happens every single time if you first try to apply HFS+ compression to a folder with ditto and if there aren't just "incompressible" file types in it (videos and pictures in some format that already has it's own compression)... for example, it seems that ditto wouldn't try to apply HFS+ compression to JPEG files and it looks like it just leaves them as they are, even if you wanted to apply the HFS+ compression on a whole folder containing JPEGs... it just seems like it would apply HFS+ compression on other files in that folder, that it can compress well.

So I guess that's probably why it wouldn't happen if you maybe tried it with some folder containing just pictures or some video clips... but if there are text files in a folder or apps or something in some file format that isn't already using its own compression, then it happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.