Merge, diff etc fails strangely - is this a bug?

Hi all,
I'm just setting up svn for some projects I'm working on, anyway, everything is sweet (so much better than CVS last time I used it), all running through apache2 in a virtual host.

But I have a problem, I have a "tag" which I made a little prematurely and want to merge some changes from the trunk into it, (yeah, it's treating the tag like a branch, but it's my repository :-)).

So I check out the tag revision into a working directory..

        boffin_at_mortimer:~$ svn co http://svn.gogo.co.nz:81/oss/gogoXML/tags/v0.5 gogoXML
        A gogoXML/gogoXMLcdata.php
        ...snip...
        Checked out revision 8.

then I cd into the directory and try to merge the changes that happened between the appropriate revisions in the trunk..

        boffin_at_mortimer:~/gogoXML$ svn merge -r 3:HEAD http://svn.gogo.co.nz:81/oss/gogoXML/trunk
        svn: Apache got a malformed URI
        svn: REPORT request failed on '/oss/gogoXML/trunk'
        svn:
        The specified URI does not refer to this repository, so it is unusable.

So it's telling me there is some problem in the URI, but I know that the URL to the trunk repository is correct because I can check it out ...

        boffin@mortimer:~/gogoXML$ cd ..
        boffin_at_mortimer:~$ svn co http://svn.gogo.co.nz:81/oss/gogoXML/trunk gogoXML_trunk
        A gogoXML_trunk/gogoXML.php
        ...snip...
        Checked out revision 8.

The apache log file doesn't seem to shed any light on the matter...

        [Sun May 11 02:15:56 2003] [error] [client 203.79.122.38] Could not parse dst-path URL. [500, #190001]
        [Sun May 11 02:15:56 2003] [error] [client 203.79.122.38] (17)File exists: The specified URI does not refer to this repository, so it is unusable. [500, #190001]

I'm just a noob with svn, I did use it about 6 months ago at my previous employer but wasn't running it through apache2, I didn't run across this issue - but it looks like a bug to me, or am I doing something incorrectly ?

FWIW, this is with version 0.21.0 (r5639) - the latest one in debian-unstable, I'd rather not install from source and then have to uninstall when the debs get up to v22, and I couldn't see any issues fixed or otherwise that resemble this in the issuezilla.

You should be able to try this out yourself (no write access though) if I've got my apache setup correctly, it's a very small project so no problem checking the whole trunk/tag out (just watch that you connect on port 81, 80 is my apache1.3).

Thanks all.

---
James Sleeman
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org