Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
I'm pretty new to Debian and even Linux as a whole. After evaluating all the different distros for my switch from the world of windows I chose Debian because I liked it's simplicity, reliability, security, and most of all the philosophy behind it. I started on Jessie just a few months ago and had no problems installing it and setting it up to my liking. I am however having some problems with a fresh install of stretch. The problem is a GPG error of some sort when updating from the repositories. I have tried editing permissions in the trusted.gpg file to be able to be read by the user and group accounts (only root can after fresh install), and I also tried installing the public gpg keys listed in the error to no avail, and have also tried installing the complete debian and debian-archive keyrings which didn't solve the problem either. I have also tried installing dirmngr which was not installed either, but that didn't fix the issue either. This is the error that I get after apt-get update:
Ign:1 http://debian.mirror.constant.com/debian stretch InRelease
Get:2 http://debian.mirror.constant.com/debian stretch-updates InRelease [88.5 kB]
Hit:3 http://debian.mirror.constant.com/debian stretch Release
Err:2 http://debian.mirror.constant.com/debian stretch-updates InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
Err:4 http://debian.mirror.constant.com/debian stretch Release.gpg
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
Get:5 http://security.debian.org stretch/updates InRelease [62.9 kB]
Ign:5 http://security.debian.org stretch/updates InRelease
Fetched 62.9 kB in 0s (74.1 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://debian.mirror.constant.com/debian stretch-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://debian.mirror.constant.com/debian stretch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
W: GPG error: http://security.debian.org stretch/updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
W: The repository 'http://security.debian.org stretch/updates InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Failed to fetch http://debian.mirror.constant.com/debian/dists/stretch-updates/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
W: Failed to fetch http://debian.mirror.constant.com/debian/dists/stretch/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
W: Some index files failed to download. They have been ignored, or old ones used instead.
Any help with this would be greatly appreciated! Hopefully someone out there knows how to fix this.
Last edited by stretch99 on 2017-07-19 23:50, edited 1 time in total.
# deb http://ftp.us.debian.org/debian/ stretch main
deb http://debian.mirror.constant.com/debian/ stretch main contrib non-free
deb-src http://debian.mirror.constant.com/debian/ stretch main contrib non-free #Added by software-properties
# stretch-updates, previously known as 'volatile'
deb http://security.debian.org/ stretch/updates main contrib non-free
deb http://debian.mirror.constant.com/debian/ stretch-updates main non-free contrib
base.list base.list.save
sudo apt-key update
Warning: 'apt-key update' is deprecated and should not be used anymore !
Note: In your distribution this command is a no-op and can therefore be removed safely.
W: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported filetype.
It seems now recommended to use dirmngr , but not sure of it.
Still an issue? Downloaded and installed Stretch on RPI for OpenAG (NOT Recommended). While installing the developer build from source, ran into this problem installing dependencies for CouchDB, requiring Debian repo.
Not to sure why this happened. Perhaps because Ubuntu is hosting these keys and not Debian?!!!! @L_V problems deprecating some of the aptly security libraries? Developers moving to Ubuntu and taking there keys with them? It would be interesting to know.
My fix: If its not already installed, install dirmngr. Then copy one of the GPG keys from the output of the failed update. Then fetch it from Ubuntuś public key server of all things . The public keys appear to be consistent across the board for this problem. This was my output:
W: GPG error: http://ftp.de.debian.org/debian stretch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY EF0F382A1A7B6500
W: The repository 'http://ftp.de.debian.org/debian stretch Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.