| Summary: | repoman goes into endless loop on gpg key problems | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Daniel Black (RETIRED) <dragonheart> |
| Component: | Repoman | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | betelgeuse, vapier |
| Priority: | High | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 115839 | ||
| Attachments: | repoman.diff | ||
|
Description
Daniel Black (RETIRED)
2004-07-17 21:58:47 UTC
No traceback sorry just this when a repoman commit is done.
<<< files/pdnsd.rc6
<<< files/digest-pdnsd-1.1.10
>>> Computed message digests.
gpg: no default secret key: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
!!! YOU MUST sign the Manifest.
!!! You can also disable this for the time being by removing FEATURES='sign'gpg: no default secret key: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
!!! YOU MUST sign the Manifest.
!!! You can also disable this for the time being by removing FEATURES='sign'gpg: no default secret key: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
!!! YOU MUST sign the Manifest.
!!! You can also disable this for the time being by removing FEATURES='sign'gpg: no default secret key: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
!!! YOU MUST sign the Manifest.
!!! You can also disable this for the time being by removing FEATURES='sign'gpg: no default secret key: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
!!! YOU MUST sign the Manifest.
!!! You can also disable this for the time being by removing FEATURES='sign'gpg: no default secret key: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
!!! YOU MUST sign the Manifest.
!!! You can also disable this for the time being by removing FEATURES='sign'gpg: no default secret key: secret key not available
Did you set PORTAGE_GPG_DIR ? no. So the problem is not the passphares on the key, gpg simply can't find your key (remember that portage probably runs under a different user with a different $HOME). PORTAGE_GPG_DIR should be set to the dir where your keyring for signing is. This should get moved into portage_gpg.py and handled with checks and exceptions. bug 60384 describes an issue with gnupg-1.9 not working/existing. Can anyone duplicate this with a recent version of repoman/portage? ( preferably 2.0.53 or greater ). Yep. Checking in Manifest; /var/cvsroot/gentoo-x86/net-p2p/azureus-bin/Manifest,v <-- Manifest new revision: 1.75; previous revision: 1.74 done gpg: no default secret key: unusable secret key gpg: .//Manifest: clearsign failed: unusable secret key !!! gpg exited with '512' status !!! YOU MUST sign the Manifest. !!! You can also disable this for the time being by removing FEATURES='sign'gpg: no default secret key: unusable secret key gpg: .//Manifest: clearsign failed: unusable secret key !!! gpg exited with '512' status !!! YOU MUST sign the Manifest. !!! You can also disable this for the time being by removing FEATURES='sign'gpg: no default secret key: unusable secret key gpg: .//Manifest: clearsign failed: unusable secret key Repoman also goes into an endless loop with an expired key. Created attachment 79643 [details, diff]
repoman.diff
Does this help at all? Atleat with bailing?
*** Bug 72873 has been marked as a duplicate of this bug. *** that patch was bogus. dont try it This is fixed in svn r3173. Released in 2.1_pre9-r1. |
