checkout fails in win10 but succeeds in Ubuntu 12.04

[Dale Akitt]

I am encountering a consistent failure whenever I try to create a working copy on my Windows machine.  If I try to create the same checkout on my Ubuntu 12.04 VM, there is no such failure.  I am new to SVN and I guessing someone has probably seen this before and may know how to correct the issue.

When I open the parent folder, there are two versions of the aux.c file and they both appear to be intact.

Screen shot of the error message attached. 

Dale Akitt

[Stefan]

That's a known problem: you can't create a file named "aux" on Windows. It's just not possible. (search the web for "forbidden filenames on Windows")

And that means you can not check out that source code as long as it has a file named aux.c in there.

Also: since windows file systems are case-insensitive, you will also get an error if you have two files that are different only in case - because on windows those two files would result in the same file on disk.

[Dale Akitt]

Of course it would be something like that!  Thanks so much for the info.

Dale

--
You received this message because you are subscribed to a topic in the Google Groups "TortoiseSVN" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tortoisesvn/fTcBqeGAp8I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/bc96488c-dd2a-43d9-9fa9-7f3f0fb5cb6fn%40googlegroups.com.

[David Balažic]

On Friday, 11 September 2020 at 22:12:55 UTC+2 Stefan wrote:

> That's a known problem: you can't create a file named "aux" on Windows. It's just not possible. (search the web for "forbidden filenames on Windows")

Actually no, see below.

It is just the DOS/ancient-Windows API (don't know the exact name) that has this limitation. Windows and NTFS can have such files with no issues.

But many (most?) software uses the above API (or assumes/hardcodes those limitations themselves) , using files like that would lead to problems sooner or later. read: supporting them in (T)SVN will just move the "it doesn't work" problem from the checkout step to the next one (like compiling the checked out source code or similar)

Example on Windows 10 (works since XP or so also):

C:\winsux\tmp\xxx>dir
 Volume in drive C is Windows
 Volume Serial Number is XXXXX

 Directory of C:\winsux\tmp\xxx

12.09.2020  16:34    <DIR>          .
12.09.2020  16:34    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s)  278.334.681.088 bytes free

C:\winsux\tmp\xxx>echo gre ge> test1

C:\winsux\tmp\xxx>dir
 Volume in drive C is Windows
 Volume Serial Number is XXXXX

 Directory of C:\winsux\tmp\xxx

12.09.2020  16:35    <DIR>          .
12.09.2020  16:35    <DIR>          ..
12.09.2020  16:35                 8 test1
               1 File(s)              8 bytes
               2 Dir(s)  278.334.681.088 bytes free

C:\winsux\tmp\xxx>copy test1 "\\.\c:\winsux\tmp\xxx\aux"
        1 file(s) copied.

C:\winsux\tmp\xxx>dir
 Volume in drive C is Windows
 Volume Serial Number is E454-7E89

 Directory of C:\winsux\tmp\xxx

12.09.2020  16:35    <DIR>          .
12.09.2020  16:35    <DIR>          ..
12.09.2020  16:35                 8 aux
12.09.2020  16:35                 8 test1
               2 File(s)             16 bytes
               2 Dir(s)  278.334.603.264 bytes free

C:\winsux\tmp\xxx>type aux
The system cannot find the file specified.

C:\winsux\tmp\xxx>type .\aux
The system cannot find the file specified.

C:\winsux\tmp\xxx>type "\\.\c:\winsux\tmp\xxx\aux"
gre ge

Regards,

David

PS: Case insensitivity can also be turned on, but is is even a bigger mess.

[Stefan Küng]

well yes, you can do that. But now try to do anything with those files using the explorer.

And any app that uses a file-open dialog has automatically the same problem, because those are explorer objects...