I am simply trying to run sudo apt update
, but am encountering the seemingly classic error of:
Err:9 https://dl.winehq.org/wine-builds/ubuntu focal InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F
Err:10 https://dl.winehq.org/wine-builds/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F
This is all well and good. Several sources [1][2] Mention this as a quick and easy fix, specifically for that key:
wget -nc https://dl.winehq.org/wine-builds/winehq.key && sudo apt-key add winehq.key && sudo apt update
But when I run the command, but it still bounces back at the sudo apt update
step with the same error, even though the key seemed to have been correctly added. I even double checked this like so:
$ apt-key list
/etc/apt/trusted.gpg
--------------------
[...]
pub rsa3072 2018-12-10 [SC]
D43F 6401 4536 9C51 D786 DDEA 76F1 A20F F987 672F
uid [ unknown] WineHQ packages <wine-devel@winehq.org>
[...]
The key has clearly already been added, and the later half of the string associated with the key listing also corresponds (DDEA 76F1 A20F F987 672F
~= 76F1A20FF987672F
).
What am I missing? Why does sudo apt update
seemingly just ignore this newly added key?
How can I run sudo apt update
successfully in this situation?