Processing triggers for desktop-file-utils (0.24+linuxmint1). Processing triggers for menu (2.1.47ubuntu4). Processing triggers for man-db (2.9.1-1). Processing triggers for gnome-menus (3.36.0-1ubuntu1). Processing triggers for mime-support (3.64ubuntu1). 1335595 files and directories currently installed.) Get:1 stable/main amd64 google-chrome-stable amd64. ~ $ sudo apt-get install google-chrome-stableġ upgraded, 0 newly installed, 0 to remove and 43 not upgraded.Īfter this operation, 1’589 kB of additional disk space will be used. Of course in most situations, the google-chrome-stable package should be installed. Google-chrome-unstable - The web browser from Google Google-chrome-stable - The web browser from Google ![]() Google-chrome-beta - The web browser from Google There are three different versions available: ~ $ sudo apt-cache search chrome You can now install (or update if you already manually installed the deb package) Google Chrome. Now run apt-get update (or apt update) and you should see the InRelease and Packages download from the newly added Google repository: ~ $ sudo apt-get update Then add the repository: ~ $ echo "deb stable main" | sudo tee /etc/apt//chrome.list This allows you to install Chrome through APT – and therefore also update Chrome using APT.įirst download and install the APT key from Google, which is used to sign the packages: ~ $ wget -q -O - | sudo apt-key add. Using the APT repository from GoogleĪlthough rarely mentioned or published, Google actually has its own APT repository for Chrome. This is pretty annoying and the update should be automated. You need to download and manually install the current deb package – again. The following package was automatically installed and is no longer required:Ġ upgraded, 0 newly installed, 0 to remove and 106 not wget -qO - | sudo apt-key add echo "deb focal/mongodb-org/6.0 multiverse" | sudo tee /etc/apt//mongodb-org-6.0.listĭeb focal/mongodb-org/6.0 sudo apt-get updateA click on this update button gets you – once more – on the download website of Google Chrome. Gnupg is already the newest version (2.2.19-3ubuntu2.2). Still getting the public key not available error. I am running the steps to install MongoDB community edition. They have been ignored, or old ones used instead. W: Failed to fetch The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 GPG error: stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 The repository is not updated and the previous index files will be used. W: An error occurred during the signature verification. The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 What to do? I did the same install steps on a different system yesterday and it worked. ![]() ![]() I did run “sudo apt-key adv -keyserver”, but I am not sure which keyserver to use on that command. The “sudo apt-get update” step fails with error “signature could not be verified because public key is not available”. Running the steps to install mongo community on WSL Ubuntu 20.04.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |