-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NO_PUBKEY 5478FEE00E35DFD3 #13
Comments
hmm, did I let my gpg key expire...
I need a new key, then everyone need to update the key. |
MEMO for me
You need to repeat this step, since the public key has been updated, now longer valid than 2 years
|
Thanks. Thus is routine for many apps. Most recent, spotify. Thankyou for
this app! My daughter is loving it.
El dom., 16 de febrero de 2025 5:48 a. m., ChristopherHX <
***@***.***> escribió:
… MEMO
# To get the fingerprint
gpg --list-secret-keys --keyid-format LONG
gpg --quick-set-expire <fingerprint> 8y
gpg --armor --export-secret-keys <fingerprint>
You need to repeat this step, since the public key has been updated, now
longer valid than 2 years
curl -sS https://minecraft-linux.github.io/pkg/deb/pubkey.gpg | sudo tee -a /etc/apt/trusted.gpg.d/minecraft-linux-pkg.asc
—
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXPIG5CQLETME357BFV7KL2QBUIZAVCNFSM6AAAAABXG6O426VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRRGM3TGMBYGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: ChristopherHX]*ChristopherHX* left a comment
(minecraft-linux/pkg#13)
<#13 (comment)>
MEMO
# To get the fingerprint
gpg --list-secret-keys --keyid-format LONG
gpg --quick-set-expire <fingerprint> 8y
gpg --armor --export-secret-keys <fingerprint>
You need to repeat this step, since the public key has been updated, now
longer valid than 2 years
curl -sS https://minecraft-linux.github.io/pkg/deb/pubkey.gpg | sudo tee -a /etc/apt/trusted.gpg.d/minecraft-linux-pkg.asc
—
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXPIG5CQLETME357BFV7KL2QBUIZAVCNFSM6AAAAABXG6O426VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRRGM3TGMBYGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks for the key update. Are there instructions for Fedora for the similar step? |
For now, just used a workaround like: But definitely, there should be a proper way to update the local pubkey. |
The .repo files I shown in the readme point to that url for rpm, so could be caching
I don't think to have a fedora system that has fetched the old key at the moment |
Unfortunately, it was not working, tried it the first thing. But ok, for Fedora (on daughter's laptop) it's done using the workaround. |
You may have an old copy of my public key under a different file name in /etc/apt/trusted.gpg.d At least that was it for me. If you remove all keys of my ppa from that folder, the error should just print key not found instead of expired |
Thanks, it worked to delete first the same file |
@dilnix Could you please try this command on fedora?
This seems to delete the previously imported key (I have published) of my repository and asks again on install like first time. |
On Fedora 41 I have done it like this:
Your output should be something like the following:
Look for the old key and remove with:
Then you can retry
|
Thanks both, it worked. |
Got this error while trying to update.
The install procedure after deleting the ppa and keys don't fix it.
The text was updated successfully, but these errors were encountered: