![]() ![]() ![]() When the error first popped up in the terminal it didn't tell me "which" repository was having a problem, just that one of them was missing the public key, so I narrowed it down by manually disabling the repositories (removing the 3rd party files from /etc/apt/) until the error went away. I just wanted to share this little tidbit of info in case anybody else runs into this problem. Try new features with Google Chrome Beta Google Chrome Google Settings, or learn more. If you run into this issue, Google has a page set up specifically for showing you how to manually add the public signing key for your particular package manager. So as soon as they deem the version stable and put it on the. It added the repository, but without the key my system kept warning me there was no public key available for the repository. yochananmarqos This package follows the stable release channel of the Google Debian releases. ![]() In this case however, for whatever reason, the deb I downloaded today (28 April 2016, Chrome version .86 (64-bit)) didn't add the signing key. so that the end user doesn't have to do anything other than install regular system updates when they're available and Chrome will get pulled in with everything else. Normally the deb file from google(dot)com/chrome automagically sets up the repository, adds the public signing key, etc. I started disabling 3rd party repositories and found out the problem was coming from Google Chrome's repository. I kept getting an error when manually checking for updates in the terminal with "apt-get update" telling me there was no public key for something. So I had a strange issue today while installing Google Chrome on a Debian machine.
0 Comments
Leave a Reply. |