Cannot commit new files under component directories beginning with a plus sign

[GoogleCodeExporter]

The following steps will reproduce the problem:

1) In a new or existing project, which may already contain directories with a 
plus sign, create, add, and commit a new directory with a plus sign in the name:

mkdir +MyDirectory
svn add +MyDirectory
svn commit -m 'Adding directory with a plus sign in the name'

This works.

2) Under the new directory, create and add a file:

cd +MyDirectory
touch MyFile.cpp
svn add MyFile.cpp

This works.

3) Attempting to commit the file fails:

svn commit -m 'Adding a file under a directory with a plus sign'
svn: Commit failed (details follow):
svn: '/svn/trunk/+MyDirectory' path not found

4) This failure seems to have started happening within the past 3-4 months.

This failure adversely affects projects that package MATLAB, because the MATLAB 
language requires package directories to begin with a plus sign.

It also affects projects that include directories with names like 
libstdc++5-3.3.6-2-i586.

Original issue reported on code.google.com by dddvis...@gmail.com on 10 Jul 2010 at 12:04

[GoogleCodeExporter]

Google development team has been contacted, and a fix is pending for next 
update to Google Code:

http://code.google.com/p/support/issues/detail?id=3769&q=dddvision&colspec=ID%20
Type%20Status%20Milestone%20Priority%20Stars%20Owner%20Summary

Original comment by dddvis...@gmail.com on 10 Jul 2010 at 12:06

• Changed state: Done

[GoogleCodeExporter]

In the meantime, use the following workaround:

1) Copy all files from the directory with the plus sign in the name to a 
similar directory without the plus sign. Be careful not to miss any files, or 
your changes could be lost.

2) Execute the following, replacing the directory name and message as needed:
svn add MyDirectory
svn rm +MyDirectory
svn commit -m 'My message'
svn mv MyDirectory +MyDirectory
svn commit -m 'My message'

Original comment by dddvis...@gmail.com on 10 Jul 2010 at 12:16

• Changed state: Started

[GoogleCodeExporter]

Problem was resolved by the Google team.

Original comment by dddvis...@gmail.com on 3 Sep 2010 at 5:26

• Changed state: Fixed