{"id":4980,"date":"2024-08-19T20:42:47","date_gmt":"2024-08-19T15:12:47","guid":{"rendered":"https:\/\/www.veeble.org\/kb\/?p=4980"},"modified":"2025-02-20T16:01:17","modified_gmt":"2025-02-20T10:31:17","slug":"how-to-undo-the-last-yum-update-easy-rollback-guide","status":"publish","type":"post","link":"https:\/\/www.veeble.com\/kb\/how-to-undo-the-last-yum-update-easy-rollback-guide\/","title":{"rendered":"How to Undo the Last Yum Update: Easy Rollback Guide"},"content":{"rendered":"\n<figure class=\"wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex\">\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/www.veeble.org\/kb\/wp-content\/uploads\/2024\/08\/Undo-last-update-by-yum-roll-back-feature.jpeg\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" width=\"1792\" height=\"485\" data-id=\"5028\" src=\"https:\/\/www.veeble.org\/kb\/wp-content\/uploads\/2024\/08\/Undo-last-update-by-yum-roll-back-feature.jpeg\" alt=\"Learn how to undo the last YUM update with these YUM roll back guide.\" class=\"wp-image-5028\" srcset=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/Undo-last-update-by-yum-roll-back-feature.jpeg 1792w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/Undo-last-update-by-yum-roll-back-feature-300x81.jpeg 300w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/Undo-last-update-by-yum-roll-back-feature-1024x277.jpeg 1024w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/Undo-last-update-by-yum-roll-back-feature-768x208.jpeg 768w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/Undo-last-update-by-yum-roll-back-feature-1536x416.jpeg 1536w\" sizes=\"auto, (max-width: 1792px) 100vw, 1792px\" \/><\/a><\/figure>\n<\/figure>\n\n\n\n<p>This guide provides step-by-step instructions for administrators and developers working with CentOS, RHEL, or CloudLinux systems to <strong>undo the last Yum update and rollback to the previous stable state<\/strong>. It covers identifying problematic updates, removing them, and reverting to the earlier version.<\/p>\n\n\n\t\t\t\t<div class=\"wp-block-uagb-table-of-contents uagb-toc__align-left uagb-toc__columns-1  uagb-block-2af4b4a4      \"\n\t\t\t\t\tdata-scroll= \"1\"\n\t\t\t\t\tdata-offset= \"30\"\n\t\t\t\t\tstyle=\"\"\n\t\t\t\t>\n\t\t\t\t<div class=\"uagb-toc__wrap\">\n\t\t\t\t\t\t<div class=\"uagb-toc__title\">\n\t\t\t\t\t\t\tTable Of Contents\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<div class=\"uagb-toc__list-wrap \">\n\t\t\t\t\t\t<ol class=\"uagb-toc__list\"><li class=\"uagb-toc__list\"><a href=\"#undoing-yum-updates-risks-and-consequences\" class=\"uagb-toc-link__trigger\">Undoing YUM Updates: Risks and Consequences<\/a><li class=\"uagb-toc__list\"><a href=\"#methods-to-undo-the-last-yum-update\" class=\"uagb-toc-link__trigger\">Methods to Undo the Last Yum Update<\/a><ul class=\"uagb-toc__list\"><li class=\"uagb-toc__list\"><a href=\"#1-manual-rollback-using-package-versions\" class=\"uagb-toc-link__trigger\">1. Manual Rollback using Package Versions<\/a><li class=\"uagb-toc__list\"><li class=\"uagb-toc__list\"><a href=\"#2-using-yum-history-to-rollback-updates\" class=\"uagb-toc-link__trigger\">2. Using Yum History to Rollback Updates<\/a><li class=\"uagb-toc__list\"><li class=\"uagb-toc__list\"><a href=\"#3-restoring-from-a-backup-using-yum-history\" class=\"uagb-toc-link__trigger\">3. Restoring from a Backup using Yum History<\/a><\/li><\/ul><\/li><li class=\"uagb-toc__list\"><a href=\"#troubleshooting-common-issues-during-rollback\" class=\"uagb-toc-link__trigger\">Troubleshooting Common Issues During Rollback<\/a><ul class=\"uagb-toc__list\"><li class=\"uagb-toc__list\"><a href=\"#experience-the-power-of-a-dedicated-server-with-our-vps-hosting-plans\" class=\"uagb-toc-link__trigger\">Experience the power of a dedicated server with our VPS hosting plans.<\/a><\/ul><\/ul><\/ol>\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\n\n\n<p><\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"undoing-yum-updates-risks-and-consequences\">Undoing YUM Updates: Risks and Consequences<\/h2>\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Potential dependency conflicts<\/strong>: Reverting a package to an older version may break <a href=\"https:\/\/askubuntu.com\/questions\/361741\/what-are-dependencies\" target=\"_blank\" rel=\"noopener\">dependencies<\/a>, causing software malfunction or failure.<\/li>\n\n\n\n<li><strong>System configurations, scripts, or customizations<\/strong>: The rollback process may undo changes introduced by the previous update, leading to unexpected behavior or manual intervention.<\/li>\n\n\n\n<li><strong>Impact on data or services<\/strong>: Undoing a YUM update may revert changes to database schemas, configuration files, or other critical system components, disrupting normal application or service operations.<\/li>\n\n\n\n<li><strong>Recommendations<\/strong>: Thorough research, understanding the update&#8217;s impact, and having a <a href=\"https:\/\/www.veeble.org\/kb\/setup-linux-vps-backup-server-using-rsync\/\" target=\"_blank\" rel=\"noopener\">backup<\/a> strategy to mitigate risks and ensure a successful rollback process.<\/li>\n<\/ul>\n\n\n\n<p><\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"methods-to-undo-the-last-yum-update\">Methods to Undo the Last Yum Update<\/h2>\n\n\n<p>The choice of method to undo the last YUM update on your CentOS, RHEL, or CloudLinux system depends on the specific circumstances and control level required. The three methods we have are the following:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Manual rollback using package versions<\/li>\n\n\n\n<li>Using yum history to rollback updates<\/li>\n\n\n\n<li>Restoring from a backup using yum history<\/li>\n<\/ol>\n\n\n\n<p><\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"1-manual-rollback-using-package-versions\">1. Manual Rollback using Package Versions<\/h3>\n\n\n<p>One of the most straightforward methods to undo a YUM update is to manually roll back the affected packages to their previous versions. This approach involves <strong>identifying the problematic package(s), determining the previous version(s), and then installing the older version(s)<\/strong> to revert the system to the desired state.<\/p>\n\n\n\n<p>To perform a manual rollback, you can use the <strong>yum downgrade<\/strong> command, followed by the package name and the specific version you want to install.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>yum downgrade &lt;package name&gt; <\/code><\/pre>\n\n\n\n<p>For example, if you need to undo an update to the <code>httpd<\/code> package, you can use the following command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>yum downgrade httpd-2.4.6-93.el7.x86_64<\/code><\/pre>\n\n\n\n<p>This command will install the previous version of the <code>httpd<\/code> package, effectively undoing the recent update.<\/p>\n\n\n\n<p>It&#8217;s important to note that when performing a manual rollback, you need to be aware of any dependencies that the affected package(s) may have. Ensure that you also downgrade any dependent packages to their previous versions to avoid compatibility issues.<\/p>\n\n\n\n<p><\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"2-using-yum-history-to-rollback-updates\">2. Using Yum History to Rollback Updates<\/h3>\n\n\n<p>Another method to undo a <a href=\"https:\/\/www.wikihow.com\/Yum-Update\" target=\"_blank\" rel=\"noopener\">YUM update<\/a> is to use the <strong>yum history<\/strong> command, which provides a detailed history of all package installations, updates, and removals performed on your system. This approach allows you to easily identify the specific update you want to undo and revert the system to its previous state.<\/p>\n\n\n\n<p>To use <strong>yum history<\/strong> for rollback, follow these steps:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Run the <strong>yum history list<\/strong> command to view the history of yum transactions.<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>yum history list<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-2 is-layout-flex wp-block-gallery-is-layout-flex\">\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/www.veeble.org\/kb\/wp-content\/uploads\/2024\/08\/yum-history-command.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" width=\"1137\" height=\"140\" data-id=\"5030\" src=\"https:\/\/www.veeble.org\/kb\/wp-content\/uploads\/2024\/08\/yum-history-command.png\" alt=\"yum history list command\" class=\"wp-image-5030\" srcset=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/yum-history-command.png 1137w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/yum-history-command-300x37.png 300w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/yum-history-command-1024x126.png 1024w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/yum-history-command-768x95.png 768w\" sizes=\"auto, (max-width: 1137px) 100vw, 1137px\" \/><\/a><\/figure>\n<\/figure>\n\n\n\n<ol start=\"2\" class=\"wp-block-list\">\n<li>Identify the transaction ID (TID) or the date\/time of the update you want to undo.<\/li>\n\n\n\n<li>Use the <strong>yum history undo &lt;TID&gt;<\/strong> command to revert the system to the state before the selected transaction.<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>yum history undo &lt;TID&gt;<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-3 is-layout-flex wp-block-gallery-is-layout-flex\">\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/www.veeble.org\/kb\/wp-content\/uploads\/2024\/08\/yum-history-undo-command.gif\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" width=\"1208\" height=\"234\" data-id=\"5032\" src=\"https:\/\/www.veeble.org\/kb\/wp-content\/uploads\/2024\/08\/yum-history-undo-command.gif\" alt=\"yum history undo command for roll back the update\" class=\"wp-image-5032\"\/><\/a><\/figure>\n<\/figure>\n\n\n\n<p>For example, if you want to undo the last YUM update, you can use the following command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code><code> <span style=\"background-color: initial;color: var(--ast-global-color-3)\">yum history undo last<\/span><\/code><\/code><\/pre>\n\n\n\n<p>This command identifies the steps needed to revert the system. It restores the state before the latest YUM transaction.<\/p>\n\n\n\n<p>The <strong>yum history<\/strong> approach is helpful for undoing multiple updates. It is also useful when updates have complex dependencies. The YUM history feature ensures that the rollback process correctly handles all the necessary package versions and dependencies.<\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"3-restoring-from-a-backup-using-yum-history\">3. Restoring from a Backup using Yum History<\/h3>\n\n\n<p>If previous methods are not feasible, you may want a complete system restoration. Consider restoring from a backup. This approach uses the <strong>yum history<\/strong> command to identify the backup snapshot for the desired system state. Then, restore the system from that backup.<\/p>\n\n\n\n<p>To restore from a backup using <strong>yum history<\/strong>, follow these steps:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Run the <strong>yum history list<\/strong> command to view the history of YUM transactions.<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>yum history list<\/code><\/pre>\n\n\n\n<ol start=\"2\" class=\"wp-block-list\">\n<li>Identify the transaction ID (TID) or the date\/time of the backup snapshot you want to restore.<\/li>\n\n\n\n<li>Use the <strong>yum-complete-transaction &#8211;undo &lt;TID&gt;<\/strong> command to initiate the restoration process.<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>yum-complete-transaction --undo &lt;TID&gt;<\/code><\/pre>\n\n\n\n<p>This command will undo all the YUM transactions that occurred after the selected backup snapshot, effectively restoring your system to its previous state.<\/p>\n\n\n\n<p>It&#8217;s important to note that this approach requires you to have a reliable backup of your system, which should be regularly maintained and tested to ensure its integrity. Restoring from a backup can be a more time-consuming process, but it provides a comprehensive way to undo a YUM update and revert your system to a known good state.<\/p>\n\n\n\n<p><\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"troubleshooting-common-issues-during-rollback\">Troubleshooting Common Issues During Rollback<\/h2>\n\n\n<p>When rolling back a YUM update, unexpected issues like <strong>dependency conflicts, third-party repository interference, or system configuration changes may arise<\/strong>. These problems can prevent a successful rollback. <\/p>\n\n\n<h6 class=\"wp-block-heading\" id=\"1-dependency-conflicts-during-yum-history-undo-command\">1. <span style=\"text-decoration: underline\">Dependency Conflicts during YUM HISTORY UNDO Command<\/span><\/h6>\n\n\n<p>A dependency error is shown below, which occurred when a user rollback the system:<\/p>\n\n\n\n<figure class=\"wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-4 is-layout-flex wp-block-gallery-is-layout-flex\">\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/www.veeble.org\/kb\/wp-content\/uploads\/2024\/08\/dependency-error.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" width=\"986\" height=\"130\" data-id=\"5021\" src=\"https:\/\/www.veeble.org\/kb\/wp-content\/uploads\/2024\/08\/dependency-error.png\" alt=\"Error: Package: httpd-2.4.6-93.el7.centos.x86_64 (base)\nRequires: httpd-tools = 2.4.6-93.el7.centos\nRemoving: httpd-tools-2.4.6-97.el7.centos.x86_64 (@updates)\nhttpd-tools = 2.4.6-97.el7.centos\" class=\"wp-image-5021\" srcset=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/dependency-error.png 986w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/dependency-error-300x40.png 300w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/dependency-error-768x101.png 768w\" sizes=\"auto, (max-width: 986px) 100vw, 986px\" \/><\/a><\/figure>\n<\/figure>\n\n\n\n<p>This indicates that the <code>httpd<\/code> package requires a specific version of <code>httpd-tools<\/code>, which is no longer available. You can manually install the required version of the conflicting package. For example, with the command below, we can manually install the required package version mentioned in the error.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo yum install httpd-tools-2.4.6-93.el7.centos.x86_64<\/code><\/pre>\n\n\n\n<p>After resolving the dependency conflict, attempt the rollback again with the same command you did before: <\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo yum history undo &lt;transaction id&gt;<\/code><\/pre>\n\n\n\n<p>Sometimes, multiple packages can cause the same problem. Using the <strong>&#8211;allowerasing<\/strong> option is the best choice here. When using <strong>&#8211;allowerasing<\/strong> option, YUM will automatically handle the erasure of conflicting packages.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo yum history undo &lt;transaction id&gt; --allowerasing<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-verse\">When using --allowerasing option with <strong>sudo yum history undo<\/strong> command, there\u2019s a risk of removing packages that might be important for other parts of the system, potentially leading to further issues. Therefore, use it with caution.<\/pre>\n\n\n\n<p><\/p>\n\n\n<h6 class=\"wp-block-heading\" id=\"2-thirdparty-repository-interference-during-yum-history-undo-command\">2. <span style=\"text-decoration: underline\">Third-Party Repository Interference during YUM HISTORY UNDO Command<\/span><\/h6>\n\n\n<p><a href=\"https:\/\/www.veeble.org\/kb\/adding-additional-repositories-in-centos\/\" target=\"_blank\" rel=\"noopener\">Third-party repositories<\/a> can introduce packages that conflict with those in the <a href=\"https:\/\/rpm.org\/documentation.html\" target=\"_blank\" rel=\"noopener\">official repositories<\/a>. This can complicate rollbacks because the versions of packages available from third-party repositories may differ from those in the official repositories.<\/p>\n\n\n\n<p>To resolve this, you can temporarily disable third-party repositories to avoid conflicts during the execution of the <strong>yum history undo<\/strong> command. To list all enabled repositories, execute the command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>yum repolist<\/code><\/pre>\n\n\n\n<p>After identifying the repositories to disable, execute the following command, replacing &lt;repository_name&gt; with the name of the third-party repository you wish to disable.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo yum-config-manager --disable &lt;repository_name&gt;<\/code><\/pre>\n\n\n\n<p>With the third-party repositories disabled, attempt the rollback again!<\/p>\n\n\n\n<p><\/p>\n\n\n<h6 class=\"wp-block-heading\" id=\"3-reverting-system-configuration-changes-after-rollback\"><span style=\"text-decoration: underline\">3. Reverting System Configuration Changes After RollBack<\/span><\/h6>\n\n\n<p>During an update, configuration files may change, and rolling back a package might not revert these changes, causing inconsistencies. The only solution is to manually replace the current configurations with the old ones.<\/p>\n\n\n\n<pre class=\"wp-block-verse\">When updating YUM, YUM saves your modified configuration files with a .rpmsave extension in the same path as your system configuration files (\/etc). With these .rpmsave files, you can revert the system configuration files after rollback.<\/pre>\n\n\n\n<p>Identify any configuration files that were altered during the update. These files are often located in <code>\/etc\/<\/code>. For example, if you updated Apache (httpd), you might check the configuration with:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>diff \/etc\/httpd\/conf\/httpd.conf \/etc\/httpd\/conf\/httpd.conf.rpmsave<\/code><\/pre>\n\n\n\n<p>This command compares the current configuration with the saved configuration before the update.<br>If you need to revert the configuration files to their previous states, just copy the .rpmsave file to the original file. For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo cp \/etc\/httpd\/conf\/httpd.conf.rpmsave \/etc\/httpd\/conf\/httpd.conf<\/code><\/pre>\n\n\n\n<p>This command copies the saved configuration file back to its original location. After restoring the configuration file, remember to reboot the specific service related to the configuration or <a href=\"https:\/\/www.veeble.org\/kb\/how-to-reboot-linux-and-windows-using-the-command-line\/\" target=\"_blank\" rel=\"noopener\">reboot the system<\/a>.<\/p>\n\n\n\n<p>These are some troubleshooting steps. However, different issues may arise. Research online and consult professionals for assistance.<\/p>\n\n\n\n<div class=\"wp-block-uagb-separator uagb-block-4cd17cc9\"><div class=\"wp-block-uagb-separator__inner\" style=\"--my-background-image:\"><\/div><\/div>\n\n\n\n<p>By following this guide, you can easily undo the last YUM update, and ensure a more reliable and stable computing environment for your CentOS, RHEL, or CloudLinux systems.<\/p>\n\n\n\n<div style=\"height:35px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-uagb-call-to-action uagb-block-136d3d69 wp-block-button\"><div class=\"uagb-cta__wrap\"><h3 class=\"uagb-cta__title\">Experience the power of a dedicated server with our VPS hosting plans.<\/h3><p class=\"uagb-cta__desc\">With our VPS hosting, you&#8217;ll get your own dedicated server with root access, so you can customize it to your needs.<\/p><\/div><div class=\"uagb-cta__buttons\"><a href=\"https:\/\/www.veeble.com\/in\/kvm-vps\/\" class=\"uagb-cta__button-link-wrapper wp-block-button__link\" target=\"_blank\" rel=\"noopener noreferrer\">Get started<svg xmlns=\"https:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\"><path d=\"M504.3 273.6l-112.1 104c-6.992 6.484-17.18 8.218-25.94 4.406c-8.758-3.812-14.42-12.45-14.42-21.1L351.9 288H32C14.33 288 .0002 273.7 .0002 255.1S14.33 224 32 224h319.9l0-72c0-9.547 5.66-18.19 14.42-22c8.754-3.809 18.95-2.075 25.94 4.41l112.1 104C514.6 247.9 514.6 264.1 504.3 273.6z\"><\/path><\/svg><\/a><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Discover how to easily undo the last YUM update with our beginner-friendly rollback guide to resolve issues caused by recent updates.<\/p>\n","protected":false},"author":7,"featured_media":7261,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[5],"tags":[],"class_list":["post-4980","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux"],"uagb_featured_image_src":{"full":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/How-to-Undo-the-Last-Yum-Update-Easy-Rollback-Guide.png",1366,768,false],"thumbnail":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/How-to-Undo-the-Last-Yum-Update-Easy-Rollback-Guide-150x150.png",150,150,true],"medium":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/How-to-Undo-the-Last-Yum-Update-Easy-Rollback-Guide-300x169.png",300,169,true],"medium_large":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/How-to-Undo-the-Last-Yum-Update-Easy-Rollback-Guide-768x432.png",768,432,true],"large":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/How-to-Undo-the-Last-Yum-Update-Easy-Rollback-Guide-1024x576.png",1024,576,true],"1536x1536":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/How-to-Undo-the-Last-Yum-Update-Easy-Rollback-Guide.png",1366,768,false],"2048x2048":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2024\/08\/How-to-Undo-the-Last-Yum-Update-Easy-Rollback-Guide.png",1366,768,false]},"uagb_author_info":{"display_name":"Adrian Antony","author_link":"https:\/\/www.veeble.com\/kb\/author\/adrian\/"},"uagb_comment_info":0,"uagb_excerpt":"Discover how to easily undo the last YUM update with our beginner-friendly rollback guide to resolve issues caused by recent updates.","_links":{"self":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/4980","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/comments?post=4980"}],"version-history":[{"count":26,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/4980\/revisions"}],"predecessor-version":[{"id":7363,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/4980\/revisions\/7363"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/media\/7261"}],"wp:attachment":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/media?parent=4980"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/categories?post=4980"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/tags?post=4980"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}