On 23 Mar 2009, at 00:35, Stefan Sperling wrote:
> On Sun, Mar 22, 2009 at 05:58:23PM +0000, Barry Scott wrote:
>> On 20 Mar 2009, at 12:25, Greg Stein wrote:
>>> * r36302
>>> Fix a small problem in the loggy upgrade process. Some v10
>>> working copies
>>> have .svn/format, and some don't. The *intent* is to remove the
>>> file if
>>> present, so make the code match.
>>> Justification:
>>> If change-svn-wc-format.py is used to downgrade a working copy
>>> from 1.6 to 1.5 format, the script does not add the format file,
>>> rendering 1.6 clients unable to update the working copy again:
>>> "svn: Can't remove file '.svn/format': No such file or directory"
>>> Since the presence of that file has been deprecated for ages,
>>> let's just apply this easy fix to 1.6 instead of tweaking the
>>> script.
>>> Votes:
>>> +1: rhuijben, stsp, arfrever, gstein
>>
>> How about fixing change-svn-wc-format.py so that those of us that
>> use this in development can avoid this bug before 1.6.1 is released.
>
> Can you make a patch?
No. All my spare time is currently going to getting pysvn ready for
release against 1.6.
>
>
> FWIW I wanted this fix in 1.6.0 to save people the nuisance but it
> did not make it because the backport did not get enough votes by
> other devs for 1.6.0.
>
> Anyway, I'd still recommend you stop using this script now. The script
> will most likely be phased out with 1.7 anyway, because of the working
> copy library rewrite. It is quite unlikely that we'll get a script
> that
> can up- and downgrade between 1.6 and 1.7 working copy formats.
Its is a problem when experimenting with new SVN that a WC that is not
intended to be upgraded is and breaks the old SVN tool chains.
If 1.7 cannot be downgraded I need a way to prevent to upgrade happing
at all.
How about a config option that prevents upgrades that 1.7 would honor?
Then
developers like myself could turn off auto upgrade and avoid upgrade
damage.
Barry
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1399503
Received on 2009-03-24 09:49:55 CET