cli: ubuntu public key unavailable

Describe the feature or problem you’d like to solve

I’m trying to install github cli on ubuntu following the instructions, but apt can’t seem to find and validate the public key used to sign the package.

Err:1 https://cli.github.com/packages stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C99B11DEB97541F0
[...]
W: GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C99B11DEB97541F0

It seems to be missing from keyserver.ubuntu.com: https://keyserver.ubuntu.com/pks/lookup?search=C99B11DEB97541F0&op=hget

Proposed solution

Add public key to keyserver.ubuntu.com or update public key used to sign package.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 19 (5 by maintainers)

Most upvoted comments

@mjohngreene I also ran into this a few minutes ago. The install website says they changed the key recently and to follow their instructions: https://github.com/cli/cli/blob/trunk/docs/install_linux.md#debian-ubuntu-linux-raspberry-pi-os-apt Once I reran this (on Ubuntu) the error went away.

+20

gadfort on Sep 7, 2022

I am currently running KDE Neon (20.04) and had to do the following (note: the first two lines were undoing the previous attempt to use the new accepted method in the docs):

<removed by admin>

I have not run the release upgrade to 22.04 yet, so this may just be for the last LTS, but I am now able to install/update gh without any errors.

cat /etc/os*
NAME="KDE neon"
VERSION="5.25"
ID=neon
ID_LIKE="ubuntu debian"
PRETTY_NAME="KDE neon User - 5.25"
VARIANT="User Edition"
VARIANT_ID=user
VERSION_ID="20.04"
HOME_URL="https://neon.kde.org/"
SUPPORT_URL="https://neon.kde.org/"
BUG_REPORT_URL="https://bugs.kde.org/"
LOGO=start-here-kde-neon
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

code-chimp on Sep 27, 2022

@DrPyser Thank you for confirming! We have modified our installation instructions to fix the permissions issue when setting up our package repository 👍

mislav on Jun 23, 2022