[
https://issues.apache.org/jira/browse/SVN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Zhakov updated SVN-3131:
-----------------------------
Fix Version/s: (was: nonblocking)
> Error message not accurate when path is too long
> ------------------------------------------------
>
> Key: SVN-3131
> URL: https://issues.apache.org/jira/browse/SVN-3131
> Project: Subversion
> Issue Type: Improvement
> Components: cmdline client
> Affects Versions: 1.4.x
> Environment: Windows XP
> Reporter: Subversion Importer
>
> {noformat:nopanel=true}
> Hi all,
> I'm using: svn, version 1.4.3 (r23084)
> compiled Jan 18 2007, 07:47:40
> In our of our project, we have a quite long path. I just tried to checkout
> this
> project from the svn repository, and got the following error:
> svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup' and
> try again
> svn: Can't open file
> '.svn\tmp\text-base\NoeudDossierAdminListenerManagerSingleton.java.svn-base'
> After investigating, I found that this error is actually due to the path being
> too long, which is not supported by windows.
> So, I obviously don't require svn to fix this windows limitation. But I guess
> it
> would be a good idea to try and detect this problem to help the user
> understand
> more easily what's wrong.
> In fact, the previous message can let the user think there's something bizarre
> with Svn, although it's not its fault at all.
> So, to sum up, couldn't svn try and detect the cwd + the path that's being
> updated/checkouted. And if it encounters an error, displays a message saying
> (in
> addition or in replacement of the current message) something like "Path is too
> long. The platform isn't able to handle paths bigger than 255 chars (e.g.).
> Svn
> cannot continue."
> What do you think?
> Cheers.
> {noformat}
> Original issue reported by *batmat*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
