Can't get public key

[jpelletier]

Select Topic Area

Question

Body

I'm trying to install node-red on a Banana Pi M2 Zero. For this, there's a script which does all the install. It works fine on a Raspberry Pi.
However, there are 2 sites from which the public key is unavailable. One of these is https://cli.github.com.

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 23F3D4EA75716059
E: The repository 'http://cli.github.com/packages stable InRelease' is not signed.

We can get a public key with this command, but this one is specifically for Ubuntu.
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5

What would be the correct URL for cli.github.com ?

[airtower-luna]

The documentation mentions both a download URL, and that they recently had to replace the key: https://github.com/cli/cli/blob/trunk/docs/install_linux.md

[jpelletier]

I tried to get the key manually, but after apt update, I get:
E: Conflicting values set for option Signed-By regarding source https://cli.github.com/packages/ stable: /usr/share/keyrings/githubcli-archive-keyring.gpg != /usr/share/keyrings/githubcli.gpg
E: The list of sources could not be read.

[airtower-luna]

That sounds like a mistake in your package sources configuration, maybe the same repository listed twice, with the different keys that the error message complains about? Impossible to say for sure without seeing the config, though. 🤔

[jpelletier]

Here is the content of /etc/apt/sources.list

deb http://ports.ubuntu.com/ jammy main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ jammy main restricted universe multiverse

deb http://ports.ubuntu.com/ jammy-security main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ jammy-security main restricted universe multiverse

deb http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse

deb http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse
# deb-src http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ jammy main

Here is the command I use to get the public key:

sudo apt-key adv --keyserver cli.github.com/packages/githubcli.gpg --recv-keys 23F3D4EA75716059
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.1u7aPD6HI6/gpg.1.sh --keyserver cli.github.com/packages/githubcli.gpg --recv-keys 23F3D4EA75716059
gpg: keyserver receive failed: Connection timed out

[airtower-luna]

There's no mention of the GitHub CLI repository in your sources.list, I assume there are other file(s) in /etc/apt/sources.list.d/. You can list them all and their names with a command like this:

for f in /etc/apt/sources.list.d/*; do echo "== ${f} =="; cat "${f}"; done

As for getting the public key, do what the deprecation warning says and stop using apt-key. Instead simply download the key file, and use the signed-by setting of the repository entry to point at it. Though as it's manually managed you should put it into /etc/apt/keyrings/, not /usr/share/keyrings/ like the GitHub CLI documentation says (see the Debian Wiki entry on the matter).

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬