You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Stein <gs...@gmail.com> on 2009/03/20 12:25:02 UTC
"format" file in working copies
Jack,
On IRC, I saw that you wrote:
jackr: is there supposed to be no more .svn/format? because I'm in
this weird loop: svn cleanup fails "can't remove
blah/blah/.svn/format: no such file or directory" touch
blah/blah/.svn/format; svn cleanup; "can't remove
some/other/.svn/format".......
And there is a relatively easy answer to that, contained in STATUS,
slated for fixing in 1.6.1:
* 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
I'm guessing you bounced back and forth between 1.6 and 1.5 on that
working copy?
Cheers,
-g
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1364214
Re: "format" file in working copies
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Mar 20, 2009, at 1:14 PM, Jack Repenning wrote:
> On Mar 20, 2009, at 5:25 AM, Greg Stein wrote:
>
>> On IRC, I saw that you wrote:
>>
>> jackr: is there supposed to be no more .svn/format?
>> ...
>> And there is a relatively easy answer to that, contained in STATUS,
>> slated for fixing in 1.6.1:
>> ...
>> I'm guessing you bounced back and forth between 1.6 and 1.5 on that
>> working copy?
>
> Absolutely bloody BINGO! And thanks so much for fixing that. I was
> probably going to hunt that down today, after my misery of last night.
>
> "STATUS," eh? Guess I gotta spend more time curled up with
> hacking.html....
Well, you won't find it in STATUS now. I spent this morning merging
all the pending items into 1.6.x, so the branch should be sufficient
for you now.
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1366464
Re: "format" file in working copies
Posted by Jack Repenning <jr...@collab.net>.
On Mar 20, 2009, at 5:25 AM, Greg Stein wrote:
> On IRC, I saw that you wrote:
>
> jackr: is there supposed to be no more .svn/format?
> ...
> And there is a relatively easy answer to that, contained in STATUS,
> slated for fixing in 1.6.1:
> ...
> I'm guessing you bounced back and forth between 1.6 and 1.5 on that
> working copy?
Absolutely bloody BINGO! And thanks so much for fixing that. I was
probably going to hunt that down today, after my misery of last night.
"STATUS," eh? Guess I gotta spend more time curled up with
hacking.html....
-==-
Jack Repenning
jackrepenning@tigris.org
Project Owner
SCPlugin
http://scplugin.tigris.org
"Subversion for the rest of OS X"
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1366379
Re: "format" file in working copies
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Mar 26, 2009 at 06:04:21PM +0800, Edmund Wong wrote:
> Greg Stein wrote:
> > The 1.7 upgrade process will be manual -- no auto-upgrade. It is
> > expected to take a bit of time, so we can't just "sneak it in". And
> > given that it is one direction only... yah, manual.
> >
>
> PMJI, does this mean that any upgrading from a
> 1.5.x repository to a 1.6+ repository will be a one
> way deal?
We were talking about working copies, not repositories.
> I've been studying this change-svn-wc-format.py file
> and while I'm still learning (just started learning
> to be honest) Python, wouldn't it be just like adding
> a check if the format file exists. If it doesn't, it
> creates the file (depending on the version #, of course).
Yes. It's that easy to fix the script. But we had a fix for
the client already which was originally scheduled for 1.6.0,
so no one was bothered enough to fix the script.
Now that 1.6.0 was released without the client-side fix because some
developers (not me) didn't care enough about the issue, there is no
fix at all for this problem in 1.6.0, so people who use the script
with 1.6.0 have a problem.
1.6.1 will have the fix.
> Or am I barking up the wrong tree? (Pardon my incompetence
> in this matter. My desire to help is kind of making like
> a complete dork.)
By all means, don't feel ashamed and please go ahead and try to
fix the script if you can! If you post a fix to this list it will
help all others who want to use the script with 1.6.0.
Thanks,
Stefan
Re: "format" file in working copies
Posted by Edmund Wong <ed...@belfordhk.com>.
Greg Stein wrote:
> The 1.7 upgrade process will be manual -- no auto-upgrade. It is
> expected to take a bit of time, so we can't just "sneak it in". And
> given that it is one direction only... yah, manual.
>
PMJI, does this mean that any upgrading from a
1.5.x repository to a 1.6+ repository will be a one
way deal?
I've been studying this change-svn-wc-format.py file
and while I'm still learning (just started learning
to be honest) Python, wouldn't it be just like adding
a check if the format file exists. If it doesn't, it
creates the file (depending on the version #, of course).
Or am I barking up the wrong tree? (Pardon my incompetence
in this matter. My desire to help is kind of making like
a complete dork.)
Btw, Greg, I don't want to sound rude or anything,
but could you clarify my query within the "issue
manager" thread?
Thanks.
Edmund
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1427995
Re: "format" file in working copies
Posted by Greg Stein <gs...@gmail.com>.
The 1.7 upgrade process will be manual -- no auto-upgrade. It is
expected to take a bit of time, so we can't just "sneak it in". And
given that it is one direction only... yah, manual.
Cheers,
-g
On 2009-03-24, Barry Scott <ba...@barrys-emacs.org> wrote:
> 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
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1401113
Re: "format" file in working copies
Posted by Barry Scott <ba...@barrys-emacs.org>.
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
Re: "format" file in working copies
Posted by Stefan Sperling <st...@elego.de>.
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?
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.
Stefan
Re: "format" file in working copies
Posted by Arfrever Frehtes Taifersar Arahesis <ar...@gentoo.org>.
2009-03-22 18:58:23 Barry Scott napisał(a):
> On 20 Mar 2009, at 12:25, Greg Stein wrote:
>
> > Jack,
> >
> > On IRC, I saw that you wrote:
> >
> > jackr: is there supposed to be no more .svn/format? because I'm in
> > this weird loop: svn cleanup fails "can't remove
> > blah/blah/.svn/format: no such file or directory" touch
> > blah/blah/.svn/format; svn cleanup; "can't remove
> > some/other/.svn/format".......
> >
> > And there is a relatively easy answer to that, contained in STATUS,
> > slated for fixing in 1.6.1:
> >
> > * 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
> >
> >
> > I'm guessing you bounced back and forth between 1.6 and 1.5 on that
> > working copy?
> >
>
> 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.
You can use Gentoo :)
http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/subversion/files/subversion-1.6.0-various_fixes.patch?view=markup
--
Arfrever Frehtes Taifersar Arahesis
Re: "format" file in working copies
Posted by Barry Scott <ba...@barrys-emacs.org>.
On 20 Mar 2009, at 12:25, Greg Stein wrote:
> Jack,
>
> On IRC, I saw that you wrote:
>
> jackr: is there supposed to be no more .svn/format? because I'm in
> this weird loop: svn cleanup fails "can't remove
> blah/blah/.svn/format: no such file or directory" touch
> blah/blah/.svn/format; svn cleanup; "can't remove
> some/other/.svn/format".......
>
> And there is a relatively easy answer to that, contained in STATUS,
> slated for fixing in 1.6.1:
>
> * 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
>
>
> I'm guessing you bounced back and forth between 1.6 and 1.5 on that
> working copy?
>
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.
Barry
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1382489