On Tuesday 30 August 2005 03:22, Uwe Kitzmann wrote:
> >> Propably there's no chance to repair such a rev file?
> >
> > If you post to the dev@ list and make the file available, someone
> > there might be able to examine the file's contents and see if there's
> > an easy way to manually repair it.
>
> Unfortunately this is not possible. It's a large file (12MB) with mostly
> binaries
> of a commercial application. Anyway, thanks a lot for your help.
Uwe, another user has run across a similar problem, and I think both of your
issues are related. Is there any feasible way for me to have at least a copy
of the rev file (143)? I'd be willing to sign an NDA. I think there might
be an issue in the FSFS code, and I'd love to get to the bottom of it.
Alternately, I can provide you with a python script, and have you do a few
things with a copy of the file for me. The script will produce a large
amount of output, but none of it contains the actual file contents. Only
file and directory names involved in the commit would be revealed. It would
take longer to inspect the situation, but it would still be very useful.
For information about the other user's issue, take a look at:
<http://svn.haxx.se/dev/archive-2005-09/0409.shtml>
Thanks!
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 15 11:44:49 2005