bzr crashed with ErrorFromSmartServer in _translate_error(): Error received from smart server: ('error', 'ValueError', "Absent factory for StaticTuple('requirements.master.-20101129082038-4vmtrh7lc3o626j7-19', '<email address hidden>')")

[Guilherme Salgado]

This happened when I tried to branch lp:~mwhudson/offspring/path-independence

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bzr 2.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
BzrDebugFlags: set()
BzrVersion: 2.3.4
CommandLine: ['/usr/bin/bzr', 'branch', 'lp:~mwhudson/offspring/path-independence']
CrashDb: bzr
Date: Tue Sep 20 15:35:07 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
Locale: en_GB.utf8
PackageArchitecture: all
Platform: Linux-2.6.38-11-generic-x86_64-with-Ubuntu-11.04-natty
ProcCmdline: /usr/bin/python /usr/bin/bzr branch lp:~mwhudson/offspring/path-independence
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LC_MESSAGES=en_US.UTF-8
 LANG=en_GB.utf8
 LANGUAGE=en_US:en
PythonVersion: 2.7.1
SourcePackage: bzr
Title: bzr crashed with ErrorFromSmartServer in _translate_error(): Error received from smart server: ('error', 'ValueError', "Absent factory for StaticTuple('requirements.master.-20101129082038-4vmtrh7lc3o626j7-19', '<email address hidden>')")
UpgradeStatus: Upgraded to natty on 2011-04-15 (158 days ago)
UserEncoding: UTF-8
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare sbuild tape video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #839336, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.