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

Re: Broken Revision in FSFS Repo

From: Mariusz Droździel <mdrozdziel_at_gmail.com>
Date: Wed, 3 Mar 2010 15:19:10 +0100

2010/3/3 Mariusz Droździel <mdrozdziel_at_gmail.com>:

> Well, actually at first this one seemed to be quite trivial. Its
> enough to raise Apache loglevel to debug in order to see the exact
> filenames in mod_authnz_ldap logs.

Ok, in the end the solution described by Martin worked great. Thanks
big time! Small tip for anyone who will run into this problem and read
this topic. Raise apache loglevel to debug. If your sync fails, just
do checkout of the failing revision. You will exactly see which file
is broken. After denying access you can continue the sync with no
problem.

Out of 100k files I lost historical data for only 5 (newest versions
are there in the local copy), so its not that bad after all.

-- 
Mariusz Drozdziel
Received on 2010-03-03 15:19:45 CET

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