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

Re: Upgrading a very old SVN version

From: Andreas Mohr <andi_at_lisas.de>
Date: Thu, 14 Dec 2017 09:01:05 +0100

On Wed, Dec 13, 2017 at 05:19:50PM -0500, Nico Kadel-Garcia wrote:
> On Wed, Dec 13, 2017 at 2:27 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> > Step 1 is very safe and easy and you are unlikely to encounter problems.
> > Step 2 is more of an unknown. There are various bugs that existed in older
> > versions that allowed some data to be stored in repository in format that
> > was in violation of what was intended. Newer versions of Subversion detect
> > and enforce those rules better. If you have any of this data you might get
> > errors when loading the repository to the new format. If you do, you can
> > search the archives of this list to find answers on how to proceed.
> Jumping that far between versions, I'd *expect* trouble. The
> repository is basically a file-system based database. I'd urge *not*
> updating that in place.

Are we talking:
- full update, with certain suitable (last-minor stable) interim versions used?
- full update, going from earth to mars?

Possibly you're recommending "avoiding *both* variants of such a large jump,
if possible".

If this "problematic" sentiment holds, then interesting questions are:
- is an upgrade from very old versions generally supposed to be "doable"?
  (i.e., should this use case be supported as best as can be?)
- if support ought to be best/improved, then how to analyze whether this
  holds water? (in this particular case)
  Would perhaps be good to go through such an upgrade for test purposes only,
  then "play a bit" with the resulting test-only data
  to possibly determine some issues.


Andreas Mohr
Received on 2017-12-14 09:01:16 CET

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