You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 a Trace/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.
When testing with the dev test build, the archive is created with a .exe suffix, instead of .7z? It expands, and I can rename it if needs be, but this seems like an unintended change?
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 😄
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: