You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Christophe Franco <ch...@tanusoft.com> on 2011/10/17 11:42:13 UTC

1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

Hello

I have upgraded my TortoiseSVN to 1.7.0 version, and when trying to 
upgrade one of my local working copies, here is the error message that 
it displays :

---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
(users@subversion.apache.org)
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

In file
 
'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\entries.c'
  line 1935: assertion failed (svn_checksum_match(entry_md5_checksum,
  found_md5_checksum))
---------------------------
OK
---------------------------


Re: 1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

Posted by Ulrich Eckhardt <ul...@dominolaser.com>.
Am 17.10.2011 11:42, schrieb Christophe Franco:
> Please take the time to report this [...]  with as much
> information as possible about what you were trying to do.

This part is important.


> But please first search the mailing list archives for the error message
> to avoid reporting the same problem repeatedly.

This part is important, too.


Uli
**************************************************************************************
Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at http://www.dominolaser.com
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************


Re: 1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

Posted by Stefan Sperling <st...@elego.de>.
On Mon, Oct 17, 2011 at 11:53:02AM +0200, Andreas Krey wrote:
> On Mon, 17 Oct 2011 11:42:13 +0000, Christophe Franco wrote:
> | You had a broken working copy that can't be upgraded.
> | http://svn.haxx.se/tsvnusers/archive-2011-10/0086.shtml
> 
> ...practically meaning that the WC 1.6->1.7 conversion code can't really deal with
> what 1.6 typically leaves behind in the sandbox. (This is documented but yet the
> cleanup does not always seem to be enough...)
> 

The problem is that we have no idea why all these 1.6 working copies
were broken in the first place. If we knew why, we could try to make
the upgrade code work around it.

It could be a missing .svn folder, or corrupted or changed files in
.svn/text-base/, or some other problem.

Re: 1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

Posted by Andreas Krey <a....@gmx.de>.
On Mon, 17 Oct 2011 11:42:13 +0000, Christophe Franco wrote:
> Hello
...
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\entries.c'
>  line 1935: assertion failed (svn_checksum_match(entry_md5_checksum,
>  found_md5_checksum))


To quote Andy Levy <an...@gmail.com> from about yesterday:
| ...
| > http://subversion.apache.org/mailing-lists.html
|
|    This is very important. Please do it. You'll find an answer that way.
|
| You had a broken working copy that can't be upgraded.
| http://svn.haxx.se/tsvnusers/archive-2011-10/0086.shtml

...practically meaning that the WC 1.6->1.7 conversion code can't really deal with
what 1.6 typically leaves behind in the sandbox. (This is documented but yet the
cleanup does not always seem to be enough...)

Andreas

--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800

Re: 1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

Posted by Stefan Sperling <st...@elego.de>.
On Mon, Oct 17, 2011 at 11:42:13AM +0200, Christophe Franco wrote:
> Hello
> 
> I have upgraded my TortoiseSVN to 1.7.0 version, and when trying to
> upgrade one of my local working copies, here is the error message
> that it displays :

Known problem.
Your 1.6 working copy was corrupted and cannot be upgraded.
Get a new checkout.

Future versions of Subversion will show a better error message.