[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

ra_dav and mod_dav_svn target problem

From: Chia-liang Kao <clkao_at_clkao.org>
Date: 2003-08-05 18:10:48 CEST

Hi,

I'm testing some ra api with my new perl bindings work.
below is a chunk of code that people with knowledge of the api
should be able to understand easily:

my ($anchor, $target) = ('http://svn.collab.net/repos/svn/trunk',
                         'subversion/mod_authz_svn');

my ($fromrev, $rev) = (6183, 6185);

my $editor = new SVN::Delta::Editor(_debug => 1);

my $ra = SVN::Ra->new(url => $anchor, pool => $pool);

my $reporter =
    $ra->do_diff ($rev, $target, 1, 1, undef, $editor) ;

$reporter->set_path ('', $fromrev, 0, $pool);
$reporter->finish_report ();

the code sends out the expect report request:

<S:update-report xmlns:S="svn:"><S:src-path>http://svn.collab.net/repos/svn/trunk</S:src-path><S:target-revision>6185</S:target-revision><S:update-target>subversion/mod_authz_svn</S:update-target><S:ignore-ancestry>yes</S:ignore-ancestry><S:entry rev="6183"></S:entry></S:update-report>

but the server replies a 404 on
file not found: revision `6185', path `/trunk/mod_authz_svn/mod_authz_svn.c'

so it looks like that mod_dav_svn is ignoring the first part of the path
components (subversion/) in update-target.

you might ask why i don't put the first component of the target in
the anchor, but chances there are path foo/bar and foo/bar/deep are
created in the same revision, so i need to use foo as anchor and
bar/deep as target if i want to do_diff the first revision of
foo/bar/deep.

so is this a problem in mod_dav_svn? or there is some way else to
achieve the thing described above?

Cheers,
CLK

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 5 18:11:10 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.