You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Kamesh Jayachandran <ka...@collab.net> on 2009/03/30 14:51:40 UTC

Re: [PATCH]Upgrading pre svn1.2 repositories to svn 1.6 fails(upgrading to 1.5 succeeds though!)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks Stefan and Hyrum.

Committed in r36851 and nominated for 1.6.x backport.

With regards
Kamesh Jayachandran

Stefan Sperling wrote:
> On Mon, Mar 30, 2009 at 09:28:33AM -0500, Hyrum K. Wright wrote:
>> On Mar 30, 2009, at 9:26 AM, Kamesh Jayachandran wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>>
>>>
>>> Hyrum K. Wright wrote:
>>>> Do we support upgrade version-hopping like this?  I was under the
>>>> impression that to upgrade from 1.X to 1.X+2, you'd better go through
>>>> 1.X+1.
>>>>
>>> What if somebody is *not* interested in 1.X and continue using old  
>>> 1.X-1
>>> and suddenly needs 1.X+1 badly, so why not he upgrade directly?
>>>
>>> In any case atleast we should detect leap upgrades and take meaningful
>>> upgrade path or atleast suggest something useful instead of vague  
>>> error.
>> Sure.  I'm not saying we shouldn't support it, I'm just that I didn't  
>> know we currently do support that upgrade path.  (And if somebody  
>> really did want to jump several repository formats ahead, they are  
>> probably better off doing a dump/load.)
> 
> It's a regression either way because it worked with 1.5.x.
> 
> I'd say we should fix the bug, whether or not we support such
> an upgrade. It's an easy fix.
> 
> Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ0Nx83WHvyO0YTCwRAmpIAJ48Zd1T2gfUqbX2ZiBmInmbvAdXFQCgnE5E
URfro70e9cvZXaQqg5E7roA=
=w6Ay
-----END PGP SIGNATURE-----

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