On Mon, Jan 16, 2012 at 08:29, Garret Wilson <garret_at_globalmentor.com> wrote:
> On 1/15/2012 11:16 PM, Stefan Küng wrote:
>> ...
>> * SVNKit is *not* an official svn package.
>
> OK, but in the absence of an official specification of Subversion
> properties, the behavior of clients in the wild is relevant, I would think.
http://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav/
>
>> * you're confusing DAV properties and SVN properties. Those are
>> completely different things.
>
> I don't know if you read the article I referenced. I'm aware of what
> WebDAV properties are---I implemented both a client and a server
> directly from RFC 2518 itself. The point here is that Subversion over
> mod_dav is yet another client implementation, and the Subversion
> properties I indicated can be set and retrieved over this client as
> well. (I'm pretty sure the mod_dav-based client is an "official" svn
> package.) So two Subversion clients (one official, one not) accepts
> these properties; TortoiseSVN does not. I'm trying to find out why.
Not just TSVN. All svn clients that use the svn library do not.
While the svn server behaves as much as DAV server as it can, there
are some differences. And svn clients first check svn properties for
validity in svn before they can be set. Your property is a valid DAV
property, but not a valid svn property. You might be able to set that
property with non-official clients, but that doesn't make them valid.
>> * the error you get is because your property name is in fact invalid
>> if used as an svn property: it must not contain spaces
>
> There are no spaces in the property name I provided. The article even
> points out the Unicode code points of the characters I'm using. And as I
svn properties must be utf8 encoded. And that's mentioned in every doc
about svn properties.
> mention, all the characters I'm using are valid XML name characters.
> (Yes, I know XML is not Subversion, but in the absence of a Subversion
> property specification, the fact that another widely-used and
> rigorously-documented/tested specification accepts these characters are
> valid name characters is surely germane, especially since the WebDAV
> Subversion implementation uses XML as its communication format and
> Subversion properties are stored as XML names.)
>
>> (for one, there
>> are more restrictions).
>
> If you could point me to some specification that indicates these
> restrictions, I would be grateful. So far you haven't mentioned any
> restrictions that apply to the property name I provided.
>
> I imagine that this problem ultimately lies on the Subversion side, but
> since the problem first arose for me on TortoiseSVN, I wanted to run it
> by the experts here. Thanks for any insight.
That's not true. Your blog post clearly mentions that you tried twice
on the svn list without success. Now you're trying here.
Understandable, but futile - TSVN is a client and uses the svn
library. Your problems and questions are not with TSVN but with the
svn library. I'm pretty sure that the official svn client (the command
line client) gave you the very same error message when you tried to
set your property.
Please try again on the svn list - since you haven't received any
answer to your questions on the users list, try the dev list.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2909099
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-01-16 11:02:26 CET