I googled for a while but couldn't find the right solution for me.
They have been ignored, or old ones used instead. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: noneĮ: Some index files failed to download.
N: See apt-secure(8) manpage for repository creation and user configuration details.Į: Failed to fetch server certificate verification failed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. W: The repository ' apt/stable/ Release' does not have a Release file. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
The key is readable, although it does not mention F57D4F59BD3DF454.I was following the official instruction to install Sublime text 3 but get errors shown as below when I do sudo apt-get update: Ign:10 apt/stable/ InRelease When I inspect the dearmored key, sudo gpg -show-keys /usr/local/share/keyrings/sublime-keyring.gpg, I get the following, which seems plausibly correct: pub rsa4096 Or maybe the key was somehow mangled in the dearmoring process and no longer has the contents expected. This could mean that gpg can not read the contents of the key. I read this to mean that apt is correctly passing on the location of the key I have downloaded. Preparing to exec: /usr/bin/apt-key -quiet -readonly -keyring /usr/local/share/keyrings/sublime-keyring.gpg verify -status-fd 3 /tmp/50y /tmp/ When I run with debug for gpg, sudo apt -o Debug::Acquire::gpgv=True update, I get a few more details: Get:1 apt/stable/ InRelease Ġ% inside VerifyGetSigners N: See apt-secure(8) manpage for repository creation and user configuration details. N: Updating from such a repository can't be done securely, and is therefore disabled by default.
W: GPG error: apt/stable/ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F57D4F59BD3DF454Į: The repository ' apt/stable/ InRelease' is not signed. The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F57D4F59BD3DF454
Then I run sudo apt update which creates the following output regarding sublime text repo: Get:1 apt/stable/ InRelease Set pinning rules to restrict repo usage: printf "%s\n" "Package: *" "Pin: origin " "Pin-Priority: 1" "" "Package: sublime-text" "Pin: origin " "Pin-Priority: 500" | sudo tee /etc/apt/preferences.d/sublime-text.pref Sudo chmod -v 0640 /usr/local/share/keyrings/sublime-keyring.gpgĬreate source list: printf "deb apt/stable/" | sudo tee /etc/apt//sublime-text.list Sudo chown -v root:root /usr/local/share/keyrings/sublime-keyring.gpg Sudo mv -v ~/Downloads/sublime-keyring.gpg /usr/local/share/keyrings/sublime-keyring.gpg Sudo mkdir -vp /usr/local/share/keyrings/ However, when running apt update I am getting the following error regarding the encryption key: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F57D4F59BD3DF454ĭownload key, convert key from ascii to binary, and move key to shared location: curl | gpg -dearmor > ~/Downloads/sublime-keyring.gpg I am intentionally applying the method for connecting to third party repositories described on the Debian and Stackexchange pages, using Sublime as an example of a third party repo. I am using the instructions linked below to setup apt to install sublime-text.