Closed fsworld009 closed 5 years ago
Did you refresh the key, as instructed in the README? I'll check with my Arch box later, but the signatures are considered valid by my Fedora server. The last update of the packages was on January 12th, whereas the key was recently extended to 2020-01-01.
-- Chris Warrick https://chriswarrick.com/
On Sat, 19 Jan 2019, 14:53 WorldFS <notifications@github.com wrote:
Hi,
looks like your key has expired, according to your README it was valid until 12th this month.
For now I have to disable pkgbuilder upgrade on pacman due to invalid key.
Would be nice if you get a chance to renew it, thanks!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Kwpolska/pkgbuilder/issues/61, or mute the thread https://github.com/notifications/unsubscribe-auth/AAT-m-dTxVQ2is6gBe0W54sZrldIc8a6ks5vEyNegaJpZM4aJJgb .
It works now.
Previously I was getting this error:
$ sudo pacman-key -r 5EAAEA16
gpg: keyserver receive failed: No data
==> ERROR: Remote key not fetched correctly from keyserver.
And doing pacman -Syu
will give me
error: pkgbuilder: signature from "Chris Warrick <kwpolska@gmail.com>" is unknown trust
Hence I checked this repo and thought the key was expired. So I disabled pkgbuilder in pacman.conf
and do a pacman upgrade, I think keyring has been updated because of this, so now retrieving keys works again.
To summarize the steps I took to resolve this issue (for future reference):
pkgbuilder
to IgnorePkg
(comma-separated list)# [pkgbuilder]
# Server = https://pkgbuilder-repo.chriswarrick.com/
pacman -Syu
pacman.conf
pacman -Syu
should work and can upgrade pkgbuilderThanks for your help :)
Hi,
looks like your key has expired, according to your README it was valid until 12th this month.
For now I have to disable pkgbuilder upgrade on pacman due to invalid key.
Would be nice if you get a chance to renew it, thanks!