Failed to find old revision of moved file

[Nicolas Goutte <ni...@snafu.de>]

I have a seen that Subversion has a problem with finding old revision of a 
moved file, for example:

LANG=C svn log -r1 http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/
README

results in:

svn: REPORT request failed on '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/
README'
svn: '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/README' path not found


Looking at the Subversion FAQ, it is written that similar problems are 
supposed to be fixed with version 1.1 but that seems not to be the case.

(The problem exists also when trying to access a file by a path instead of 
doing it by a URL.)

Is this a known behaviour? Is there already an issue (which I would have 
missed) about it?

Have a nice day!


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

Re: Failed to find old revision of moved file

[Nicolas Goutte <ni...@snafu.de>]

On Sunday 05 June 2005 21:44, Nicolas Goutte wrote:
> I have a seen that Subversion has a problem with finding old revision of a
> moved file, for example:
>
> LANG=C svn log -r1
> http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/ README
>
> results in:
>
> svn: REPORT request failed on
> '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/ README'
> svn: '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/README' path not found
>
>
> Looking at the Subversion FAQ, it is written that similar problems are
> supposed to be fixed with version 1.1 but that seems not to be the case.
>
> (The problem exists also when trying to access a file by a path instead of
> doing it by a URL.)
>
> Is this a known behaviour? Is there already an issue (which I would have
> missed) about it?

I have just found out that there is indeed an issue (#1482) about it, which I 
have missed when I had tried the first time to search for it:
http://subversion.tigris.org/issues/show_bug.cgi?id=1482

Have a nice day!

>
> Have a nice day!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org


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

Re: Failed to find old revision of moved file

[Kevin Puetz <pu...@puetzk.org>]

David Faure wrote:

> On Monday 06 June 2005 00:45, Max Bowsher wrote:
>> Nicolas Goutte wrote:
>> > On Sunday 05 June 2005 23:18, Max Bowsher wrote:
>> >> Nicolas Goutte wrote:

> Well, what about this then?
> svn log http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README
> shows that there was a revision number 2558 on that file, right?
> 
> svn diff -r1:2558
> http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README can even
> show you the patch of that revision.
> 
> Now, how do I get the log of that revision only?
> 
> svn log -r2558
> http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README svn:
> REPORT request failed on
> '/repos/svn/!svn/bc/2558/branches/1.1.x-r14063/doc/README' svn:
> '/repos/svn/!svn/bc/2558/branches/1.1.x-r14063/doc/README' path not found
> 
> Why does "svn log" show a revision, and a log, which can't be retrieved
> independently with svn log -r<rev> ? I know that the file moved since that
> revision, but that's a detail that one usually doesn't care about when
> looking at history. If I want to know why a given change was made, it
> doesn't matter to me where the file was when that change was made.

Right, but at present it matters to svn :-( The log has to be retrieved
under the pathname that the file had at that time.

> This problem affects KDE a lot, because everything got moved (reorganized)
> after the cvs2svn conversion, so any trip back in history hits this "no
> such revision" bug in svn log -r.

This is happening because of issue 2287
(http://subversion.tigris.org/issues/show_bug.cgi?id=2287). To fix it, svn
log ought to take a peg revision (like diff does), and then the renames
wouldn't mess it up. As the default peg revision is BASE (or HEAD if not in
a wc), it would even default right for this case then.


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

Re: Failed to find old revision of moved file

[David Faure <fa...@kde.org>]

On Monday 06 June 2005 00:45, Max Bowsher wrote:
> Nicolas Goutte wrote:
> > On Sunday 05 June 2005 23:18, Max Bowsher wrote:
> >> Nicolas Goutte wrote:
> >>> I have a seen that Subversion has a problem with finding old revision of
> >>> a moved file, for example:
> >>>
> >>> LANG=C svn log -r1
> >>> http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/ README
> >>>
> >>> results in:
> >>>
> >>> svn: REPORT request failed on
> >>> '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/ README'
> >>> svn: '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/README' path not
> >>> found
> >>
> >> That file does not exist in that revision. Thus a 'not found' error.
> >> Exactly as expected.
> >
> > Well, it depends what you expect.
> >
> > On one side a "svn log" gives such a revision number and when you want to 
> > do
> > anything with that revision number it does not work. That is not what I
> > expect. Sorry!
> 
> Well, no *I* don't expect svn log to give me revision numbers that don't 
> work, either. But I'm pretty sure there is no way you could have got svn log 
> to tell you that branches/1.1.x-r14063 existed in r1.
> 
> I think you have tried to show us a minimal example of your problem, but 
> have actually trimmed your actual problem away in trying to minimize the 
> example, leaving behind a useless command.

Well, what about this then?
svn log http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README
shows that there was a revision number 2558 on that file, right?

svn diff -r1:2558 http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README
can even show you the patch of that revision.

Now, how do I get the log of that revision only?

svn log -r2558 http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README
svn: REPORT request failed on '/repos/svn/!svn/bc/2558/branches/1.1.x-r14063/doc/README'
svn: '/repos/svn/!svn/bc/2558/branches/1.1.x-r14063/doc/README' path not found

Why does "svn log" show a revision, and a log, which can't be retrieved independently
with svn log -r<rev> ? I know that the file moved since that revision, but that's
a detail that one usually doesn't care about when looking at history. If I want to
know why a given change was made, it doesn't matter to me where the file was when
that change was made.

This problem affects KDE a lot, because everything got moved (reorganized) 
after the cvs2svn conversion, so any trip back in history hits this "no such revision" bug
in svn log -r.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).


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

Re: Failed to find old revision of moved file

[Nicolas Goutte <ni...@snafu.de>]

On Monday 06 June 2005 00:45, Max Bowsher wrote:
> Nicolas Goutte wrote:
> > On Sunday 05 June 2005 23:18, Max Bowsher wrote:
> >> Nicolas Goutte wrote:
> >>> I have a seen that Subversion has a problem with finding old revision
> >>> of a moved file, for example:
> >>>
> >>> LANG=C svn log -r1
> >>> http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/ README
> >>>
> >>> results in:
> >>>
> >>> svn: REPORT request failed on
> >>> '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/ README'
> >>> svn: '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/README' path not
> >>> found
> >>
> >> That file does not exist in that revision. Thus a 'not found' error.
> >> Exactly as expected.
> >
> > Well, it depends what you expect.
> >
> > On one side a "svn log" gives such a revision number and when you want to
> > do
> > anything with that revision number it does not work. That is not what I
> > expect. Sorry!
>
> Well, no *I* don't expect svn log to give me revision numbers that don't
> work, either. But I'm pretty sure there is no way you could have got svn
> log to tell you that branches/1.1.x-r14063 existed in r1.

Then at least the error message should be different. It should not be "path 
not found" but something like "revision does not exist for path".

>
> I think you have tried to show us a minimal example of your problem, but
> have actually trimmed your actual problem away in trying to minimize the
> example, leaving behind a useless command.

No, I really tried to get a single old revision and at first was surprised by 
the error. (The original case was on a file that was moved, as the module was 
re-organized.)

Now that I have understood the logic behind it, I find that the error message 
is misleading.

So perhaps my wish is a sort of --follow-life switch that follows moves for a 
log.

Have a nice day!

>
> Max.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org


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

Re: Failed to find old revision of moved file

[Max Bowsher <ma...@ukf.net>]

Nicolas Goutte wrote:
> On Sunday 05 June 2005 23:18, Max Bowsher wrote:
>> Nicolas Goutte wrote:
>>> I have a seen that Subversion has a problem with finding old revision of
>>> a moved file, for example:
>>>
>>> LANG=C svn log -r1
>>> http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/ README
>>>
>>> results in:
>>>
>>> svn: REPORT request failed on
>>> '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/ README'
>>> svn: '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/README' path not
>>> found
>>
>> That file does not exist in that revision. Thus a 'not found' error.
>> Exactly as expected.
>
> Well, it depends what you expect.
>
> On one side a "svn log" gives such a revision number and when you want to 
> do
> anything with that revision number it does not work. That is not what I
> expect. Sorry!

Well, no *I* don't expect svn log to give me revision numbers that don't 
work, either. But I'm pretty sure there is no way you could have got svn log 
to tell you that branches/1.1.x-r14063 existed in r1.

I think you have tried to show us a minimal example of your problem, but 
have actually trimmed your actual problem away in trying to minimize the 
example, leaving behind a useless command.

Max.


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

Re: Failed to find old revision of moved file

[Nicolas Goutte <ni...@snafu.de>]

On Sunday 05 June 2005 23:18, Max Bowsher wrote:
> Nicolas Goutte wrote:
> > I have a seen that Subversion has a problem with finding old revision of
> > a moved file, for example:
> >
> > LANG=C svn log -r1
> > http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/ README
> >
> > results in:
> >
> > svn: REPORT request failed on
> > '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/ README'
> > svn: '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/README' path not
> > found
>
> That file does not exist in that revision. Thus a 'not found' error.
> Exactly as expected.

Well, it depends what you expect.

On one side a "svn log" gives such a revision number and when you want to do 
anything with that revision number it does not work. That is not what I 
expect. Sorry!

Have a nice day!

>
> Max.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org


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

Re: Failed to find old revision of moved file

[Max Bowsher <ma...@ukf.net>]

Nicolas Goutte wrote:
> I have a seen that Subversion has a problem with finding old revision of a
> moved file, for example:
>
> LANG=C svn log -r1
> http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/ README
>
> results in:
>
> svn: REPORT request failed on
> '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/ README'
> svn: '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/README' path not 
> found

That file does not exist in that revision. Thus a 'not found' error.
Exactly as expected.

Max.


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