failure while cloning a https/svn branch

[Stefan Monnier]

When I try to branch from the upstream svn repository I first get:

   % LC_ALL=C bzr clone https://svn.rice.edu/r/rap/Acumen
   HTTPS svn.rice.edu, Realm: 'Rice Subversion' username: <foo>
   HTTPS <foo>@svn.rice.edu, Realm: 'Rice Subversion' password: <bar>
   [\ ] 1KB 1KB/s | fetching svn revision info 0/14436

Then the 0 strarts counting up til about 994, at which point the thing
appears to hang for a while (a few minutes), and finally ends with the
traceback below. This is a Debian testing system, in case it matters.

        -- Stefan

bzr: ERROR: subvertpy.SubversionException: ("REPORT of '/r/rap/!svn/bc/14436': 200 OK (https://svn.rice.edu)", 175002)

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 835, in exception_to_return_code
    return the_callable(*args, **kwargs)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 1030, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 647, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.5/site-packages/bzrlib/builtins.py", line 1204, in run
    from_location)
  File "/usr/lib/python2.5/site-packages/bzrlib/bzrdir.py", line 952, in open_tree_or_branch
    return bzrdir._get_tree_branch()
  File "/usr/lib/python2.5/site-packages/bzrlib/bzrdir.py", line 937, in _get_tree_branch
    branch = self.open_branch()
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/svn/remote.py", line 225, in open_branch
    branch = SvnBranch(repos, self.branch_path)
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/svn/branch.py", line 175, in __init__
    self.layout = self.repository.get_layout()
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/svn/repository.py", line 653, in get_layout
    return self.get_layout_source()[0]
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/svn/repository.py", line 675, in get_layout_source
    self._find_guessed_layout()
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/svn/repository.py", line 694, in _find_guessed_layout
    revnum, self._hinted_branch_path)
  File "/usr/lib/python2.5/site-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.5/site-packages/bzrlib/plugins/svn/logwalker.py", line 176, in iter_changes
    self._fetch_revisions(max(from_revnum, to_revnum), pb=pb)
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/svn/logwalker.py", line 248, in _fetch_revisions
    self.actual._transport.get_log(rcvr, [""], self.saved_revnum, to_revnum, 0, True, True, False, todo_revprops)
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/svn/transport.py", line 467, in get_log
    revprops)
SubversionException: ("REPORT of '/r/rap/!svn/bc/14436': 200 OK (https://svn.rice.edu)", 175002)

bzr 1.17 on python 2.5.4 (linux2)
arguments: ['/usr/bin/bzr', 'clone', 'https://svn.rice.edu/r/rap/Acumen']
encoding: 'ANSI_X3.4-1968', fsenc: 'ANSI_X3.4-1968', lang: 'fr_CH.UTF-8'
plugins:
  bzrtools /usr/lib/python2.5/site-packages/bzrlib/plugins/bzrtools [1.17]
  launchpad /usr/lib/python2.5/site-packages/bzrlib/plugins/launchpad [1.17]
  netrc_credential_store /usr/lib/python2.5/site-packages/bzrlib/plugins/netrc_credential_store [1.17]
  svn /usr/lib/python2.5/site-packages/bzrlib/plugins/svn [1.0]
*** 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.

[Stefan Monnier (monnier)]

I just saw that Debian testing is a bit behind the times in some of those tools, so I upgraded bzr to 2.0.1 and python-subvertpy to 0.7.0 (both via Debian unstable), but it made no difference and the backtrace is identical.

[Jelmer Vernooij (jelmer)]

Does "svn log -r1:14436 -v https://svn.rice.edu/r/rap" work?

[Stefan Monnier (monnier)]

> Does "svn log -r1:14436 -v https://svn.rice.edu/r/rap" work?

Hmmm.... indeed it seems to stop after r1025.
And "svn log -v https://svn.rice.edu/r/rap" gives me most of the rest
but stops at r1181 (starting from 14436).
The repository works just fine for "normal" accesses, tho.
And git-svn had no problem checking it out, FWIW.

        Stefan

[Jelmer Vernooij (jelmer)]

This seems like a problem in Subversion. I suspect git-svn doesn't pull down the full history and might therefore not have this problem.

[Stefan Monnier (monnier)]

> This seems like a problem in Subversion. I suspect git-svn doesn't pull
> down the full history and might therefore not have this problem.

git-svn did report some warnings. In any case
https://svn.rice.edu/r/rap/Acumen did not exist in most of the
repository's life (I think it was created on revision 11646).

git-svn did give me the whole history from that first commit, although
it also did output some warnings while doing it, but IIUC those warnings
were about the fact that https://svn.rice.edu/r/rap/Acumen didn't exist
in the too distant past.

While I understand that there might be a problem in the repository,
I have no control over that repository (tho I do have commit access to
it), so I can't really fix it. Currently I use git-svn rther than
bzr-svn, but I'd rather use bzr-svn if possible.

Would it be possible to work around the problem by instructing bzr-svn
to start at revision 11646?

        Stefan

[Jelmer Vernooij (jelmer)]

On Tue, 2009-11-03 at 14:32 +0000, Stefan Monnier wrote:
> > This seems like a problem in Subversion. I suspect git-svn doesn't pull
> > down the full history and might therefore not have this problem.
>
> git-svn did report some warnings. In any case
> https://svn.rice.edu/r/rap/Acumen did not exist in most of the
> repository's life (I think it was created on revision 11646).
>
> git-svn did give me the whole history from that first commit, although
> it also did output some warnings while doing it, but IIUC those warnings
> were about the fact that https://svn.rice.edu/r/rap/Acumen didn't exist
> in the too distant past.
>
> While I understand that there might be a problem in the repository,
> I have no control over that repository (tho I do have commit access to
> it), so I can't really fix it. Currently I use git-svn rther than
> bzr-svn, but I'd rather use bzr-svn if possible.
>
> Would it be possible to work around the problem by instructing bzr-svn
> to start at revision 11646?
This should be possible, but there are some buts. We would need to have
references to the older revisions if we do this, to ensure referential
integrity. These revisions would be ghosts in the local branch.

Potentially the local branch could be stacked onto the original
Subversion branch. This requires inter-format stacking support in
bzrlib, which is not there (yet).

Alternatively, we can support such a clone *without* stacking but that
requires some (relatively trivial) UI support in Bazaar. E.g. "bzr
branch --last 5 <url> <local-dir>" to fetch only the last 5 revisions.

Cheers,

Jelmer

--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>