You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Louis Haynes <lo...@crablouie.com> on 2005/02/22 17:03:21 UTC
Working copy not locked
I've search the documentation on this but have not seen a resolution
for my problem.
I have just created a repository and then checked out the code. Created
some new files, ran my ant build file which updated some other files.
The problem is that I added the build directories to svn and in my ant
build script the build directories get deleted and recreated, deleting
all the svn metadata for that directory. So now that I'm trying to
commit my new additions and updates I get the following error:
svn: Commit failed (details follow):
svn: Working copy '/dev/local/project/extras/viewgen/build' not locked
I have tried to use svn update, remove, checkout, svnadmin recover, and
just about any combination to get around this problem.
How do I correct this?
Thanks, Louis
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Working copy not locked
Posted by Bernardo Arlandis Mañó <be...@tsolucio.com>.
En/na Louis Haynes ha escrit:
> I agree totally with your comments. I did not mean to include the build
> directories in the SVN. It was a stupid mistake of being too hasty to
> get things in a repository. I only figured out that I made the mistake
> when trying to add and commit new stuff. So now I need to remove these
> build directories but I'm having trouble becuase everything I try to do,
> I get that error.
> Thanks, Louis
>
Hi Louis.
Check out a new working copy in another place, there you'll be able to
delete everything that shouldn't be there with "svn delete ...". Copy
the files modified in your old working copy to this new one, or use a
diff to grab the changes. Use your new working copy and delete the old
one. Don't forget to do a commit to actually make the changes in the
repository.
Regards.
Bernardo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Working copy not locked
Posted by Louis Haynes <lo...@crablouie.org>.
I agree totally with your comments. I did not mean to include the build
directories in the SVN. It was a stupid mistake of being too hasty to
get things in a repository. I only figured out that I made the mistake
when trying to add and commit new stuff. So now I need to remove these
build directories but I'm having trouble becuase everything I try to do,
I get that error.
Thanks, Louis
Konrad Rosenbaum wrote:
>On Tuesday 22 February 2005 18:03, Louis Haynes wrote:
>
>
>>I've search the documentation on this but have not seen a resolution
>>for my problem.
>>
>>I have just created a repository and then checked out the code. Created
>>some new files, ran my ant build file which updated some other files.
>>The problem is that I added the build directories to svn and in my ant
>>build script the build directories get deleted and recreated, deleting
>>all the svn metadata for that directory. So now that I'm trying to
>>commit my new additions and updates I get the following error:
>>
>>svn: Commit failed (details follow):
>>svn: Working copy '/dev/local/project/extras/viewgen/build' not locked
>>
>>I have tried to use svn update, remove, checkout, svnadmin recover, and
>>just about any combination to get around this problem.
>>
>>How do I correct this?
>>
>>
>
>Fix ant to not delete the directory.
>
>
>
>Moreover: DO NOT STORE BUILT FILES IN A VCS!
>Anything that is built by your environment does not belong in the version
>control (regardless of whether you use svn, cvs, vss, etc.pp). Any
>Developer can rebuild that him-/herself.
>
>While Java might be very forgiving with this behaviour any C++ Programmer
>can tell you that even the slightest change in Compiler-Version or
>LibC-Version changes your binaries completely.
>
>This is the material for fantastic stories about debugging woes! You can
>scare whole university classes senseless with that... ;-)
>
>Besides: this wastes valuable memory and bandwidth on the VCS-Server.
>
>
> Konrad
>
>
Re: Working copy not locked
Posted by Tom Mornini <tm...@infomania.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Feb 22, 2005, at 11:13 AM, Konrad Rosenbaum wrote:
> Moreover: DO NOT STORE BUILT FILES IN A VCS!
I don't totally disagree with this statement, but I do disagree a bit.
:-)
It makes a LOT of sense to store many things in a VCS.
1) Binary tools used to build code. Why risk different versions in use
by
different developers. How else to track the entire build environment
over time?
2) Binary builds built for release. Why not keep a record of what was
actually released?
Now, I generally store these sorts of items in a different repository,
though.
- --
- -- Tom Mornini
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCHD/MzaKkuvKwKvcRAnONAJ41Ss1MrSvLQsZxFMHv5aX2/0XvvwCfX5yY
vbi1DKOVpGeA5cX+4WKAmow=
=pIhr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Working copy not locked
Posted by Konrad Rosenbaum <ko...@silmor.de>.
On Tuesday 22 February 2005 18:03, Louis Haynes wrote:
> I've search the documentation on this but have not seen a resolution
> for my problem.
>
> I have just created a repository and then checked out the code. Created
> some new files, ran my ant build file which updated some other files.
> The problem is that I added the build directories to svn and in my ant
> build script the build directories get deleted and recreated, deleting
> all the svn metadata for that directory. So now that I'm trying to
> commit my new additions and updates I get the following error:
>
> svn: Commit failed (details follow):
> svn: Working copy '/dev/local/project/extras/viewgen/build' not locked
>
> I have tried to use svn update, remove, checkout, svnadmin recover, and
> just about any combination to get around this problem.
>
> How do I correct this?
Fix ant to not delete the directory.
Moreover: DO NOT STORE BUILT FILES IN A VCS!
Anything that is built by your environment does not belong in the version
control (regardless of whether you use svn, cvs, vss, etc.pp). Any
Developer can rebuild that him-/herself.
While Java might be very forgiving with this behaviour any C++ Programmer
can tell you that even the slightest change in Compiler-Version or
LibC-Version changes your binaries completely.
This is the material for fantastic stories about debugging woes! You can
scare whole university classes senseless with that... ;-)
Besides: this wastes valuable memory and bandwidth on the VCS-Server.
Konrad