[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Repository Upgrade Problems moving to 1.5

From: Scott Palmer <swpalmer_at_gmail.com>
Date: Wed, 9 Jul 2008 11:52:17 -0400

Hello all,

I recently upgraded our server and repository to Subversion 1.5 and there
were a couple hiccups along the way that I thought I would share. It's
probably my fault for not reading enough documentation ahead of time, but
maybe this post can save someone the same trouble or shed light on a need
for clearer documentation.

The problem is with locks. When doing the upgrade I decided to do a
dump/load to get the most efficient results possible (sharding the FSFS
database etc.) - I had everyone disconnected anyway so why not take the time
to do it as thoroughly as possible...

Two users had obtained locks on files prior to the update, but when the data
was restored the locks were "lost". This resulted in another user getting a
lock and modifying a file that should have been locked already by someone
else. In another case according to my user, "I locked my Design-Debug log
before the SVN upgrade, and then during the upgrade the server lost the lock
status. So I tried to get the lock again so I could check-in my changes,
and it reverted my log back to what's in the repository, so I lost all my

I'm trying to get more detailed information of the subversion commands
used. I believe everyone was using the TortoiseSVN client, though at this
point it doesn't seem to be a client issue to me.

In any case the documentation I read mentioned things like copying over hook
scripts and config files after the dump load... but nothing mentioned an
extra step required to preserve locks.



P.S. please copy me on replies as I am not subscribed to the list.
Received on 2008-07-09 18:21:57 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.