[build/ci] gpg-sign step failure #3513

Closed
opened 2025-11-02 05:15:31 -06:00 by GiteaMirror · 10 comments
Owner

Originally created by @sapk on GitHub (Jun 25, 2019).

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.

Originally created by @sapk on GitHub (Jun 25, 2019). 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.
GiteaMirror added the topic/build label 2025-11-02 05:15:31 -06:00
Author
Owner

@sapk commented on GitHub (Jun 25, 2019):

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

@sapk commented on GitHub (Jun 25, 2019): Looking at [dl.gitea.io](https://dl.gitea.io/gitea/master/), I would say that it is failing since 22/06/2019
Author
Owner

@lunny commented on GitHub (Jun 26, 2019):

I will investigate it.

@lunny commented on GitHub (Jun 26, 2019): I will investigate it.
Author
Owner

@sapk commented on GitHub (Jun 26, 2019):

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

@sapk commented on GitHub (Jun 26, 2019): This should be fixed before 1.9 release. So maybe we should add it to the milestone.
Author
Owner

@lunny commented on GitHub (Jun 27, 2019):

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

@lunny commented on GitHub (Jun 27, 2019): This should be resolved if https://drone.gitea.io/go-gitea/gitea/10218 runs successfully.
Author
Owner

@sapk commented on GitHub (Jun 27, 2019):

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 ?

@sapk commented on GitHub (Jun 27, 2019): 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 ?
Author
Owner

@lunny commented on GitHub (Jun 27, 2019):

@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.

@lunny commented on GitHub (Jun 27, 2019): @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.
Author
Owner

@techknowlogick commented on GitHub (Jun 28, 2019):

@lunny did you update private key on drone?

@techknowlogick commented on GitHub (Jun 28, 2019): @lunny did you update private key on drone?
Author
Owner

@lunny commented on GitHub (Jun 29, 2019):

I have but it still failed.

@lunny commented on GitHub (Jun 29, 2019): I have but it still failed.
Author
Owner

@lunny commented on GitHub (Jun 29, 2019):

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.

@lunny commented on GitHub (Jun 29, 2019): 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.
Author
Owner

@sapk commented on GitHub (Jun 29, 2019):

Perfect. Thanks @lunny 🎉

@sapk commented on GitHub (Jun 29, 2019): Perfect. Thanks @lunny :tada:
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3513