manjaro-sway: 🐛 GPG Key Expired?
branch
stable
Architecture
x86_64
Description
Cannot use pacman, seems @boredland key expired?
❯ gpg --homedir /etc/pacman.d/gnupg --list-keys | grep strass -A 3 -B 3
gpg: WARNING: unsafe ownership on homedir '/etc/pacman.d/gnupg'
gpg: Note: trustdb not writable
pub rsa3072 2021-07-07 [SC] [expired: 2023-07-07]
A44C644D792767CED7941AFEABB2075D5F310CF8
uid [ expired] Jonas Strassel <info@jonas-strassel.de>
uid [ expired] Jonas Strassel <jonas.strassel@ioki.com>
uid [ expired] Jonas Strassel <jo.strassel@gmail.com>
uid [ expired] Jonas Strassel <jonas.strassel@manjaro.org>
pub rsa4096 2014-09-28 [SC]
77DC01C9971AC3C39A0626F72C089F09AC97B894
Reproduction steps
$ sudo rm -r /etc/pacman.d/gnupg
$ sudo pacman-key --init
$ sudo pacman-key --populate archlinux manajro
$ sudo pacman -S archlinux-keyring manjaro-keyring
...
❯ sudo pacman -S manjaro-keyring
error: manjaro-sway: signature from "Jonas Strassel <info@jonas-strassel.de>" is unknown trust
error: database 'manjaro-sway' is not valid (invalid or corrupted database (PGP signature))
### Screenshots
_No response_
### Logs
_No response_
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 2
- Comments: 15 (8 by maintainers)
temp fix :
sudo pacman-key --recv-keys A44C644D792767CED7941AFEABB2075D5F310CF8sudo pacman-key --lsign-key A44C644D792767CED7941AFEABB2075D5F310CF8In Manjaro keyring, my signature has been switched out a long time ago (beginning of June), the package database was correctly signed yesterday. Not sure, but maybe you need to update your local signature store, let me check the command for that.
I didn’t see the pinned issue, since I came to this issue by a link somewhere on the internet. But I tried and it worked, thanks!
Ya, the new issue is caused by fixing the underlying issue of another one 😞 there was no non-breaking way to do that, sadly.
Just to provide some context here as i’ve come across this on both of my machines.
I noticed that the manjaro-sway repo was not in my package databases
Then i added the repo following #447 , and encountered the error :