bzr-svn aborted on 'bzr branch'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Subversion Plugin |
New
|
Undecided
|
Jelmer Vernooij |
Bug Description
I tried to bzr branch a svn repo, and bzr aborted with this message and asking to file a report:
$ bzr branch $SVNROOT/
[======
Traceback (most recent call last):
File "/usr/lib/
return run_bzr(argv)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
revision_id, basis_dir)
File "/home/
result_repo = repo.clone(result, revision_id, basis)
File "/usr/lib/
return unbound(self, *args, **kwargs)
File "/usr/lib/
self.
File "/usr/lib/
return InterRepository
File "/usr/lib/
return unbound(self, *args, **kwargs)
File "/home/
self.
File "/home/
return unbound(self, *args, **kwargs)
File "/home/
self.callbacks, svn_config, None)
File "/usr/lib/
return apply(_
SubversionExcep
bzr 0.13.0 on python 2.4.4.candidate.1 (linux2)
arguments: ['/usr/bin/bzr', 'branch', 'svn+ssh://<email address hidden>
** please send this report to <email address hidden>
This is feisty's bzr 0.13-0u1 running on edgy, with the latest bzr-svn version that supports bzr 0.13.
Changed in bzr: | |
assignee: | nobody → jelmer |
I suspect this is a duplicate of memory-leaks, though not entirely sure. It's the only situation in which I've seen this exception though, and the number of revisions already pulled also appears to be quite high. I can't reproduce/debug this problem, because I'm not a gnome-games committer.