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

Re: corrupt commits - Eclipse 3.0.1/Subclipse 0.9.28/JavaSVN 0.8.5

From: Toby Thain <toby_at_smartgames.ca>
Date: 2005-03-23 00:20:18 CET

On 8-Mar-05, at 4:01 PM, Alexander Kitaev wrote:

> Hello Toby,
>
>> Thanks for the response. I've already had to fix this
>> particular repo (reverse merge), and I can't give you access
>> to it, but I can make a test repo somewhere that I can give
>> you access, and see if I can reproduce it.
> Actually I do not need repository access to reproduce the problem.
> What I
> would like to have are the files that got corrupted - base version and
> wc
> version of the file as they were before commit that resulted in
> corrupted
> version in repository. I will make the same commit on my computer
> (into my
> local repository) and as I think the problem is on the client side, I
> will
> be able to get corrupted file in my repository as well.

Alexander

We have just seen another example of a corrupt commit: File was changed
at r34 and r30, both those revisions are corrupt, and I cannot
therefore give you the wc version committed at r30 since the corruption
was detected too late.

However this does show that the bug is alive and well. In this case the
project was Java, and the commit was made from a Windows box. In the
previous instance it was a C++ project and committed from OS X. So I'm
still waiting to catch the bug red-handed. :-(

Toby
Received on Wed Mar 23 10:20:18 2005

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

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