Reputation: 6483
I ran into an issue with TortoiseSVN failing on an Update, due to The filename or extension is too long
.
Reading the manual on long paths (http://subversion.apache.org/faq.html#long-paths), it says that:
Why does this problem not affect TortoiseSVN? Because TortoiseSVN always provides absolute paths to the Subversion APIs.
However, this problem is happening with TortoiseSVN. Searching on Google resulted in some posts saying that it should work, and some that it shouldn't. I find it a big limitation to have to restrict paths to being under 255 characters in total.
Any idea if this issue can actually be circumvented?
Upvotes: 0
Views: 1070
Reputation: 43575
As the docs already state: there's no problem with paths longer than 148/255 chars in TortoiseSVN.
However: NTFS (and most other file systems) have a limitation that can you simply can not get around. That limitation is that filenames (including the file extension) must not exceed 255 chars (the full path can be longer). Also, each sub-path must not exceed 248 chars.
So for example:
c:\verylong....foldername\anotherverylong...foldername\longfilename.txt
If your files are within that limit, then there's something else wrong. (if you're storing the files on a disk formatted with FAT32, you'll have more restrictions on the path part lengths).
Upvotes: 1