C. Michael Pilato wrote:
> Eric Gillespie wrote:
>> Eirik Bjørsnøs <eirbjo_at_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 <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2008-09-08 23:42:49 CEST