From 1d6850f3ac839326c5596db5a570bc7832bb394e Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Sat, 4 Feb 2012 06:26:12 -0800 Subject: repoman: support git commit --gpg-sign In order to sign commits with git, you will need Git >=1.7.9 and your key will have to be configured by `git config user.signingkey key_id`. Also, the repository will need to have "sign-commits = true" in metadata/layout.conf. This will fix bug #333687. --- bin/repoman | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'bin/repoman') diff --git a/bin/repoman b/bin/repoman index 6e9125480..bee6661db 100755 --- a/bin/repoman +++ b/bin/repoman @@ -582,6 +582,13 @@ repo_config = repoman_settings.repositories.get_repo_for_location(repodir) portdb.porttrees = list(repo_config.eclass_db.porttrees) portdir = portdb.porttrees[0] +if repo_config.sign_commit: + if vcs == 'git': + # NOTE: It's possible to use --gpg-sign=key_id to specify the key in + # the commit arguments. If key_id is unspecified, then it must be + # configured by `git config user.signingkey key_id`. + vcs_local_opts.append("--gpg-sign") + # In order to disable manifest signatures, repos may set # "sign-manifests = false" in metadata/layout.conf. This # can be used to prevent merge conflicts like those that -- cgit v1.2.3-1-g7c22