Hyrum K Wright <hyrum.wri...@wandisco.com> writes: > I tried this again using serf, and a WC->REPO copy works just fine; it > only fails on a REPO->REPO copy. > >> Any clues in the server error log? > > The server log gives: > [Tue Sep 06 08:12:02 2011] [error] [client xxx.xxx.xxx.79] Querying > mergeinfo requires version 3 of the FSFS filesystem schema; filesystem > '/var/svn/repos/hikehy/db' uses only version 2 [501, #200007] > [Tue Sep 06 08:12:02 2011] [error] [client xxx.xxx.xxx.79] Querying > mergeinfo requires version 3 of the FSFS filesystem schema; filesystem > '/var/svn/repos/hikehy/db' uses only version 2 [501, #200007] > > After upgrading the filesystem on the server, the problem disappears, > and I can create the tag using ra_serf. > > What's interesting about this is that ra_neon didn't require querying > mergeinfo (or at least didn't fail when doing so) and ra_serf did.
I can reproduce it by creating a repository using --pre-1.5-compatible. I see the error log entry for both neon and serf. The entry in the error log doesn't correspond to the serf call that fails, it is generated when libsvn_client/copy.c:repos_to_repos_copy calls svn_client__get_repos_mergeinfo, and that error is cleared because squelch_incapable is TRUE. However a subsequent call to svn_ra_check_path fails in serf.c:fetch_path_props and seems to do so without contacting the server. Perhaps serf is failing to clear an internal error? I think we should raise an issue. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com