Question
Error during upgrade Ubuntu 18.04 to 22.04
- Posted on February 10, 2023
- Ubuntu 18.04
Asked by joel9b158e40551b15093f213f
Hi - Following upgrade instructions at https://www.digitalocean.com/community/tutorials/how-to-upgrade-to-ubuntu-20-04-focal-fossa
When doing
sudo apt update
I get following GPGerror:
Hit:1 http://ppa.launchpad.net/ondrej/apache2/ubuntu bionic InRelease
Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:3 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
Hit:4 https://esm.ubuntu.com/ubuntu trusty-infra-security InRelease
Hit:5 https://esm.ubuntu.com/ubuntu trusty-infra-updates InRelease
Hit:6 https://repos.insights.digitalocean.com/apt/do-agent main InRelease
Hit:7 http://mirrors.digitalocean.com/ubuntu bionic InRelease
Hit:8 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease
Hit:9 http://mirrors.digitalocean.com/ubuntu bionic-backports InRelease
Ign:10 http://dl.google.com/linux/mod-pagespeed/deb stable InRelease
Hit:11 http://dl.google.com/linux/mod-pagespeed/deb stable Release
Err:12 http://dl.google.com/linux/mod-pagespeed/deb stable Release.gpg
The following signatures were invalid: EXPKEYSIG 78BD65473CB3BD13 Google Inc. (Linu x Packages Signing Authority) <linux-packages-keymaster@google.com>
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/mod -pagespeed/deb stable Release: The following signatures were invalid: EXPKEYSIG 78BD6 5473CB3BD13 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@ google.com>
W: Failed to fetch http://dl.google.com/linux/mod-pagespeed/deb/dists/stable/Release. gpg The following signatures were invalid: EXPKEYSIG 78BD65473CB3BD13 Google Inc. (L inux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Some index files failed to download. They have been ignored, or old ones used inst ead.
Any idea how to fix this before proceeding ??
Thanks
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Get started for free
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
Hi there,
What you could try doing is to remove the repository that is causing the problem and then once you are ready, you could re-add the correct repository again for the new Ubuntu version.
You could do that in two ways:
Open the file with your favourite text editor and comment out the mod-pagespeed lines by adding a
#in the beginning of the lineAlternatively, you can use the
add-apt-repository, the command should look something like this:Then update the package index:
sudo apt update.And finally, rerun the upgrade. After the upgrade is complete, you could re-add the repo as normal.
Make sure to always back up your Droplet when doing such major upgrades.
Let me know how it goes!
Best,
Bobby