Steve Alexander wrote:
> Public bug reported:
>
> The bzr release I'm testing gives messages ocassionally like "Please use
> create_signatures, not check_signatures to set signing policy."
>
> But, it doesn't tell me where or how I need to use these things.
You only get that message if you have already configured
"check_signatures", so I assumed you know where you set it.
> If this is in some config file, perhaps bzr could tell me what config
> file it is.
Signature checking may be configured in any of ~/bazaar/global.conf,
~/bazaar/locations.conf, or .bzr/branch.conf. The API that determines
the config value doesn't (currently) include a human-readable
description of where the value that determined the policy came from.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steve Alexander wrote:
> Public bug reported:
>
> The bzr release I'm testing gives messages ocassionally like "Please use
> create_signatures, not check_signatures to set signing policy."
>
> But, it doesn't tell me where or how I need to use these things.
You only get that message if you have already configured
"check_signatures", so I assumed you know where you set it.
> If this is in some config file, perhaps bzr could tell me what config
> file it is.
Signature checking may be configured in any of ~/bazaar/ global. conf, locations. conf, or .bzr/branch.conf. The API that determines
~/bazaar/
the config value doesn't (currently) include a human-readable
description of where the value that determined the policy came from.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://
iD8DBQFFDrW20F+ nu1YWqI0RArXnAJ 91Ws0/NqvyuLIyt pq4MMOV1yIRngCf TjWL CxT8ecPA=
EWevMAuQlWkQ9HK
=YgKM
-----END PGP SIGNATURE-----