Scott Miller wrote on Wed, Feb 27, 2013 at 10:26:20 -0800:
> Hi,
> 
> I am using  Subversion 1.6.12 (r955767 on an Ubuntu server.  SVN has been
> up and running a long time and had very few, if any, problems.  Last week I
> needed to make for new repos.  Three went just fine.
> 
> The fourth has been a problem.  Here is a history of what happened and what
> I did.
> 
> I used svnadmin and created the repo on the server.
> 
> Using TortoiseSVN I checked it out to my Win7 desktopy.  I created
> trunk,tags and branches folders and committed them to the repo.  Then I
> took all the production code from our ubuntu server and copied it into a
> subdirectory named public inside the trunk directory.  Everything went as
> expected until this point.
> 
> Then I tried to commit all this code to the repo.  It failed due to lack of
> disk space.  This turned out to be correct, I freed up disk space deleted
> the repo directory and started the whole process again.  This time when I
> went to commit all the code I got a Cannot write to the prototype revision
> file of transaction '1-5' becasuse a previous reperesntation is currently
> being written by another process.
> 
> 
> I again deleted everything restarted the server, restarted my desktop.  It

Does "restart" mean "apachectl -k restart", "reboot", or something else?

Do you happen to have multiple versions of libapr (ignore libapr-util)?

Are all repositories on the same filesystem and mount point?  Is it
a local or network mount?

> still did not work.
> 
> I looked through the code I was trying to upload and found that at one
> point it must have been part of some repo because in many subdirectories
> there were .svn folders.  On my desktop I deleted them all.
> 
> This time I deleted and restarted everything and even used different folder
> and directory names,  I still get an error.  Commit failed
> Cannot write to the prototype revision file fo the transaction '1-1'
> becasuse a previous reperesntation is currently being written by another
> process.
> 
> Where do I go from here?
> 
> Scott

Reply via email to