Bug : Local filename modification to uppercase during some Tortoise operations

66 views
Skip to first unread message

Nastin Nicolas

unread,
Jan 15, 2018, 6:15:10 AM1/15/18
to TortoiseSVN
Hello,

First of all, thanks for Tortoise that gives me a great help.

I have some files in my repository whose names are modified to uppercase during some Tortoise operations : update, update to revision, switch. After those operations, Tortoise view file as "missing"

Here an example :
- I have a file named "ZCSync.pas". Its filename was never modified since its creation
- The working copy is up-to-date and there is no pending modifications
- I update this file to the previous revision number (Another possibilty is to delete the file with Windows Explorer and to update the folder)
- Filename become ZCSYNC.PAS
- Tortoise now view "ZCSync.pas" as "missing"
- A revert operation restore the right filename

Some details :
- Repo-browser never shows filename "ZCSYNC.PAS"
- The issue always appears on the same files.
- Issue appears on two computers with Windows 10 1709 + Tortoise 1.9.7.27907 but also on previous Tortoise version
- SVN Server 1.9.7.30920 (Database was created with 1.6) 
- One of my collegues does not have this issue (the only difference is Windows 10 1703)
- The "FixCaseRenames" option is enabled. I try disable it but it does not resolve the issue.
- I deleted my working copy and uninstalled Tortoise. And then I reinstalled it and make a Checkout. But it does not help.

Does someone has any idea ?

Thank to all of you !
Nicolas

Stefan

unread,
Jan 16, 2018, 11:06:37 AM1/16/18
to TortoiseSVN
svn does not itself convert filenames or pathnames.
But: if your working copy is on a old filesystem like FAT (not FAT32), then the filesystem returns those names when queried for.

Oh, and I know of a virus scanner (with a 'k' in its name) that once did that to all file requests: it forced Windows to return only uppercase pathnames.

Stefan

Nastin Nicolas

unread,
Jan 19, 2018, 3:03:32 AM1/19/18
to TortoiseSVN
Many Thanks Stefan.


Le mardi 16 janvier 2018 17:06:37 UTC+1, Stefan a écrit :
But: if your working copy is on a old filesystem like FAT (not FAT32), then the filesystem returns those names when queried for.

 I was using a VeraCrypt encrypted container formatted in FAT32 (not FAT). I switched to NTFS and I do not manage to reproduce the issue

Le mardi 16 janvier 2018 17:06:37 UTC+1, Stefan a écrit :
Oh, and I know of a virus scanner (with a 'k' in its name) that once did that to all file requests: it forced Windows to return only uppercase pathnames.

Yes, I was previously using this virus scanner but the issue lasted after the virus scanner change.

Nicolas
Reply all
Reply to author
Forward
0 new messages