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

Extend E155021 message to include supported format version

From: Notes Jonny <jongmob_at_gmail.com>
Date: Wed, 2 Jul 2014 10:44:53 +0100

Hello

I raised this ticket. Ben Reser suggested to discuss on here in the
first instance

http://subversion.tigris.org/issues/show_bug.cgi?id=4511
Extend E155021 message to include supported format version

svn, version 1.7.5 (r1336830)

Could error message E155021 be extended please to include the format code that
is supported.

svn: E155021: This client is too old to work with the working copy at
'/cygdrive/c/ws/shared_ws/dev_code' (format 31).
You need to get a newer Subversion client. For more details, see
  http://subversion.apache.org/faq.html#working-copy-format-change

e.g. could it be changed to:

svn: E155021: This client supports (format 28) and is therefore too
old to work with the working copy at
'/cygdrive/c/ws/shared_ws/dev_code' (format 31).

This is useful to know, because we have various different applications
which checkout in svn format (cygwin svn, Hudson, Jenkins,
TortoiseSVN) and are suffering from incompatibility.

Of course, what would be even better if client formats were backwards
compatible, and tools forward compatible. Like audio codecs are.

As my local soltuion, I found a computer that had old Cygwin
installed, and copied that folder so that I could get an old version
of svn.exe
svn, version 1.7.5 (r1336830)
   compiled Jun 27 2012, 15:27:52

I have seen similar messages from SVN.exe when the checked out
repository is in an new format than svn.exe (e.g. svn.exe supports up
to format 29, but checked out copy by TortoiseSVN is in format 31)

Is there a published list of the format numbers and what versions they
change? I'm still a little confused.

Regards, Jon

What is your opinion on this change?
Received on 2014-07-02 11:45:22 CEST

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

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