subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Notes Jonny <jong...@gmail.com>
Subject Re: Extend E155021 message to include supported format version
Date Thu, 03 Jul 2014 09:37:40 GMT
Hi Bert

Could I ask, would it be possible to standardise the .svn format to
avoid the problems I see?


svn: E155021: This client is too old to work with the working copy at
'/cygdrive/c/jenkins/_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


Like the way FLAC or MP3 bitstream is standardised, if .svn folder
could be standardised, and not change from format 29 -> 31, it would
make my life simpler (I have cygwin svn.exe, TortoiseSVN and also
Jenkins SVN) because Jenkins SVN is lagging behind, I have to manually
find old versions of other tools.  That is the workaround. However, if
svn was backwards and forwards compatible to work gracefully with
checkouts that would be great.

Regards, Jon



On Wed, Jul 2, 2014 at 2:21 PM, Notes Jonny <jongmob@gmail.com> wrote:
> Hi Bert
>
> That is good. I will close the ticket
> Regards, jon
>
> On Wed, Jul 2, 2014 at 11:30 AM, Bert Huijben <bert@qqmail.nl> wrote:
>>
>>
>>> -----Original Message-----
>>> From: Notes Jonny [mailto:jongmob@gmail.com]
>>> Sent: woensdag 2 juli 2014 11:45
>>> To: users@subversion.apache.org
>>> Subject: Extend E155021 message to include supported format version
>>>
>>> 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
>>
>> This is already implemented in the current code....
>>
>>  You just need the newer version to see the updated message.
>> (We don't have a time machine to update your older version to include the message
there)
>>
>>         Bert
>>

Mime
View raw message