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

Re: Repository Upgrade Problems moving to 1.5

From: Scott Palmer <swpalmer_at_gmail.com>
Date: Thu, 10 Jul 2008 07:56:13 -0400

On 10-Jul-08, at 5:32 AM, Jonathan Ashley wrote:

>>> ... 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 changes."
>>> ...
>>> 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.
>> You're correct. Locks are not preserved in a dumpfile.
> You can however, copy the db/locks folder from your old repository to
> your new one, and everything should work. Assuming FSFS of course.

Thanks, I'll remember that for next time.

> Well... it worked for me anyway. I should point out that I also kept
> the same URL to access the repository (i.e. the server name did not
> change) and the same repository UUID. I don't know if changes here
> could have caused problems.

Load into an empty repo preserves the UUID so that shouldn't be a
problem for my case.

> I would be surprised if the client quietly reverted the changed file
> and caused changes to be lost. Are you sure that your user didn't
> accidentally do that?

I was also very surprised. But that is the claim. They say all they
did was use TortoiseSVN to "Get Lock" on the file. It makes no sense
to me.



  • application/pkcs7-signature attachment: smime.p7s
Received on 2008-07-10 18:05:53 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.