MIME-Version: 1.0
In-Reply-To: <4E861356.60107@acm.org>
References: <4E861356.60107@acm.org>
Date: Sat, 1 Oct 2011 10:24:39 -0500
Message-ID: <CAHiT=DGLfCd3m1pBW-iYt81VShMO_K7MRsBtx0ESQG2aY_a9+Q@mail.gmail.com>
Subject: Re: [TESTING] Updated: subversion-1.7.0rc4-1
From: Reini Urban <rurban@x-ray.at>
To: The Cygwin Mailing List <cygwin@cygwin.com>, cygwin-announce@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On Fri, Sep 30, 2011 at 2:07 PM, David Rothenberger wrote:
> IMPORTANT: This release has a new working copy format. To use this
> release, you must manually upgrade your working copy format,
> rendering it unusable with previous major releases.
>
> Please see the release notes
>  http://subversion.apache.org/docs/release-notes/1.7.html
> for more details about the changes in Subversion.

In particular you must run `svn cleanup` in ALL your repos BEFORE
upgrading cygwin.
And the after the cygwin install you can do: `svn upgrade`

"Subversion 1.7 cannot upgrade working copies that a 1.6 client would
have refused to operate upon before an svn cleanup was run (with a 1.6
client). In other words, before upgrading to 1.7, a 1.6 client must be
used to run svn cleanup on all working copies that require cleanup. We
regret for this limitation, but we had to introduce it in order for
1.7 to ship timely and without overcomplicating the internals"

But I love the new centralized SQLite db.
-- 
Reini

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple