Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of jongmob@gmail.com designates
 74.125.82.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53B525AD.903@wandisco.com>
References: 
 <CACZYS+q1V5G8XRP6NtCvH1u9QBnffR5ze1TDjt3DfD2ohJ5+Bw@mail.gmail.com>
	<043e01cf95e0$bd56f7c0$3804e740$@qqmail.nl>
	<CACZYS+q8Y_3BuBfCBA0ToYV86Pjj=vUr7e5v3Y5HJUkxON62Qg@mail.gmail.com>
	<CACZYS+p-8rXdD+dijmst_d1YnZZ7UVmE7R8jtzrQ-0-+fXZ46A@mail.gmail.com>
	<53B525AD.903@wandisco.com>
Date: Thu, 3 Jul 2014 10:58:35 +0100
Message-ID: 
 <CACZYS+peD6Sj4v1_50+mDcgh8tBri7J2VsPcsV8TXJ71nSXxJQ@mail.gmail.com>
Subject: Re: Extend E155021 message to include supported format version
From: Notes Jonny <jongmob@gmail.com>
To: =?UTF-8?Q?Branko_=C4=8Cibej?= <brane@wandisco.com>
Cc: users@subversion.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Brane

On Thu, Jul 3, 2014 at 10:43 AM, Branko =C4=8Cibej <brane@wandisco.com> wro=
te:
> On 03.07.2014 11:37, Notes Jonny wrote:
>
> 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.
>
>
> It's definitely not trivial. We want to do that eventually, but due to
> hysterical raisins, it's going to take a fair amount of work.
>
> -- Brane

Hi Brane

Many thanks for your reply

I guess the other idea is to promise to only allow ".svn format"
updates every 5 years? I can't think that I've noticed any
improvements since I've been using new formats..  Do GIT repos suffer
these same problems?

I suffer this .svn dependency hell every time I need to build a new
automated build server (most places don't even publish old packages
any-more).

Jon