Found another way to re-create the bug very similarly.
What that web application that I'm trying to version does sometimes in
the files it creates (that I mention) below is to copy a directory into
another place. A copy, not a move.
So, when you go and try to version this new directory, that is a copy of
an old one that is already version controlled, the new directory already
has a .svn directory in it.
And, when you add the new directory to the repository, you get an error.
Which as mentioned previously isn't so bad. But the error is very
cryptic. Probably should warn saying, in this case, "This directory
already has a .svn!".
Then, the real problem, like below, after you commit this error, is
trying to figure out how to get the file back in the repository, and you
get errors from "svn add" and "svn rm".
-------- Original Message --------
Subject: Found a Bug
Date: Tue, 03 May 2005 16:47:50 -0400
From: Levander <email@example.com>
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: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 4 11:13:04 2005