Skip to content
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

[Bug]: GPG error signatures were invalid: EXPKEYSIG 23F3D4EA75716059 #7186

Closed
1 of 2 tasks
gufeisheng001 opened this issue Sep 8, 2024 · 10 comments
Closed
1 of 2 tasks
Labels
Bug Something isn't working as it should

Comments

@gufeisheng001
Copy link

What happened?

while compiling get an
Screenshot from 2024-09-08 13-15-48
GPG error: https://cli.github.com/packages stable InRelease: The following signatures were invalid: EXPKEYSIG 23F3D4EA75716059 GitHub CLI [email protected]

How to reproduce?

./compile.sh build BOARD=orangepi5-plus BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools editors email internet multimedia office programming remote_desktop' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=yes RELEASE=bookworm
log-build-84f3f0fb-a224-4da9-a1a6-c709fe82d013.log

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Ubuntu 24.04 Noble

Are you building on Windows WSL2?

  • Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@gufeisheng001 gufeisheng001 added the Bug Something isn't working as it should label Sep 8, 2024
Copy link

github-actions bot commented Sep 8, 2024

Jira ticket: AR-2483

@EvilOlaf
Copy link
Member

EvilOlaf commented Sep 8, 2024

We need to wait for GH to replace their expired key

cli/cli#9569

@EvilOlaf EvilOlaf closed this as completed Sep 8, 2024
@EvilOlaf EvilOlaf added Not framework bug Bug in 3rd party component and removed Bug Something isn't working as it should labels Sep 8, 2024
@williammartin
Copy link
Contributor

Hi from the GitHub CLI team and very sorry for the inconvenience here.

I see this is already closed out but there seems to be some confusion:

We need to wait for GH to replace their expired key cli/cli#9569

The key was already updated on Thursday 5th September. If you are still running into issues let me know and I'll try to provide support here.

@gufeisheng001
Copy link
Author

gufeisheng001 commented Sep 8, 2024

Hi from the GitHub CLI team and very sorry for the inconvenience here.

I see this is already closed out but there seems to be some confusion:

We need to wait for GH to replace their expired key cli/cli#9569

The key was already updated on Thursday 5th September. If you are still running into issues let me know and I'll try to provide support here.

Hi, i did those step, after that run ./compile.sh (even got an fresh install Ubuntu24.04.1LTS to test it out) but still got the same error.
what i did was :

  1. wget -qO- https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo tee /etc/apt/keyrings/githubcli-archive-keyring.gpg > /dev/null
  2. sudo chmod go+r /etc/apt/keyrings/githubcli-archive-keyring.gpg
  3. echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null
  4. sudo apt update
    gh is already the newest version (2.55.0).
    So did i miss some step, or other things?

@williammartin
Copy link
Contributor

When you run sudo apt update do you see the same error?

GPG error signatures were invalid: EXPKEYSIG 23F3D4EA75716059

If you're seeing gh is already the newest version (2.55.0). it seems like you have the correct keyring. If you're seeing an different error with the project, I'm not sure what that would be.

@gufeisheng001
Copy link
Author

Nope, apt update did not see errors, only saw it while compiling Armbian build
Screenshot from 2024-09-09 02-55-28

@williammartin
Copy link
Contributor

Ah, I'm not sure what that is doing but it seems likely that this file needs to be updated with https://cli.github.com/packages/githubcli-archive-keyring.gpg

I created a PR here #7192 with the change I think is required.

@EvilOlaf
Copy link
Member

EvilOlaf commented Sep 9, 2024

Apologies. Did a quick search across the framework but could not find it. So it was overall an issue on our end.

@EvilOlaf EvilOlaf added Bug Something isn't working as it should and removed Not framework bug Bug in 3rd party component labels Sep 9, 2024
@gufeisheng001
Copy link
Author

I got mistake the default gpg file location on debian/ubuntu, that still at /usr/share/keyrings/ NOT /etc/apt/keyrins/. Based on the cli/cli#9569 (comment)
no errors present any more after done those steps

  1. wget -qO- https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo tee /usr/share/keyrings/githubcli-archive-keyring.gpg > /dev/null
  2. sudo chmod go+r /usr/share/keyrings/githubcli-archive-keyring.gpg
  3. echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null

THANKS ALL!

@williammartin
Copy link
Contributor

Ah, sorry about that @gufeisheng001, after that comment we updated the original issue description with a script to handle that difference but it was probably too late for you. Glad you have it fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working as it should
Development

Successfully merging a pull request may close this issue.

3 participants