You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Eirik Bjørsnøs <ei...@gmail.com> on 2008/09/05 22:57:26 UTC

log -g fails on revision 31828

Doing an "svn log -g -r31828 http://svn.collab.net/repos/svn/" fails
for me in the middle of the response with:

svn: REPORT of '/repos/svn/!svn/bc/31828': 200 OK (http://svn.collab.net)

Is this a bug in Subversion or could it be related to the "Historical
surgery" as mentioned on http://svn.collab.net/ ?

I'm using svn version 1.5.2 (r32768)

Without -g, it works fine:

r31828 | cacknin | 2008-06-21 03:16:24 +0200 (Sat, 21 Jun 2008) | 7 lines

On the svnpatch-diff branch, bring up to sync with trunk(...)

Eirik.

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

Re: log -g fails on revision 31828

Posted by "C. Michael Pilato" <cm...@collab.net>.
C. Michael Pilato wrote:
> Eric Gillespie wrote:
>> Eirik Bjørsnøs <ei...@gmail.com> writes:
>>
>>> Doing an "svn log -g -r31828 http://svn.collab.net/repos/svn/" fails
>>> for me in the middle of the response with:
>>>
>>> svn: REPORT of '/repos/svn/!svn/bc/31828': 200 OK (http://svn.collab.net)
>>>
>>> Is this a bug in Subversion or could it be related to the "Historical
>>> surgery" as mentioned on http://svn.collab.net/ ?
>> It's a bug either way.
> 
> I see the following in Apache's error_log after trying this very command:
> 
> Provider encountered an error while streaming a REPORT response.  [400, #0]
> Failure opening '/trunk/contrib/client-side/svnmerge/svnmerge-migrate-histo\
> ry.py'  [400, #160016]
> Failure opening '/trunk/contrib/client-side/svnmerge/svnmerge-migrate-histo\
> ry.py'  [400, #160016]
> '/trunk/contrib/client-side/svnmerge' is not a directory in filesystem '/us\
> r/local/svn/repositories/svn/db'  [400, #160016]

Fixed in r32977, and proposed for backport to 1.5.3.

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand


Re: log -g fails on revision 31828

Posted by "C. Michael Pilato" <cm...@collab.net>.
C. Michael Pilato wrote:
> Eric Gillespie wrote:
>> Eirik Bjørsnøs <ei...@gmail.com> writes:
>>
>>> Doing an "svn log -g -r31828 http://svn.collab.net/repos/svn/" fails
>>> for me in the middle of the response with:
>>>
>>> svn: REPORT of '/repos/svn/!svn/bc/31828': 200 OK (http://svn.collab.net)
>>>
>>> Is this a bug in Subversion or could it be related to the "Historical
>>> surgery" as mentioned on http://svn.collab.net/ ?
>> It's a bug either way.
> 
> I see the following in Apache's error_log after trying this very command:
> 
> Provider encountered an error while streaming a REPORT response.  [400, #0]
> Failure opening '/trunk/contrib/client-side/svnmerge/svnmerge-migrate-histo\
> ry.py'  [400, #160016]
> Failure opening '/trunk/contrib/client-side/svnmerge/svnmerge-migrate-histo\
> ry.py'  [400, #160016]
> '/trunk/contrib/client-side/svnmerge' is not a directory in filesystem '/us\
> r/local/svn/repositories/svn/db'  [400, #160016]

I think I might have found the problem here.  Testing a fix for this
scenario now.  (I think we have a more general problem with trusting
svn:mergeinfo to be sane -- despite the fact that users can tweak it at will
-- in the server-side log logic, but there's already an issue filed to track
essentially that.)

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand


Re: log -g fails on revision 31828

Posted by "C. Michael Pilato" <cm...@collab.net>.
Eric Gillespie wrote:
> Eirik Bjørsnøs <ei...@gmail.com> writes:
> 
>> Doing an "svn log -g -r31828 http://svn.collab.net/repos/svn/" fails
>> for me in the middle of the response with:
>>
>> svn: REPORT of '/repos/svn/!svn/bc/31828': 200 OK (http://svn.collab.net)
>>
>> Is this a bug in Subversion or could it be related to the "Historical
>> surgery" as mentioned on http://svn.collab.net/ ?
> 
> It's a bug either way.

I see the following in Apache's error_log after trying this very command:

Provider encountered an error while streaming a REPORT response.  [400, #0]
Failure opening '/trunk/contrib/client-side/svnmerge/svnmerge-migrate-histo\
ry.py'  [400, #160016]
Failure opening '/trunk/contrib/client-side/svnmerge/svnmerge-migrate-histo\
ry.py'  [400, #160016]
'/trunk/contrib/client-side/svnmerge' is not a directory in filesystem '/us\
r/local/svn/repositories/svn/db'  [400, #160016]


-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand


Re: log -g fails on revision 31828

Posted by Eric Gillespie <ep...@pretzelnet.org>.
Eirik Bjørsnøs <ei...@gmail.com> writes:

> Doing an "svn log -g -r31828 http://svn.collab.net/repos/svn/" fails
> for me in the middle of the response with:
> 
> svn: REPORT of '/repos/svn/!svn/bc/31828': 200 OK (http://svn.collab.net)
> 
> Is this a bug in Subversion or could it be related to the "Historical
> surgery" as mentioned on http://svn.collab.net/ ?

It's a bug either way.

-- 
Eric Gillespie <*> epg@pretzelnet.org

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