[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 4307]  upgrade from 1.7 crashes if WC contains conflict
From:       stsp () tigris ! org
Date:       2013-01-28 17:27:26
Message-ID: 20130128172726.69299540051 () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=4307






------- Additional comments from stsp@tigris.org Mon Jan 28 09:27:26 -0800 2013 -------
If you debug this you will see that the actual error returned is a 'this working
copy must be ugraded to be used with 1.8' error.
This happens if the upgrade code starts scanning for a wcroot before the upgrade
completes.

The error isn't being shown because we abort maintainer mode builds if some
sqlite statement isn't properly reset, which might or might not be an unrelated
problem.

Some notes from IRC:

<stsp> Bert, we cannot use svn_wc__db_get_wcroot() in the upgrade code, because
the causes a dependency loop (the upgrade code must assume that the path the
user passed is a WC root)
<stsp> but svn_wc__upgrade_conflict_skel_from_raw() is using it
<stsp> which currently causes an abort if svn upgrade is used in a 1.7.x WC
which has a text conflict in it
<stsp> any ideas how to fix it?
<stsp> it seems inappropriate for that API to use a wri_abspath
<stsp> it should expect a wcroot_abspath instead and just use it

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=3046414

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]