bzr vis crashed with KeyError in linegraph()

Bug #399405 reported by Marius Gedminas
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar GTK+ Frontends
Invalid
Low
Unassigned
bzr-gtk (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bzr-gtk

I've created two bzr branches from an upstream svn repository with bzr-svn. One was created a long time ago and has a bunch of local changes. Now I'd like to see how the two branches diverged, so I do

  bzr vis branch1 branch2

and get a KeyError in my teeth. (Apport will attach the complete traceback, I presume.)

The branches are public, you can get the one that was created a long time ago and modified with

  bzr branch lp:~mgedmin/pyflakes/pyflakes-mg

and you can get a fresh one from upstream svn with

  bzr branch http://divmod.org/svn/Divmod/trunk/Pyflakes

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/bzr
InterpreterPath: /usr/bin/python2.6
Package: bzr 1.13.1-1
ProcCmdline: /usr/bin/python /usr/bin/bzr vis pyflakes-bzr pyflakes-username
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=lt_LT.UTF-8
 LC_CTYPE=lt_LT.UTF-8
PythonArgs: ['/usr/bin/bzr', 'vis', 'pyflakes-bzr', 'pyflakes-username']
SourcePackage: bzr
Title: bzr crashed with KeyError in linegraph()
Uname: Linux 2.6.28-13-generic i686
UserGroups: adm admin audio cdrom davfs2 dialout dip floppy fuse lpadmin netdev plugdev powerdev pulse-rt sambashare scanner vboxusers video

Revision history for this message
Marius Gedminas (mgedmin) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Jelmer Vernooij (jelmer)
Changed in bzr-gtk:
status: New → Confirmed
status: Confirmed → Triaged
importance: Undecided → Low
Changed in bzr-gtk (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in bzr-gtk (Ubuntu):
status: Confirmed → Invalid
Changed in bzr-gtk:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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