You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by James Oltmans <jo...@bolosystems.com> on 2007/01/31 22:37:16 UTC
Working copy locked problem
Hey all,
I've been running into an issue several times that I'd like some advice
on how to solve.
We have a project where certain files and file structures are
programmatically generated. These structures and files are then checked
back into the repository and are used to build the system from scratch,
they're best described as a bunch of categorized config files. The
problem I'm having is that in order to accurately reflect the changes
that have occurred to the system it seems best to wipe the dump
location's target before initiating the dump. This ensures that we
capture the state of the system without orphaned files and folders of
the previous dump getting in the way. This unfortunately eliminates
certain subfolders and the .svn folders they contained. They are then
replaced by, in most cases, identical subfolders that don't contain the
.svn. When I try and do an add, update, commit etc... it locks the
working copy such that svn cleanup can't fix it until I've removed the
unversioned generated files and folders.
Is there any way to have subversion restore the .svn folder for these
generated folders? Our current workaround is to leave the folder
structure intact and force the developer to remove the folders by hand,
but given the number of files and folders we're dealing with this is a
tedious process.
James Oltmans
Software Engineer
Bolo Systems, Inc.
<http://www.bolosystems.com/>
(303) 987-2238 x 107
(720) 212-0687 Direct
joltmans@bolosystems.com
RE: Working copy locked problem
Posted by James Oltmans <jo...@bolosystems.com>.
That's a great ideal, but it's not always the easiest solution. In the
case I mentioned before where we dump out a directory tree and files to
represent the configuration of the system, we've decided we're going to
have to dump to a temporary location that people can't commit from then
write a copy program to handle it in order not to wipe out the .svn
folders and properly mark folders for addition and deletion.
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2007a@ryandesign.com]
Sent: Friday, February 02, 2007 1:11 AM
To: James Oltmans
Cc: users@subversion.tigris.org
Subject: Re: Working copy locked problem
On Jan 31, 2007, at 16:37, James Oltmans wrote:
> Is there any way to have subversion restore the .svn folder for
> these generated folders?
No. Subversion policy is that you are not to touch the .svn folders
or their contents. If you do, the working copy will most likely
break, as you've seen.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Working copy locked problem
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jan 31, 2007, at 16:37, James Oltmans wrote:
> Is there any way to have subversion restore the .svn folder for
> these generated folders?
No. Subversion policy is that you are not to touch the .svn folders
or their contents. If you do, the working copy will most likely
break, as you've seen.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org