"bzr visualise/gannotate" asserts on certain per-file commit comments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
John A Meinel | ||
Bazaar GTK+ Frontends |
Fix Released
|
Undecided
|
John A Meinel |
Bug Description
bzr branch -r 'revid:<email address hidden>' https:/
bzr pull bzr-gcommit-
bzr viz --limit=1
gives me:
Traceback (most recent call last):
File "/home/
self.
File "/home/
file_info = bdecode(
File "/home/
r, l = decode_
File "/home/
v, f = decode_
File "/home/
k, f = decode_string(x, f)
File "/home/
n = long(x[f:colon])
ValueError: invalid literal for long() with base 10: ''
and the Per-file tab is empty though there was a per-file commit message at gcommit time.
The context is:
this revision was created by a colleague when using OS X (with X11), doing copy-paste from Thunderbird into gcommit, and pressing the "commit" button. It might be an issue of \r, \r\n...
It is for sure a bug in bzr or bzr-gtk and not a user error: as "bzr gcommit" managed to commit, "bzr viz" should be able to display the committed revision.
gannotate has same problem (see one post below).
Related branches
Changed in bzr: | |
assignee: | nobody → mbp |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in bzr: | |
assignee: | mbp → jameinel |
Changed in bzr-gtk: | |
assignee: | nobody → jameinel |
status: | New → In Progress |
Changed in bzr: | |
status: | Fix Committed → Fix Released |
Changed in bzr-gtk: | |
status: | Fix Committed → Fix Released |
latest bzr.dev, latest bzr-gtk