bzr crashed with KeyError in get_revision_paths(): 'missing revision paths for 78'

Bug #936562 reported by Marius Gedminas
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bzr-svn (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Try this:

    bzr branch http://mg.pov.lt/eazysvn/svn/ eazysvn-bzr

I get a traceback:

    KeyError: 'missing revision paths for 78'

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bzr 2.4.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
BzrDebugFlags: set()
BzrVersion: 2.4.2
CommandLine:
 ['/usr/bin/bzr',
  'branch',
  'svn+ssh://fridge/home/mg/svn/eazysvn',
  'eazysvn-bzr']
CrashDb: bzr
Date: Mon Feb 20 00:12:35 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.7
Locale: lt_LT.UTF-8
PackageArchitecture: all
Platform: Linux-3.0.0-16-generic-i686-with-Ubuntu-11.10-oneiric
ProcCmdline: /usr/bin/python /usr/bin/bzr branch svn+ssh://fridge/home/username/svn/eazysvn eazysvn-bzr
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=lt_LT.UTF-8
 LANGUAGE=lt_LT:lt:en_GB:en
 LC_CTYPE=lt_LT.UTF-8
PythonVersion: 2.7.2
SourcePackage: bzr
Title: bzr crashed with KeyError in get_revision_paths(): 'missing revision paths for 78'
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (129 days ago)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Marius Gedminas (mgedmin) wrote :
visibility: private → public
Revision history for this message
Marius Gedminas (mgedmin) wrote :

(The same error happens when I use the svn+ssh:// url pointing to the same repository, except you won't be able to reproduce it without a user account. I accidentally invoked apport-bug with the crash dump that used the private ssh url instead of the public http one, sorry if that causes any confusion.)

tags: removed: need-duplicate-check
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This was a bug in bzr-svn that could occur when the "fetching revision info" step was interrupted.

Newer versions of bzr-svn will no longer get you into this situation, but the data in the bzr-svn cache may still be broken. You can delete it by removing ~/.cache/bazaar/svn/4fc293c4-4eed-0310-a01a-b4ad72f90fad or ~/.bazaar/svn-cache/4fc293c4-4eed-0310-a01a-b4ad72f90fad

Looking at the contents of the repository, it seems like you probably want to run either:

$ bzr branch http://mg.pov.lt/eazysvn/svn/trunk eazysvn-bzr

(to clone just trunk)

or

$ bzr svn-import bzr branch http://mg.pov.lt/eazysvn/svn/ eazysvn-bzr

(to clone all branches in the repository)

Changed in bzr-svn (Ubuntu):
status: New → Fix Released
Revision history for this message
Marius Gedminas (mgedmin) wrote :

Thank you, yes, rm -r ~/.cache/bazaar/svn/4fc293c4-4eed-0310-a01a-b4ad72f90fad made the error go away.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.