Difference between revisions of "Talk:Chrome rather than Chromium"
From Free Knowledge Base- The DUCK Project: information for everyone
(Created page with "== F'ing GPG Key Bullsh*t == W: GPG error: http://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is no...") |
(→F'ing GPG Key Bullsh*t) |
||
| Line 5: | Line 5: | ||
N: Updating from such a repository can't be done securely, and is therefore disabled by default. | N: Updating from such a repository can't be done securely, and is therefore disabled by default. | ||
N: See apt-secure(8) manpage for repository creation and user configuration details. | N: See apt-secure(8) manpage for repository creation and user configuration details. | ||
| + | |||
| + | Starting with Ubuntu 20.04 LTS and Debian 11, there has been a change in how APT handles public keys. The apt-key command is deprecated | ||
| + | |||
| + | Each repository’s keys are now recommended to be stored individually, either in the /etc/apt/trusted.gpg.d/ directory or specified in the repository’s source list entry | ||
Revision as of 20:47, 26 October 2024
F'ing GPG Key Bullsh*t
W: GPG error: http://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2 E: The repository 'http://dl.google.com/linux/chrome/deb stable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
Starting with Ubuntu 20.04 LTS and Debian 11, there has been a change in how APT handles public keys. The apt-key command is deprecated
Each repository’s keys are now recommended to be stored individually, either in the /etc/apt/trusted.gpg.d/ directory or specified in the repository’s source list entry
