Signing commits with Breezy
Martin Steigerwald
martin at lichtvoll.de
Mon Oct 29 20:31:02 UTC 2018
Hi Jelmer.
Thank you for your quick reply. I am subscribed to the list, so no need
to Cc me.
Jelmer Vernooij - 29.10.18, 18:52:
> On Mon, Oct 29, 2018 at 12:26:33PM +0100, Martin Steigerwald wrote:
> > I switched from Bazaar to Breezy some time ago.
> >
> > And after making sure that the signing plugin is in the right
> > directory, Breezy still used it, although "brz plugins" shows:
> >
> > signing (failed to load)
> >
> > ** Unable to load plugin 'signing' from
> > '/home/martin/.config/breezy/
> >
> > plugins/signing': Missing parentheses in call to 'print'. Did you
> > mean print(rev_id)? (__init__.py, line 71)
>
> This appears to be because the plugin is not compatible with Python 3.
Well I removed it after having seen this error message.
> > Anyway, on another user account, I did not have this plugin in
> > configuration directory and it still worked. Upto recently.
> >
> > Configuration is as follows:
> >
> > % cat ~/config/breezy/breezy.conf
> > [DEFAULT]
> > email = somemail
> > create_signatures = always
> > gpg_signing_key = SOMEKEYID
>
> Breezy supports commit signing out of the box - you shouldn't need a
> plugin for it.
Then why doesn't it ask me for entering the passphrase anymore and
commits unsigned? Does native support need different options? I searched
for a howto or documentation on how to configure signing commits but did
not find anything.
> I've never actually heard of a bzr plugin for signing either. What is
> its origin?
I have no idea anymore. I could dig it out from a backup in case it is
important for you to know.
Thanks,
--
Martin
More information about the bazaar
mailing list