Bazaar

bzr crashed with BzrCheckError in _commit_write_group(): Internal check failed: Cannot add revision(s) to repository: missing referenced chk root keys: [StaticTuple('sha1:3c52a9038699157dee61f9bd1b03d255fa021805',)]

Bug #839515 reported by Matthias Klose on 2011-09-02

This bug report is a duplicate of: Bug #522637: BzrCheckError: Cannot add revision(s) to repository: missing referenced chk root keys. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Bazaar	Triaged	High	Unassigned
	bzr (Ubuntu)	Triaged	High	Unassigned

Bug Description

current oneiric 20110902, when running
bzr co lp:~ubuntu-desktop/unity/ubuntu

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bzr 2.4.0-3ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: wl
Architecture: i386
BzrDebugFlags: set()
BzrVersion: 2.4.0
CommandLine: ['/usr/bin/bzr', 'co', 'lp:~ubuntu-desktop/unity/ubuntu']
CrashDb: bzr
Date: Fri Sep 2 14:06:21 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
Locale: en_US.UTF-8
PackageArchitecture: all
Platform: Linux-3.0.0-9-generic-i686-with-Ubuntu-11.10-oneiric
ProcCmdline: /usr/bin/python /usr/bin/bzr co lp:~ubuntu-desktop/unity/ubuntu
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
PythonVersion: 2.7.2
SourcePackage: bzr
Title: bzr crashed with BzrCheckError in _commit_write_group(): Internal check failed: Cannot add revision(s) to repository: missing referenced chk root keys: [StaticTuple('sha1:3c52a9038699157dee61f9bd1b03d255fa021805',)]
UpgradeStatus: No upgrade log present (probably fresh install)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Matthias Klose (doko) wrote on 2011-09-02:

BzrLogTail.txt Edit (2.6 KiB, text/plain; charset="utf-8")
BzrPlugins.txt Edit (910 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (776 bytes, text/plain; charset="utf-8")
ProcStatus.txt Edit (776 bytes, text/plain; charset="utf-8")
PythonLoadedModules.txt Edit (33.8 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (3.5 KiB, text/plain; charset="utf-8")

visibility:

private → public

Apport retracing service (apport) on 2011-09-02

tags:

removed: need-duplicate-check

Revision history for this message

Jelmer Vernooij (jelmer) wrote on 2011-09-02:

Reproduced here using bzr.dev.

Changed in bzr (Ubuntu):
status:	New → Triaged
importance:	Undecided → High
Changed in bzr:
importance:	Undecided → High
status:	New → Triaged

Revision history for this message

Jelmer Vernooij (jelmer) wrote on 2011-09-02:

It seems like this is a stacking, one of the ones fixxed recently?

A workaround is to clone into a shared repository in which you have already checked out lp:unity:

$ bzr init-repo unity
$ bzr branch lp:unity unity/trunk
$ bzr co lp:~ubuntu-desktop/unity/ubuntu unity/ubuntu

Revision history for this message

Martin Packman (gz) wrote on 2011-09-02:

There are instructions in the existing bug for repairing an affected repository. It's a little worrying that something messed up the repo after the root cause was fixed.