Enforcing gpg check does not work
Balint Aradi
balint.aradi at bccms.uni-bremen.de
Wed Dec 5 09:11:06 GMT 2007
Dear all,
I have a repository (created with bzr 0.92) containing checkins
without gpg-encryption. I'd expect, that checking out the repository (or
branching from the repository) somewhere, where the
${HOME}/.bazaar/bazaar.conf contains the lines
[DEFAULT]
check_signatures = require
should fail, shouldn't it? However, it does the job without any error
messages. Is it the expected behaviour or am I doing something wrong?
Also, is there a way to "gently force" developers to sign their
revisions at checkin? Could I set "create_signatures = always" in some
config file, which is automatically distributed with the branch itself?
Setting .bzr/branch/branch.conf in the original branch to
check_signatures = require
create_signatures = always
does not seem to do the job.
Thanks in advance
Bálint
--
========================================================================
Bálint ARADI, Ph.D.
Bremen Center for Computational Materials Science, University of Bremen
Room 3.10, Building TAB (A), Am Fallturm 1, 28359 Bremen, Germany
Tel.: +49 421 218 7421, Fax: +49 421 218 4764
Web: http://www.bccms.uni-bremen.de/de/mitarbeiter/b_aradi/
========================================================================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20071205/9ad21a61/attachment-0001.pgp
More information about the bazaar
mailing list