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

Re: Compatibility problem I think

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Tue, 13 Nov 2012 21:35:05 +0000

On 13 November 2012 20:53, Robert R. Kessler <kessler_at_cs.utah.edu> wrote:
> Hi,
> So, I'm a professor here at the University of Utah. A student of mine was working on a project using tortoisesvn and ankh plugin inside of vs 2010. I'm trying to resurrect his code and have access to his svn tree. Unfortunately when I try to do a simple repro browse to the file tree I get the following error:
> Found format '5', only created by unreleased dev builds.
> I've subsequently gone back and looked at the error messages and it says that it has to do with using version 1.7.0-alpha1.3. I'm using 1.7.x right now. I went into tortoisesvn archives and tried lots of versions of the software, from the 1.6.16 version up through each of the betas and RC1. The betas say that it is format 5 and formats 1-4 are only supported. Once I get to RC1 and then the other builds it gives the above error saying that it isn't supported.
> I done some web searching to see if I can find the alpha1.3 version as maybe a hack to see if I can grab the files.
> Bottom line - the svn tree has all of the source code to the project locked away and I have no way that I can figure out how to extract them.
> Any help and advice would be most appreciated.

It seems likely that your student was using a nightly build of
TortoiseSVN with file:// access to a local repository, and that
version was linked against svn 1.7.0-alpha3 or maybe subversion trunk
at that time. Or they may have been using an alpha subversion server.
Either way, I strongly suggest that you discourage students from using
unreleased version control software for important work in future,
unless that work involves testing version control systems. In fact if
you set up a department repository using a stable server version then
at least you will have control over the repository end of things.

Unfortunately the subversion.apache.org site seems to be down at the
moment, but I found this google translation of the japanese release


"Introduced Support for subversion 1.6 Packing FSFS revision Files ,
and Subversion 1.7.x alpha Releases (up to 1.7.0-alpha3) into an
SQLite database supported Packing of revprops. This is not present in
the Final Release Support (See Issue # 3952 for the reason). Any
FSFS-backed repositories that weresvnadmin create d or svnadmin
upgrade d by svnadmin from a nightly build or from an alpha release of
the 1.7.x line are not supported by the final 1.7.0 release. It is
required to dump these repositories using an svnadmin built from the
1.7.0-alpha3 release in order to upgrade them for the 1.7.0 release.

"Subversion 1.7 will complain when it encounters such repositories,
with the following error:

"subversion / libsvn_fs_fs / fs_fs.c: 1083: (apr_err = 160043)
 svnadmin: E160043: Found format '5 ', only created by unreleased dev builds;
    See http://subversion.apache.org/docs/release-notes/1.7 # revprop-Packing"

The original English will make more sense, but I'm sure you get the
picture. So what you need to do is get hold of a 1.7.0-alpha3 version
of svnadmin to dump the repository, then use a current svnadmin to
reload the content into a new repository. You may find that alpha
version on the subversion site when it comes back online, or failing
that you should ask on the subversion users mailing list.


:       ___
:  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-11-13 22:35:14 CET

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.