On Tue, 26 Jul 2011 11:53:15 +0000, Les Mikesell wrote:
> On 7/26/2011 11:42 AM, Andreas Krey wrote:
> >This is one of the high strangitude svn behaviour artefacts: That you
> >can't do two consecutive commits without getting an error (in some
> >relatively popular cases).
> And you generally shouldn't be doing that unless there is some special
> need to avoid picking up concurrent changes
No, there are no concurrent changes. I'm the only one working the repo;
For the second of the back-to-back commits I got the error, which is
easily explained when you know about mixed revisions and that. But at the
same time it looks utterly idiotic, since the WC was up to date before,
so how can it possibly be not up to date after the first commit.
rm -rf repo wc
svnadmin create repo
svn checkout file:///`pwd`/repo wc
touch A D/B D/C E
# svn add . # <- That nuisance 'already under control'...
svn add A D E
svn commit -m 'initial'
svn propset blub blah .
svn commit D -m green
svn commit . -m blau
And output (i'm on 1.6.6, however):
+ rm -rf repo wc
+ svnadmin create repo
+ svn checkout file:////Users/andreaskrey/svnt/wc/repo wc
Checked out revision 0.
+ cd wc
+ mkdir D
+ touch A D/B D/C E
+ svn add A D E
+ svn commit -m initial
Transmitting file data ....
Committed revision 1.
+ svn up
At revision 1.
+ svn propset blub blah .
property 'blub' set on '.'
+ svn commit D -m green
Transmitting file data .
Committed revision 2.
+ svn commit . -m blau
svn: Commit failed (details follow):
svn: Directory '/' is out of date
Received on 2011-07-26 20:48:19 CEST