On Sun, 9 Oct 2005, Stefan Küng wrote:
> svn info fails sometimes when it shouldn't fail. If you call svn info
> with -r and a non-HEAD revision, it fails with
> Failed to fetch lock information: 404 Not Found (https://192.168.2.2)
>
> And it even fails when I give HEAD as the peg revision.
>
> To reproduce:
>
> $ svnadmin create test
> Assume the URL to the new repository is https://192.168.2.2/svn/test
> (note: it works for file:///, but it fails for http/https).
> $ svn co https://192.168.2.2/svn/test test
> $ cd test
> $ echo test > testfile.txt
> $ svn add testfile.txt
> $ svn ci -m "adding testfile"
> $ echo testing > testfile.txt
> $ svn ci -m "modifying testfile"
> $ svn mkdir https://192.168.2.2/svn/test/TestFolder -m "create folder"
> $ svn mv https://192.168.2.2/svn/test/testfile.txt
> https://192.168.2.2/svn/test/TestFolder/testfile.txt -m "move file"
> $ svn up
> $ cd TestFolder
> $ svn info https://192.168.2.2/svn/test/TestFolder/testfile.txt
> this works
> $ svn info https://192.168.2.2/svn/test/TestFolder/testfile.txt@HEAD -r1
> Failed to fetch lock information: 404 Not Found (https://192.168.2.2)
>
Yes, this is a bug, and what is worse is that we request the lock on the
wrong path in this case, so we also give the wrong information. I'm
working on sussman's proposal in:
http://svn.haxx.se/dev/archive-2005-04/1123.shtml
What we fail to do is to make sure that the path is the same in head as
the peg revision before fetching a lock.
Thanks for the clear recipe,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 9 21:28:22 2005