1 |
Today an interesting thing happened to my repoman, as I was committing a |
2 |
change: |
3 |
|
4 |
>>> Creating Manifest for /home/ph/gentoo-x86/dev-lang/v8 |
5 |
gpg: no default secret key: Unusable secret key |
6 |
gpg: /home/ph/gentoo-x86/dev-lang/v8/Manifest: clearsign failed: |
7 |
Unusable secret key |
8 |
!!! !!! gpg exited with '2' status |
9 |
!!! Disabled FEATURES='sign' |
10 |
/var/cvsroot/gentoo-x86/dev-lang/v8/Manifest,v <-- Manifest |
11 |
new revision: 1.321; previous revision: 1.320 |
12 |
|
13 |
Indeed my private key on that machine was expired: |
14 |
|
15 |
pub 1024D/30427902 2009-08-05 [expired: 2013-06-10] |
16 |
|
17 |
But after refreshing it (I have extended the expiration date) it is fine: |
18 |
|
19 |
pub 1024D/30427902 2009-08-05 [expires: 2014-02-10] |
20 |
|
21 |
I was surprised by repoman just dropping FEATURES="sign" . I'm aware |
22 |
that at that time it has to commit an updated Manifest to prevent |
23 |
breakages, so if gpg fails it proceeds, but is there something it could |
24 |
do to check gpg sanity before committing anything? |
25 |
|
26 |
Paweł |