Bazaar GTK+ Frontends

can't sign commits

Bug #436874 reported by Jijua
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Bazaar GTK+ Frontends
Incomplete
Undecided
Unassigned
Olive
Invalid
Undecided
Unassigned

Bug Description

During commit Olive is not able to sign with the required gpg key and does not allow to go on.
Note that command line "bzr commit" command works perfectly with my secret key.
Moreover, while viewing commits signed through command-line-commit in olive, the gui description reports that no sign is available.
Attached is a screenshot reporting the error on commit.

Linux ubuntu 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009 i686 GNU/Linux
Ubuntu 9.04

Revision history for this message
Jijua (jijua) wrote :
Revision history for this message
Aldo Latino (aldolat) wrote :

I confirm this behavior in Olive.

Jelmer Vernooij (jelmer)
summary: - Olive can't sign commits
+ can't sign commits
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This is definitely not a bug in Olive, as it calls out to bzr-gtk for committing.

Changed in olive:
status: New → Invalid
Changed in bzr-gtk:
status: New → Triaged
status: Triaged → Incomplete
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

bzr-gtk calls out to bzr for the actual signing. Do you have always_sign set ? Does "bzr commit" create signed commits?

Revision history for this message
Curtis Hovey (sinzui) wrote :

I think this is a dupe of 847388, or vise-versa since this same error is now recognised in bzr. My comment explain my hack and discusses the solutions https://bugs.launchpad.net/bzr/+bug/847388/comments/4

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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