You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Stefan Küng <to...@gmail.com> on 2005/10/09 08:15:58 UTC
svn info fails for non-HEAD revisions.
Hi,
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)
Since locks aren't there in non-HEAD revisions, I think 'svn info'
shouldn't try to fetch those locks at all for non-HEAD revs. At least it
shouldn't fail.
Oh, btw:
this happens with version 1.2.3 and my own compiled binary from the
1.3.x branch!
Since this is a very important function (talking about svn_client_info,
which I use a lot in TSVN), I'd very much appreciate it if this could be
fixed before the 1.3 release.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn info fails for non-HEAD revisions.
Posted by Stefan Küng <to...@gmail.com>.
On 10/10/05, Peter N. Lundblad <pe...@famlundblad.se> wrote:
> 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)
> >
> Should be fixed in r16626, which is proposed for 1.3.0 backport.
Thanks a lot!
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn info fails for non-HEAD revisions.
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
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)
>
Should be fixed in r16626, which is proposed for 1.3.0 backport.
thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn info fails for non-HEAD revisions.
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
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