| Summary: | Repoman does not honors the PORTAGE_GPG_DIR when it signs the commit for git | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Agostino Sarubbo <ago> |
| Component: | Repoman | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | InVCS |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 462382 | ||
This should fix it: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=e9ba030a67ca69af791af8370837dfddf2f2f7b1 This is fixed in 2.1.11.56 and 2.2.0_alpha167. |
I have not the gpg key in the default path (.gnupg) so when I try to sign the commit into my overlay, repoman fails to sign the commit (not the manifest). The error is: gpg: skipped "7194459F": No secret key gpg: signing failed: No secret key error: gpg failed to sign the data fatal: failed to write commit object !!! Exiting on git (shell) error code: 128 Now If I try to sign the commit manually with gpg commit -S I get: gpg: skipped "7194459F": No secret key gpg: signing failed: No secret key error: gpg failed to sign the data fatal: failed to write commit object but with this alias I have no problem: [alias] commitsign = !GNUPGHOME="/media/dati/gnupg/" git commit -S $* So I guess portage does not honour the PORTAGE_GPG_DIR when it signs the commit.