svn ci, svn propdel, svn ci fails without update

["rupert.thurner" <ru...@gmail.com>]

i noticed now with svn-1.7.1 a behaviour which i never noticed before,
but i am unsure if i just did not fall over it, or it was not there. a
"svn commit" does not seem to update the version of '.' even if it is
invalidated. so one must do a "svn up" after the commit, without
anybody else intermingling. it should not be like this, isn't it?

rupert @ unstable9s : ~/mgar-sav
$ svn up --ignore-externals
...
$ cd pkg/openldap/trunk
<do some changes>

$ svn ci -m "openldap, upgrade to 2.4.28"
Sending        Makefile
Sending        checksums
Transmitting file data ..
Committed revision 16340.

rupert @ unstable9s : ~/mgar-sav/pkg/openldap/trunk
$ svn proplist
Properties on '.':
  svn:ignore
  svn:externals

rupert @ unstable9s : ~/mgar-sav/pkg/openldap/trunk
$ svn propdel svn:externals
property 'svn:externals' deleted from '.'.

rupert @ unstable9s : ~/mgar-sav/pkg/openldap/trunk
$ svn ci -m "openldap, remove svn:external, mgar does not need it"
Sending        .
svn: E160042: Commit failed (details follow):
svn: E160042: File or directory '' is out of date; try updating
svn: E160024: resource out of date; try updating

rupert @ unstable9s : ~/mgar-sav/pkg/openldap/trunk
$ svn up
Updating '.':
At revision 16340.

rupert @ unstable9s : ~/mgar-sav/pkg/openldap/trunk
$ svn ci -m "openldap, remove svn:external, mgar does not need it"
Sending        .

Committed revision 16341.

Re: svn ci, svn propdel, svn ci fails without update

[Mark Phippard <ma...@gmail.com>]

On Wed, Nov 30, 2011 at 3:19 PM, rupert.thurner
<ru...@gmail.com> wrote:
> i noticed now with svn-1.7.1 a behaviour which i never noticed before,
> but i am unsure if i just did not fall over it, or it was not there. a
> "svn commit" does not seem to update the version of '.' even if it is
> invalidated. so one must do a "svn up" after the commit, without
> anybody else intermingling. it should not be like this, isn't it?


This should be on users@

That said, SVN has always worked this way.  You cannot alter the
properties of a folder unless the folder as HEAD and due to
mixed-revision working copies a folder will not be at HEAD after a
commit from its children until you run update.

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/