175002 error during REPORT: 200 OK

[Marius Gedminas]

$ bzr branch http://jrfonseca.googlecode.com/svn/trunk/xdot xdot-bzr
bzr: ERROR: subvertpy.SubversionException: ("REPORT of '/svn/!svn/bc/272': 200 OK (http://jrfonseca.googlecode.com)", 175002)

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 716, in exception_to_return_code
    return the_callable(*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 911, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 547, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.6/dist-packages/bzrlib/builtins.py", line 1070, in run
    from_location)
  File "/usr/lib/python2.6/dist-packages/bzrlib/bzrdir.py", line 913, in open_tree_or_branch
    return bzrdir._get_tree_branch()
  File "/usr/lib/python2.6/dist-packages/bzrlib/bzrdir.py", line 898, in _get_tree_branch
    branch = self.open_branch()
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/remote.py", line 187, in open_branch
    branch = SvnBranch(repos, self.branch_path)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/branch.py", line 127, in __init__
    self.layout = self.repository.get_layout()
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/repository.py", line 603, in get_layout
    return self.get_layout_source()[0]
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/repository.py", line 625, in get_layout_source
    self._find_guessed_layout()
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/repository.py", line 643, in _find_guessed_layout
    revnum, self._hinted_branch_path)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/layout/guess.py", line 143, in repository_guess_layout
    repository._log.iter_changes(None, revnum, max(0, revnum-GUESS_SAMPLE_SIZE)), revnum, branch_path)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/logwalker.py", line 246, in iter_changes
    self._fetch_revisions(max(from_revnum, to_revnum), pb=pb)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/logwalker.py", line 328, in _fetch_revisions
    self.actual._transport.get_log(rcvr, [""], self.saved_revnum, to_revnum, 0, True, True, False, todo_revprops)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/svn/transport.py", line 390, in get_log
    revprops)
SubversionException: ("REPORT of '/svn/!svn/bc/272': 200 OK (http://jrfonseca.googlecode.com)", 175002)

bzr 1.13.1 on python 2.6.2 (linux2)
arguments: ['/usr/bin/bzr', 'branch', 'http://jrfonseca.googlecode.com/svn/trunk/xdot', 'xdot-bzr']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'lt_LT.UTF-8'
plugins:
  etckeeper /usr/lib/python2.6/dist-packages/bzrlib/plugins/etckeeper [unknown]
  gtk /usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk [0.96.0.dev.1]
  launchpad /usr/lib/python2.6/dist-packages/bzrlib/plugins/launchpad [unknown]
  netrc_credential_store /usr/lib/python2.6/dist-packages/bzrlib/plugins/netrc_credential_store [unknown]
  svn /usr/lib/python2.6/dist-packages/bzrlib/plugins/svn [0.5.3]
*** Bazaar has encountered an internal error.
    Please report a bug at https://bugs.launchpad.net/bzr/+filebug
    including this traceback, and a description of what you
    were doing when the error occurred.

[Jelmer Vernooij (jelmer)]

As we discussed on IRC, this isn't a bug in bzr-svn itself but either in the Google server code or in libsvn since this problem also occurs when using the command-line svn client:

svn log -v -r2 http://jrfonseca.googlecode.com/svn

[fredhoare (fred-hoare)]

This is probably a bug in the mod_dav_svn code. See http://subversion.tigris.org/issues/show_bug.cgi?id=3102.

It was fixed in svn 1.5.6 and 1.6.0

I was having this problem with an svn 1.5.5 server and after upgrading it 1.5.7 things are working fine.

[Bojan Nikolic (bojan-bnikolic)]

I'm having this problem too, but I do not think it is svn server related. This works fine:

svn log -v -r2 https://xlw.svn.sourceforge.net/svnroot/xlw

But this fails:

bzr branch https://xlw.svn.sourceforge.net/svnroot/xlw/trunk xlw-trunk

[Jelmer Vernooij (jelmer)]

Hi Bojan,

On Mon, 2009-11-30 at 09:02 +0000, Bojan Nikolic wrote:
> I'm having this problem too, but I do not think it is svn server
> related. This works fine:
>
> svn log -v -r2 https://xlw.svn.sourceforge.net/svnroot/xlw
>
> But this fails:
>
> bzr branch https://xlw.svn.sourceforge.net/svnroot/xlw/trunk xlw-trunk
>
> ** Attachment added: "crash file"
> http://launchpadlibrarian.net/36252749/bzr-20091130090122-11512.crash
>

Please try this command:

svn log -v https://xlw.svn.sourceforge.net/svnroot/xlw

This also breaks halfway in the same way as the "bzr branch" command.

[Bojan Nikolic (bojan-bnikolic)]

I take that back, svn fails too on one of the revisions:

svn log -v -r127 https://xlw.svn.sourceforge.net/svnroot/xlw
svn: REPORT of '/svnroot/xlw/!svn/bc/127': 200 OK (https://xlw.svn.sourceforge.net)

[Daniel Clemente (n142857)]

Another case with latest bzr.dev and bzr-svn:
# bzr branch https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/trunk tikiwiki-bzr
→
SubversionException: ("REPORT de '/svnroot/tikiwiki/!svn/bc/25961': 200 OK (https://tikiwiki.svn.sourceforge.net)", 175002)

However, this works:
svn log -v -r25961 https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/trunk

25961 is the latest revision. See:
# svn log -v -r25960 https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/trunk
# svn log -v -r25962 https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/trunk
svn: No such revision 25962

[Jelmer Vernooij (jelmer)]

25961 wouldn't necessarily be the broken revision but rather the start of the range for which the log was requested. In tikiwiki's case, it looks like the broken revision is 9915:

svn log -r9915 -v http://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki

[Jelmer Vernooij (jelmer)]

Sorry about using Medium.

These are essentially broken repositories, and fixing this will require libsvn and/or libneon hacking and perhaps even mod_dav_svn hacking (and upgrading the remote servers). I don't see that happening in the next 6 months.