Invalid key on update

[MousePotato]

Something has gone wrong with the mx23 keyring. I tried to check for updates today and got:

Code: Select all

Err https://cli.github.com/packages stable InRelease
  The following signatures were invalid: EXPKEYSIG 23F3D4EA75716059 GitHub CLI <opensource+cli@github.com>

Is there an update for the keyring that I missed?

[dolphin_oracle]

that's not our repo, so not our key.

you can try the Fix Apt GPG Tool, which will check public key servers for an updated key, but it will only help if there is actually an updated key to get.

[siamhie]

This was posted yesterday. Can't install / update gh due to expired GPG key? #9569

[fehlix]

Something has gone wrong with the mx23 keyring. I tried to check for updates today and got:

Code: Select all

Err https://cli.github.com/packages stable InRelease
  The following signatures were invalid: EXPKEYSIG 23F3D4EA75716059 GitHub CLI <opensource+cli@github.com>

Is there an update for the keyring that I missed?

If you can't solve the problem with one of the two “attempted solutions” already mentioned.
Suggest you post a full QSI “Quick System Info”, and we will suggest a solution based on this.
You'll find the QSI tool within the favorites of the menu or within MX Tools.

[MousePotato]

Hmm, I hadn't considered that something i added might have also added a repository. I'll now have to try to figure out if this is from something I am still using or if it's something I abandoned and removed. In which case, I'll be wondering how to remove the repository. :)

[dolphin_oracle]

Hmm, I hadn't considered that something i added might have also added a repository. I'll now have to try to figure out if this is from something I am still using or if it's something I abandoned and removed. In which case, I'll be wondering how to remove the repository. :)

if you had provided your quick-system-info, we could tell you what file to edit.

but use mx-repo-manager, last tab. there should be check boxes to enable/disable any configured repo.

[MousePotato]

OK, I used the suggested method in the Github post. It worked in that the error is gone. But the mystery only deepens. This is "not your key" but the package it freed up to be updated is named:

Code: Select all

mx-datetime/mx 24.4mx23 amd64 [upgradable from: 23.7]

Which sure looks like a MX Linux package. Is this possibly because of a dependency?

I thought maybe the github key was due to some third-party app I had tried to install in the past. I've tried several things, such as Celestia. but I don't recall what repos they use.

[dolphin_oracle]

Nah. The operation just wouldn’t go through with any error present.