Comment 5 for bug 958551

Thanks Maarten. I'd really like to know what the commit message causing the issue was. If you can reproduce this, there are a couple of ways to go about doing that, perhaps the easiest would be:

$ BZR_PDB=1 bzr commit
... gets you into pdb debugger
> p repr(rev.message)

And include that (potentially large) output here.

Finally, can you try updating to the latest version of the bzr-builddeb plugin and see if the error still occurs, or comes in a different form? The hook that automatically filled out the commit message has been removed, so it should be possible to save what appears in the editor and attach it here. Thanks.