Re: [PATCH] Change test suite to read file properties in XML format [was: Re: cvs2svn test suite breakage caused by svn changes]

James Abbatiello <[email protected]>
Newsgroups gmane.comp.version-control.subversion.cvs2svn.devel
Message-ID <71bc59e60907271004h5eaa5ff3qb4ec3444557059e4__7157.0027423606$1248717270$gmane$org@mail.gmail.com>
On Mon, Jul 27, 2009 at 11:15 AM, Michael Haggerty<[email protected]> wrote:
> James, thanks for testing this.  It would be trivial to add the
> EOL-fixing code to my patch, but first I want to understand it because I
> fear there is a deeper problem.
>
> After digging through more Subversion code I found that the handling of
> property values is strange (and not very consistent).  Even in the case
> of XML output, where I had expected the data to come out 1:1, SVN munges
> properties that start with "svn:" while they are being output.  I hadn't
> expected that.
>
> But even though SVN outputs '\r\n' on Windows, I still don't understand
> how the '\r\n' characters get through in the test suite.

This had me stumped for a while too.
C:>svn --version
svn, version 1.6.3 (r38063)
   compiled Jun 18 2009, 12:57:17
...

C:>svn proplist --verbose --xml svntest
<?xml version="1.0"?>
<properties>
<target
   path="svntest">
<property
   name="svn:ignore">*.pyc&#13;
*.o&#13;
*~&#13;
.*~&#13;
&#13;
</property>
</target>
</properties>

The '\r\n' sequences are being folded to '\n'.  But then the XML
parser turns '&#13\n' into '\r\n' in the final output.


> Perhaps there is a cygwin issue or something.  James, what does
>
>    python -c 'import sys; print sys.platform'
>
> print on your computer?

It prints win32.  I'm running windows python not cygwin python.

-- 
James Abbatiello

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2376061

To unsubscribe from this discussion, e-mail: [[email protected]].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.