First, this should probably have gone to firstname.lastname@example.org if it didn't already.
Secondly, Subversion requires the creation of a .svn subdirectory inside
a directory to be version-controlled. It is not possible to do that unless the user has write permissions for that directory.
Thirdly, with svn built from trunk, svn status does not show the '~'
before the new directory.
On Tue, 2005-05-03 at 16:47 -0400, Levander wrote:
I searched for this issue on
http://subversion.tigris.org/project_issues.html - but it was wierd,
because nothing ever came up in any of my searches.
I am currently using version 1.1.1 of the server and the client. I am
using the version from the Ubuntu Hoary repositories.
Basically, whenever you try to "svn add" a directory that you don't have
write permission to, call it $DIR, svn gives you an error saying
"$DIR/.svn/lock: No such file or directory." This wouldn't be so bad,
although it probably should say that you need write permission to a
directory to add it to the repository.
What's worse though is when you do a "svn status", $DIR shows up in the
list with a tilde (~) next to it. If you try to re-add the directory to
the svn repository, you get an error. If you try to "svn rm" the
directory from the repository, you get an error.
The work around is to 1.) change the directory's name, 2.) "svn rm" the
directory, 3.) change the directory's name back to the original, 4.)
give yourself write permissions to the directory, 5.) "svn add" the
directory back to svn.
Trying to add a directory you don't have write access to may sound like
an obscure use case, but I don't think it is that obscure. The reason
it's coming up for me is I'm putting a web application written in php in
a svn repository. The application occasionally creates directories and
files. By default, created directories only have write permission by
the user the web server is running as. Seems like other people would be
doing this to.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org