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

Re: Old version advice

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Thu, 19 Apr 2012 13:24:37 +0100

On 19 April 2012 12:57, Peter Van Hove <peter_at_smart-projects.net> wrote:
> Hi,
> I (still) use following version:
> TortoiseSVN-
> I'm very happy with it in fact.  I use it almost every day eventhough I know
> very little about the technology behind it and I also only use novice
> features such as check in, or go back via the log to see what changes I made
> and where.
> The reason why I stopped upgrading, now years ago, is because I made a
> mistake originally with the type of repository that I created and the fact
> that the repository is placed on a remote drive in my local network.  Don't
> ask me the details, I'm not SVN savvy enough to understand the problem.  I
> had to stay with this version to be able to use it properly.
> I'm now in the process of migrating to a new system.  Obviously a 64 bit OS
> (W7).
> What to do !??
> Is the exact same version also available in 64 bit ?  Is it a stable release
> and where can I find it ?
> Or better yet, what should I do to go to the latest and greatest version
> using my type of repository ?

There is no 64-bit binary for the 1.4.x line, never was, never will
be. Your best bet is to migrate your repository to a later version. My
guess is that you have a BDB repository rather than an FSFS one, and
TortoiseSVN no longer supports access to BDB repositories using
file:/// URLs.

If that is the case then you are very lucky not to have a corrupted
repository by now. Using a BDB repo on a network share is very
strongly discouraged as it was not designed to work that way. Also,
just to be sure, you are the only person using this repository, right?
If not then you need to set up a proper subversion server.

Assuming it is just you then you need to perform a dump/load cycle on
the repository. First off you need to make sure you have no
uncommitted changes in any of your existing working copies as those
WCs are going to be deleted soon. Next you dump the content of your
existing repository into a separate file (this does not affect your
existing repository at all, just creates a loadable dump file from
it). Next you create a new empty repository in FSFS format (now the
default) and load it using the dump file you just created. That will
import every revision from the old repo into the new one. Once you
have done that you should rename your original repository so it
doesn't get accessed (and especially committed to) by mistake. Any
existing working copies you have will now be disconnected and should
be deleted. You will need to make a fresh checkout of each one from
your new repository using the TSVN 1.7 client.

You will need the subversion command line tool 'svnadmin' to do this.
If you install the latest TortoiseSVN (1.7.x) then you can opt to
install these utilities as well, otherwise you can get them separately
using links on the subversion.apache.org website.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-04-19 14:24:51 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.