On Mon, Dec 19, 2016 at 6:10 PM, Matt Garman <matthew.garman_at_gmail.com> wrote:
> We're looking at upgrading our systems from CentOS 6 to CentOS 7[1].
> CentOS 6 provides subversion-1.6, and CentOS 7 provides
> subversion-1.7. We have far too many machines and too much custom
> development to upgrade all servers at once. So there will be a period
> where the two OSes must co-exist. (Possibly a quite-lengthy period if
> the 5->6 upgrade is any indication.)
>
> In particular, our developers need to do testing on CentOS 7, which
> will inevitably result in some code changes that need to be committed.
> But their checkouts must continue to work with CentOS 6.
>
> Looking at the Subversion 1.7 release notes[2], and also my own
> testing, it appears that what I could do to make this easy for
> everyone is to upgrade all CentOS 6 clients to subversion-1.7 (i.e.
> have subversion-1.7 everywhere on the client side). Then everyone can
> do an "svn upgrade" on all their working copies and go about their
> business as usual. The svn server can stay CentOS 6 / subversion-1.6
> for now (probably done much later in the overall upgrade process).
From experience, it's that easy. There is no Subversion 1.7 in the
supported repos, and Subversion 1.9 is (from personal experience)
awkward to backport to CentOS 6. So it may take some work or
searching. I used to publish SRPM tools over at github, but I stopped
a while ago.
Received on 2016-12-20 08:49:42 CET