A case-only name clash on exFAT is not refused before a switch #77
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#77
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found on Ubuntu 26.04 with the 0.9.4 AppImage and a game folder on an exFAT loop mount. A profile holding both
Mods/FooandMods/foo, switched onto the exFAT folder, is not refused up front: both files land inMods/Foo, and the discard that follows fails with the wrong message ("something else is holding a file open"; the log sayscheckoutFailed). The case-insensitive clash check (picked per work tree by a probe, D-entries on case-insensitive drives) should find this before writing anything, as it does on Windows. Done when the clash is refused before anything is written on an exFAT folder under Linux, with a test that runs where an exFAT or case-insensitive folder is available, and the right message.