Description
Our Gitea is configured to sign the merge commits it creates from PRs.
We did have some GPG lock issues in Gitea for quite some time now and since I couldn't figure out to solve them, I changed the signatures to SSH keys.
PRs now merge every time without an internal error.
However, I still see GPG lock errors in the log and it seems to even assume that the SSH key is GPG.
Config:
[repository.signing]
SIGNING_KEY = /data/gitea/signatur/gitea-signatur.pub
SIGNING_FORMAT = ssh
SIGNING_NAME = Gitea
SIGNING_EMAIL = <redacted>
INITIAL_COMMIT = always
CRUD_ACTIONS = pubkey, twofa, parentsigned
WIKI = never
MERGES = approved
Gitea Version
1.26.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
2026/04/27 14:17:18 services/asymkey/commit.go:155:parseCommitWithGPGSignature() [E] Error getting default signing key: /data/gitea/signatur/gitea-signatur.pub unable to get default signing key: /data/gitea/signatur/gitea-signatur.pub, gpg: Note: database_open 134217901 waiting for lock (held by 17811) ...
Git Version
2.51
Operating System
SLES 15.7
How are you running Gitea?
systemd
Database
PostgreSQL
Description
Our Gitea is configured to sign the merge commits it creates from PRs.
We did have some GPG lock issues in Gitea for quite some time now and since I couldn't figure out to solve them, I changed the signatures to SSH keys.
PRs now merge every time without an internal error.
However, I still see GPG lock errors in the log and it seems to even assume that the SSH key is GPG.
Config:
Gitea Version
1.26.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
Git Version
2.51
Operating System
SLES 15.7
How are you running Gitea?
systemd
Database
PostgreSQL