Re: mod_dav_svn backward compatibility broken?

Eelco Dolstra <eelco@cs.uu.nl> writes:

> $ svn up
> svn: RA layer request failed
> svn: REPORT request failed on /repos/test
> svn: The REPORT request returned invalid XML in the response: Unknown
> XML element `repository-uuid (in
> http://subversion.tigris.org/xmlns/dav/)'. (/repos/test)

Ouch, this is a big problem. After release 0.18.0 and 0.18.1, we
rolled the UUID stuff into the trunk. The server now adds

<S2:repository-uuid>cb4d11d7-0fb8-0310-b2e3-bd6612ce3422</S2:repository-uuid>

elements within the update reports, which aren't understood by
anything but HEAD clients. libsvn_ra_dav is validating the report
language, and chokes on the new xml element around line 1723 or so:

 case ELEM_prop:
      if (child == ELEM_version_name
          || child == ELEM_creationdate
          || child == ELEM_creator_displayname
          || child == ELEM_md5_checksum
          || child == ELEM_repository_uuid /** Not present in 0.18 clients! */
          || child == ELEM_remove_prop)
        return NE_XML_VALID;
      else
        return NE_XML_DECLINE;

We're being bitten by our validator, which is being too strict, argh.

But we can't retroactively change released clients. mbk, we need to
come up with a solution here. Perhaps a different, more compatible
way to marshal the UUID from server to client. We can't release a
0.19 server that chokes earlier clients. :-(

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 4 17:59:46 2003