Bazaar

bzr crashed with NoSuchRevision in _translate_error()

Bug #723735 reported by James Hunt
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned
bzr (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: bzr

Running, "bzr push -v lp:~jamesodhunt/upstart/0.9" caused bzr to crash with an error relating to a missing revision (as shown in apport output).

This line looks rather suspicious btw:

ProcCmdline: /usr/bin/python /usr/bin/bzr push -v lp:~usernameodhunt/upstart/0.9
                                                                                    =============

Seems to be an amalgam of "username" and my lp username "jamesodhunt" (!?!)

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: bzr 2.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic-pae 2.6.35.10
Uname: Linux 2.6.35-25-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
BzrDebugFlags: set()
BzrVersion: 2.2.1
CommandLine: ['/usr/bin/bzr', 'push', '-v', 'lp:~jamesodhunt/upstart/0.9']
CrashDb: bzr
Date: Wed Feb 23 14:18:24 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.6
Locale: en_GB.utf8
Platform: Linux-2.6.35-25-generic-pae-i686-with-Ubuntu-10.10-maverick
ProcCmdline: /usr/bin/python /usr/bin/bzr push -v lp:~usernameodhunt/upstart/0.9
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.utf8
PythonVersion: 2.6.6
SourcePackage: bzr
Title: bzr crashed with NoSuchRevision in _translate_error()
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild

Revision history for this message
James Hunt (jamesodhunt) wrote :
Apport retracing service (apport)
tags: removed: need-duplicate-check
Revision history for this message
James Hunt (jamesodhunt) wrote :

The branch lp:~jamesodhunt/upstart/0.9 *does* appear on my lp page but in what state I wonder? I tried re-pushing with --overwrite but bzr says:

  No new revisions to push.
  Nothing seems to have changed

Revision history for this message
James Hunt (jamesodhunt) wrote :

I got the same error when I attempted to push the same branch to: lp:~upstart-devel/upstart/0.9

James Hunt (jamesodhunt)
visibility: private → public
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Does this also fail with just "bzr push" rather than "bzr push -v" ?

Changed in bzr (Ubuntu):
status: New → Confirmed
Changed in bzr:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
James Hunt (jamesodhunt) wrote :

@jelmer: you are correct - the problem is caused by the verbose option:

# SUCCESS
$ bzr push lp:~jamesodhunt/upstart/ignore-me-testing123

# FAILS
$ bzr push -v lp:~jamesodhunt/upstart/ignore-me-testing321

Although bzr displays a stack trace, it does appear that the branch *is* successfully pushed (since "bzr diff --old lp:~jamesodhunt/upstart/ignore-me-testing321", for example, reports no output), however I would like confirmation that this bug isn't fatal to the pushed branch!

Jelmer Vernooij (jelmer)
Changed in bzr (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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