frankgilroy wrote on Tue, 22 Jul 2008 at 11:36 -0700:
>
> We’re running across an issue when using svn log on one of our repositories.
> We regularly execute a command like the following for reporting purposes:
>
> svn log --xml --non-interactive https://our.server.com/svn/TEST/
>
> When we run this command it truncates the output at a revision that has a
> strange character in the log message. It fails to put the closing </log> in
> the XML
Is this fixed by r31875 (which will be in 1.5.1, released next week)?
> and spits out the following message:
>
> svn: REPORT of '/svn/TEST/!svn/bc/154': 200 OK
>
> I noticed that the revprops file for the offending revision contains a
> special character and gets recognized as ISO-8859 as opposed to ASCII like
> all of the rest of the 7000+ revprops files.
> I have attached that revprops file.
>
No you haven't.
> I’m told that newer versions of subversion don’t allow log messages with bad
> characters. But I’m wondering if it could be patched to file more
> gracefully for existing log messages with bad characters. Our audit folks
> don't want us going back and mucking with old log messages.
>
Subversion has always required log messages to be in UTF-8; what trunk
does differently is enforce this at commit time (see validate_prop() in
libsvn_repos/fs-wrap.c). Trunk svn will reject commits whose log messages
are not UTF-8.
I don't think any changes has been made (yet) in the other direction
(client reading properties from repos) -- I expect 1.4 to fail in the same
way.
> Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-22 21:14:32 CEST