[build/ci] gpg-sign step failure

[sapk]

The ggp-sign step is failing on drone: https://drone.gitea.io/go-gitea/gitea/10134/1/26 . That mean that no binary is released. The signing secret seems to be missing.

[sapk]

Looking at dl.gitea.io, I would say that it is failing since 22/06/2019

[lunny]

I will investigate it.

[sapk]

This should be fixed before 1.9 release. So maybe we should add it to the milestone.

[lunny]

This should be resolved if https://drone.gitea.io/go-gitea/gitea/10218 runs successfully.

[sapk]

Seems to have failed.
When it works if you re-sign the key can you re-upload with the new sign (new expire date) to pgp keyservers ?

[lunny]

@sapk I have updated the public key, see https://pgp.mit.edu/pks/lookup?op=vindex&fingerprint=on&search=0x2D9AE806EC1592E2. I think CI failed because it may cached the public key.

[techknowlogick]

@lunny did you update private key on drone?

[lunny]

I have but it still failed.

[lunny]

I think I made a mistake when I update secret key. If https://drone.gitea.io/go-gitea/gitea/10294 successfully, this should be resolved.

[sapk]

Perfect. Thanks @lunny 🎉