![\"\"](\"http:\/\/www.chan.ink\/wp-content\/uploads\/2024\/06\/WS9N8PQISBR8HYHNIRLB.png\")
<\/figure>\n\n\n\n\u5c31\u662f\u53ef\u7b11\u6211\u7684\u82f1\u8bed\u6c34\u5e73\u8ddf\u73b0\u5728\u7684\u7f16\u7a0b\u6c34\u5e73\u4e00\u6837\u8e69\u811a\u54c8\u54c8\u54c8\u3002<\/p>\n\n\n\n
\u8fd9\u662f\u5ba2\u670d\u7ed9\u51fa\u7684\u89e3\u51b3\u65b9\u6848\uff1ahttps:\/\/green.cloud\/docs\/how-to-fix-update-failed-on-linux\/<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Estimated reading: 3 minutes 148 views<\/p>\n\n\n\n In this article, you will learn how to fix some common update errors that occur frequently when you try to update on the Linux operating system. Below are 3 error cases encountered when we run updates on our Almalinux, Centos, and Debian 12 versions.<\/p>\n\n\n\n If you, for one reason or the other, are still actively using CentOS 8<\/strong>, you might probably have encountered the following error when trying to update your system or simply install a package.<\/p>\n\n\n\n For example, in the screenshot that follows, I was trying run update and ran into it.<\/p>\n\n\n\n You may well be aware that CentOS Linux 8<\/strong> died a premature death, it reached the End Of Life (EOL) on December 31st, 2021, thus it no longer receives development resources from the official CentOS project.<\/p>\n\n\n\n This means that after Dec 31st, 2021, to update your CentOS installation, you are required to change the mirrors to CentOS Vault Mirror, where they will be archived permanently.<\/p>\n\n\n\n To fix the above error, open your terminal or login via SSH, and run the following commands to change the repo URL to point to vault.centos.org<\/strong>, from the official CentOS repos.<\/p>\n\n\n\n Here we use the sed<\/strong> command to edit the required directives or parameters in the repo configuration files:<\/p>\n\n\n\n Alternatively, you can also point to the Cloudflare-based vault repository, by running the following commands:<\/p>\n\n\n\n Now you should be able to update CentOS<\/strong> or install packages without any error<\/p>\n\n\n\n When installing packages on AlmaLinux, if you run into a \u201cGPG check failed\u201d problem, it means that the available GPG keys were unable to verify the signature of the package. A corrupt repository, an out-of-date or missing GPG key, or network problems could all be the cause of this.<\/p>\n\n\n\n The GPG key for the xfsdump package was not installed, resulting in a GPG check failure during the package installation, which was resolved by importing the necessary key from the AlmaLinux repository.<\/p>\n\n\n\n cloudlinux-release-8.9-2.el8 package contains an updated AlmaLinux key, but won\u2019t help with current systems<\/p>\n\n\n\n Update the GPG keys that we use to verify packages. Importing the most recent GPG keys from the repository will enable us to perform this. So, we can run the following command:<\/p>\n\n\n\n Now you should be able to update Almalinux or install packages without any error:<\/p>\n\n\n\n I keep on getting this error when I try to install or upgrade on Debian 12 and almost everything.<\/p>\n\n\n\n You can fix the error by running the following command<\/p>\n\n\n\n You can see detailed error correction here: How to fix \u201cthe repository cdrom does not have a release file\u201d error on Debian 12<\/a><\/p>\n\n\n\n And there you have it! A comprehensive guide to fixing the update errors in Linux versions. Trust me, I\u2019ve faced this error more times than I can count and these steps have helped me every single time.<\/p>\n\n\n\n Good Luck!<\/p>\n","protected":false},"excerpt":{"rendered":" \u6700\u8fd1\u770b\u5b8c\u4e86head first python\uff0c\u867d\u7136\u8ddf\u7740\u6559\u7a0b\uff0c\u5728\u4e66\u4e2d\u6307\u5b9a\u7684\u7f51\u7ad9\u505a\u4e86\u4e00\u4e2a\u7ebf\u4e0a\u53ef\u8bbf\u95ee\u7684\u94fe\u63a5\u3002\u4f46\u662f\u8fd8\u662f […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-232","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/posts\/232","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/comments?post=232"}],"version-history":[{"count":3,"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/posts\/232\/revisions"}],"predecessor-version":[{"id":312,"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/posts\/232\/revisions\/312"}],"wp:attachment":[{"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/media?parent=232"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/categories?post=232"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.chan.ink\/index.php\/wp-json\/wp\/v2\/tags?post=232"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n\n\n\nHow to fix update failed on Linux<\/h1>\n\n\n\n
1. \u201cError: Failed to download metadata for repo \u2018appstream\u2019: Cannot prepare internal mirrorlist: No URLs in mirrorlist<\/strong>\u201d<\/a><\/h3>\n\n\n\n
![\"\"](\"https:\/\/green.cloud\/docs\/wp-content\/uploads\/2024\/06\/nw14-1024x80.png\")
<\/figure>\n\n\n\nWhat is the Cause of This Error?<\/h5>\n\n\n\n
Solution<\/h5>\n\n\n\n
# sed -i 's\/mirrorlist\/#mirrorlist\/g' \/etc\/yum.repos.d\/CentOS-*\n# sed -i 's|#baseurl=http:\/\/mirror.centos.org|baseurl=http:\/\/vault.centos.org|g' \/etc\/yum.repos.d\/CentOS-*<\/pre>\n\n\n\n
# sed -i 's\/mirrorlist\/#mirrorlist\/g' \/etc\/yum.repos.d\/CentOS-Linux-*\n# sed -i 's|#baseurl=http:\/\/mirror.centos.org|baseurl=http:\/\/vault.epel.cloud|g' \/etc\/yum.repos.d\/CentOS-Linux-*<\/pre>\n\n\n\n
![\"\"](\"https:\/\/green.cloud\/docs\/wp-content\/uploads\/2024\/06\/nw16-1024x187.png\")
<\/figure>\n\n\n\n2. Error: GPG check FAILED<\/a><\/h3>\n\n\n\n
![\"\"](\"https:\/\/green.cloud\/docs\/wp-content\/uploads\/2024\/06\/nw17-1024x161.png\")
<\/figure>\n\n\n\nCause<\/h5>\n\n\n\n
Solution<\/h5>\n\n\n\n
# rpm --import https:\/\/repo.almalinux.org\/almalinux\/RPM-GPG-KEY-AlmaLinux<\/pre>\n\n\n\n
3. Error: sub-process \u2013 apt-listchanges<\/a><\/h3>\n\n\n\n
![\"\"](\"https:\/\/green.cloud\/docs\/wp-content\/uploads\/2024\/06\/image-eror2-1024x107.png\")
<\/figure>\n\n\n\nSolution<\/h5>\n\n\n\n
# mv \/etc\/apt\/apt.conf.d\/20listchanges \/etc\/apt\/apt.conf.d\/20listchanges.bak<\/code><\/pre>\n\n\n\n4. Error: The repository cdrom does not have a release file\u201d<\/a><\/h3>\n\n\n\n
Conclusion<\/a><\/h3>\n\n\n\n