cvs2svn test suite breakage caused by svn changes

Hello everybody,

The cvs2svn test suite was partly broken by some upstream changes in
svntest (r32463 and r32484), which in turn were made to support format
changes in the output of "svn proplist".

The cvs2svn test suite uses code from the SVN test suite via
svn:externals. Up until now, we have always imported the HEAD revision
of svntest rather than selecting a particular revision. Up until now,
that has not caused any serious problems :-)

This is an awkward situation because AFAICT the old version of svntest
won't work with a new Subversion build and vice versa. Since the
cvs2svn test suite doesn't know what SVN version the user has installed,
it has to work with any version.

From a broader perspective, it seems to me that the changes to the "svn
proplist" output could also break other tools. I haven't been following
the mailing list, so I don't know to what extent these changes were debated.

If these changes were indeed intentional, I suppose that our only
alternative would be to write a parser that can handle either form of
the output (or switch to parsing the XML output or using the SVN
bindings directly). Any other suggestions are welcome.

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-28 07:49:34 CEST