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

RE: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

From: Cooke, Mark <mark.cooke_at_siemens.com>
Date: Mon, 5 Dec 2011 16:35:09 +0000

> -----Original Message-----
> From: Philip Martin [mailto:philip.martin_at_wandisco.com]
> Sent: 05 December 2011 16:25
> To: Keith Williams
> Cc: users_at_subversion.apache.org
> Subject: Re: Attmpting to Update Working Directory for a
> Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy
>
> Keith Williams <kwilliams_at_sauer-danfoss.com> writes:
>
> > In examining the Working Copy more closely, the Folder Structure is
> > partially in 1.6 format and partially is 1.7 format. I am
> making this
> > assumption by the presence of the .svn folder in some top level
> > folders but not in others. A couple of files were deleted at the
> > repository level prior to the attempt to convert the Working Copy to
> > the 1.7 format. Since the Working Copy is on a network drive someone
> > probably updated a subfolder to 1.7 before the full working
> folder was
> > attempted to be converted which was when the failure and
> report below
> > occurred.
>
> A 1.7 working copy will have a .svn/wc.db file in the root of the
> working copy. A 1.6 working copy will have a .svn/entries
> file in every versioned folder.
>
> It's not possible to upgrade a subfolder, only an entire working copy
> can be upgraded. The upgrade process writes all the 1.7 .svn
> data, for all subfolders, into a temporary location before deleting
> any of the 1.6 data. The final step of the upgrade is to move the
> new 1.7 .svn data into place and to remove the old 1.6 .svn data.

My reading of the OP was that someone had probably seleected a sub-folder for conversion and that may well have succeeded. Seeing as you can take a 1.6 sub-folder and effectively make it a top-level folder, this makes sense to me? Or does the upgrade code crawl upwards to see if folders above are versioned?

The error then happened when someone tried to convert the real root folder, where one of the subfolders was already converted...

~ mark c

> The error message you showed happens while writing the 1.7
> .svn data, so
> it happens before any of the 1.6 .svn data has been deleted from the
> subfolders. If you have versioned subfolders that are missing .svn
> folders it is likely that something other than the upgrade was
> responsible.
>
> > There are no externals associated with this Project
> > Repository. I am not aware of any changes to nodes. We do
> make commits
> > from this working copy but would not be able to do so following the
> > upgrade of the SVN Server to 1.7 until after the upgrade of the
> > working copy to the 1.7 Format.
>
> A 1.7 server supports earlier clients and doesn't care about
> the working
> copy format. If you are unable to use the working copy it's
> because you
> upgraded the client, not the server.
>
> --
> Philip
>
Received on 2011-12-05 17:35:50 CET

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