-
-
Notifications
You must be signed in to change notification settings - Fork 245
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
[REQ] Allow case-sensitive compression? #1407
Comments
Thanks a lot @mejofi. You're right, this should be not just default but mandatory. Here a build with this flag implemented: |
When testing with the dev test build, the archive is created with a |
Ah, never mind, apparently 'Self extracting archive for Windows' is a new option in 1.4.0, and turned on by default? Off by default may be a better choice 😄 Looks like it works otherwise, though. |
Yes sorry this is a mistake in that build, that option shouldn't be enabled by default. Will release a new dev version today with that fixed. |
The fixed version is now here: https://beta.keka.io Thanks again @mejofi |
Thanks again! Fixed it already, will publish when I have more changes/features. |
Is your feature request related to a problem? Please describe
When creating an encrypted 7Z archive from a folder on a case-sensitive volume,
keka7zz
exits with error code 2 whenever it encounters files that would be duplicates on a regular volume, such as 'Photo.jpg' and 'photo.jpg'.Describe the solution you'd like
Some way to have Keka enable the
-ssc
flag for 7Z archives, either via the GUI or as a hidden preference. Or perhaps it could be enabled by default, for compression?Describe alternatives you've considered
The source data comes from a case-sensitive system, where we cannot enforce better file name handling, and is synced to a case-sensitive APFS volume to be able to create snapshots. Tried to run
keka7zz
manually with the same flags as reported by the error message plus the-ssc
flag, but it exits with aTrace/BPT trap: 5
error, meaning we cannot work around it.Using the same version of
7zz
as downloaded from the main website works as expected; fails with the same error, succeeds when the-ssc
flag is added.Additional context
Redacted output from error message follows;
Additional context (2)
Relevant version info from local
7zz
binary;The text was updated successfully, but these errors were encountered: