-
Bug
-
Resolution: Fixed
-
Normal
-
1.0
-
None
-
OSX 10.4 with HFS+ and FAT32 drives
If I have a file called "FOO.mp3" and Picard wants to rename it to "Foo.mp3", it actually turns into "Foo (1).mp3". I presume this is because the filesystem is case insensitive and when it checks, it finds that the new filename already exists but doesn't realise that it's the same file because the name isn't identical to the current one.
There was a similar ticket at http://bugs.musicbrainz.org/ticket/4066 which claimed to get an error, but neither me nor bitmap could reproduce that.
- has related issue
-
PICARD-1986 Case-only changes to file names are not applied on SMB shares on Linux mounted with GVFS
- Closed
- is duplicated by
-
PICARD-1981 When renaming files (1) should not be appended to the filename
- Closed
- is related to
-
PICARD-1113 New file copies made when filename unchanged
- Closed
-
PICARD-1990 Case-only changes to file names are not applied on Windows if running with Python >= 3.8
- Closed
-
PICARD-1991 Case-only changes to file names are not applied on case insensitive file systems on Linux
- Closed
-
PICARD-1992 Case-only changes to file names are not applied on FAT32 and exFAT file systems on Windows 10
- Closed