Ryan Schmidt wrote on Mon, Feb 28, 2011 at 13:33:51 -0600:
>
> On Feb 28, 2011, at 12:37, James Ralston wrote:
>
> > Recently, Red Hat Enterprise Linux 5 updated its Subversion package
> > from 1.5.x to 1.6.11.
> >
> > This exposed a *forwards* compatibility problem: the Subversion 1.6
> > hotcopy command fails on Subversion 1.5 repositories:
> >
> > $ svnadmin hotcopy test-repo test-repo.HOTCOPY; echo $?
> > svnadmin: Can't open file 'test-repo/db/fsfs.conf': No such file or directory
> > 1
> >
> > We tested if creating an empty db/fsfs.conf file will resolve this
> > issue, and it does. And this issue seems to have been fixed in 1.6.13.
> >
> > But given that this very simple compatibility issue wasn't caught
> > until two bugfix releases later, we're concerned that there may be
> > other forwards compatibility issues that will bite us in the future.
>
> The Subversion team's promise is that any Subversion 1.x client will
> be compatible with any Subversion 1.x server, and I would assume with
> any Subversion 1.x repository. If bugs are introduced that break that
> promise, I'm confident that those bugs would be fixed.
>
Any 1.x and 1.y are compatible *over the wire*.
If you want to access a repository locally (svnadmin) you might not be
able to access a repository that had been upgraded/created by an
svnadmin of a newer minor version.
>
>
Received on 2011-02-28 21:30:44 CET