You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Krishnamoorthi Gopal <kr...@vernal.is> on 2013/12/16 14:21:17 UTC
Upgrade Subversion Repository from 1.5 into 1.8
Hi all,
Is this true - Subversion 1.8 can only upgrade working copies created with
Subversion 1.6 and Subversion 1.7
Currently we have Subversion 1.5 and want to move that into Subversion
1.8.,...............Please advise.
Regards
Support Team.
VERNALIS EMAIL NOTICE
--------------------------------------
The information contained in this email and any attachments is
confidential and may be subject to copyright or other intellectual
property protection. If you are not the intended recipient, you are not
authorized to use or disclose this information, and we request that you
notify us by reply mail or telephone and delete the original message from
your mail system.
Re: Upgrade Subversion Repository from 1.5 into 1.8
Posted by Thomas Harold <th...@nybeta.com>.
On 12/16/2013 9:03 AM, Krishnamoorthi Gopal wrote:
>
> Thanks for your clarification pavel..
>
> If i used existing repositories in Subversion 1.8 then how can i benefit
> features in new version..
>
> Shall i use commands like "svnadmin Upgrade" to upgrade my existing
> repos into latest..
>
As Mark says, "svnadmin dump" and "svnadmin load" cycle is the best way
to upgrade older SVN repositories to 1.8 because it will completely
convert it into 1.8 format (including the new space-saving additions to
the repository format).
However, you don't have to do it all at once. You could start running
SVN 1.8 on the server, then upgrade the individual repositories to the
1.8 format at your leisure. We spread our migration out over a few
weeks (going from 1.6 to 1.8 format). So during the migration period we
had a mix of repository formats on the server.
Client-side working copies, however, are much more all-or-nothing. When
the client moves to 1.8, all of the working copies also have to be
upgraded to 1.8. And we still have a few 1.6 and 1.7 clients talking to
our 1.8 server.
Naturally, you should be making good backups of your SVN repositories
daily. And the dump/load cycle is a good time to copy the dump files
off to long-term storage.
Re: Upgrade Subversion Repository from 1.5 into 1.8
Posted by Mark Phippard <ma...@gmail.com>.
On Mon, Dec 16, 2013 at 9:03 AM, Krishnamoorthi Gopal <
krishnamoorthi@vernal.is> wrote:
>
> Thanks for your clarification pavel..
>
> If i used existing repositories in Subversion 1.8 then how can i benefit
> features in new version..
>
> Shall i use commands like "svnadmin Upgrade" to upgrade my existing repos
> into latest..
>
It depends what features you care about. Most features are specific to the
client version and will work with any server version. If you are looking
to take advantage of all of the disk space saving features in repositories
then you need to dump/load the repository to rewrite the data in the new
format. svnadmin upgrade enables some of those features, but not all of
them.
You do not need to do this for client features though, like improvements in
svn merge etc.
Mark Phippard
http://markphip.blogspot.com/
Re: Upgrade Subversion Repository from 1.5 into 1.8
Posted by Krishnamoorthi Gopal <kr...@vernal.is>.
Thanks for your clarification pavel..
If i used existing repositories in Subversion 1.8 then how can i benefit
features in new version..
Shall i use commands like "svnadmin Upgrade" to upgrade my existing repos
into latest..
Regards
Krishna
From:
Pavel Lyalyakin <pa...@visualsvn.com>
To:
Krishnamoorthi Gopal <kr...@vernal.is>
Cc:
Subversion Users <us...@subversion.apache.org>, Joseba Ercilla Olabarri
<jo...@gmail.com>
Date:
12/16/2013 07:25 PM
Subject:
Re: Upgrade Subversion Repository from 1.5 into 1.8
Hello,
On Mon, Dec 16, 2013 at 5:21 PM, Krishnamoorthi Gopal
<kr...@vernal.is> wrote:
>
> Is this true - Subversion 1.8 can only upgrade working copies created
with Subversion 1.6 and Subversion 1.7
>
> Currently we have Subversion 1.5 and want to move that into Subversion
1.8.,...............Please advise.
Make sure not to confuse *a repository* with *a working copy*!
* Repository:
http://svnbook.red-bean.com/en/1.7/svn.basic.version-control-basics.html#svn.basic.repository
* Working copy:
http://svnbook.red-bean.com/en/1.7/svn.basic.version-control-basics.html#svn.basic.working-copy
It's common for new Subversion users to confuse these terms. Generally
speaking, repository is a server-side entity while working copy is a
user's local private working copy. (I guess that there is some
confusion since the subject has "repository" and the email text refers
to "working copy").
* If you are asking about repositories.
You can use your existing repositories with Subversion 1.8 server.
Though, if you want to benefit from some newer Subversion features,
you need to upgrade your repositories. See Compatibility Concerns
section in Subversion 1.8 Release Notes at
http://subversion.apache.org/docs/release-notes/1.8.html#compatibility
* If you are asking about working copies.
If you upgrade your clients to Subversion 1.8, users will need to
upgrade their working copies to newer format. They can simply checkout
new working copies as well.
http://subversion.apache.org/docs/release-notes/1.8.html#wc-upgrade
See "Upgrading the Working Copy" Release Notes section at
http://subversion.apache.org/docs/release-notes/1.8.html#wc-upgrade
Thank you.
--
With best regards,
Pavel Lyalyakin
VisualSVN Team
VERNALIS EMAIL NOTICE
--------------------------------------
The information contained in this email and any attachments is
confidential and may be subject to copyright or other intellectual
property protection. If you are not the intended recipient, you are not
authorized to use or disclose this information, and we request that you
notify us by reply mail or telephone and delete the original message from
your mail system.
Re: Upgrade Subversion Repository from 1.5 into 1.8
Posted by Pavel Lyalyakin <pa...@visualsvn.com>.
Hello,
On Mon, Dec 16, 2013 at 5:21 PM, Krishnamoorthi Gopal
<kr...@vernal.is> wrote:
>
> Is this true - Subversion 1.8 can only upgrade working copies created with Subversion 1.6 and Subversion 1.7
>
> Currently we have Subversion 1.5 and want to move that into Subversion 1.8.,...............Please advise.
Make sure not to confuse *a repository* with *a working copy*!
* Repository: http://svnbook.red-bean.com/en/1.7/svn.basic.version-control-basics.html#svn.basic.repository
* Working copy:
http://svnbook.red-bean.com/en/1.7/svn.basic.version-control-basics.html#svn.basic.working-copy
It's common for new Subversion users to confuse these terms. Generally
speaking, repository is a server-side entity while working copy is a
user's local private working copy. (I guess that there is some
confusion since the subject has "repository" and the email text refers
to "working copy").
* If you are asking about repositories.
You can use your existing repositories with Subversion 1.8 server.
Though, if you want to benefit from some newer Subversion features,
you need to upgrade your repositories. See Compatibility Concerns
section in Subversion 1.8 Release Notes at
http://subversion.apache.org/docs/release-notes/1.8.html#compatibility
* If you are asking about working copies.
If you upgrade your clients to Subversion 1.8, users will need to
upgrade their working copies to newer format. They can simply checkout
new working copies as well.
http://subversion.apache.org/docs/release-notes/1.8.html#wc-upgrade
See "Upgrading the Working Copy" Release Notes section at
http://subversion.apache.org/docs/release-notes/1.8.html#wc-upgrade
Thank you.
--
With best regards,
Pavel Lyalyakin
VisualSVN Team