Error when adding new property through Repository Browser

[Stefan Hett]

Hi,

when trying to add a new property via the repository browser (repro steps see below), I'm getting the following error popup and the property isn't added:

Steps to repro:

1. Open the repo browser
2. right click a directory -> Show properties
3. New... -> Log Sizes (assuming no log size limit entry svn property exists yet)
4. Set a minimum number of chars limit to 4 and press OK
5. add a log message and press ok

Actual result:
Error:
Subversion reported an error:
Directory '[...]' is out of date

Expected result:
svn property is added

I tried to find a corresponding report, but wasn't able to find one; still I have the feeling either I or someone else already reported this a while ago. So pardon me, if it's a duplicate.

-- 
Regards,
Stefan Hett, Developer/Administrator

EGOSOFT GmbH, Heidestrasse 4, 52146 Würselen, Germany
Tel: +49 2405 4239970, www.egosoft.com
Geschäftsführer: Bernd Lehahn, Handelsregister Aachen HRB 13473

[Stefan]

Could it be that between step 1 and 5 someone else made a commit to the repository?

"out of date" usually means you're not at HEAD. So for a WC, you need to run update.
For the repo browser, hitting F5 should do the trick.

Just tried this myself, and I don't get an error - but then this is my private repo where I'm the only one committing to it...

Stefan

[Stefan]

> [...]

Yes, I think that's what happened (i.e. someone committed something in
between these steps - though that would have been a commit to some
subnode of the one I tried to add a property to). Retrying it again,
everything works now.

Still, I'm wondering whether TSVN can't do anything about it. The repo
browser was pointing at HEAD so from a pure user's point of view
changing an SVN property and committing this change through the repo
browser shouldn't fail even if someone commits something (exception: a
property or tree change was done to the same node).

Unquestionably this is quite a rare case to run into and modifying svn
properties through the repo browser is not one of the most common use
cases IMO. So if this is nothing which can easily be changed and doesn't
point to some issue which changing/fixing would benefit more common
use-cases as well, I don't think investing more time here would be
worthwhile.

That said, thanks for taking the time to look into this and pointing out
the likely cause, Stefan.

Regards,
Stefan