- When running the
yum localinstallcommand, various requires, obsoletes, and conflicts situations were not handled properly and resulted in inconsistent package installations using different Yum commands. The underlying source code has been modified and Yum resolves all the aforementioned situations properly.
- When trying to execute the
yum update --skip-brokencommand on the command line, the package dependency resolution never ended. This bug is now fixed and dependencies are resolved successfully after executing the
yum update --skip-brokencommand.
- After creating a new yum history file, the
yum history statscommand failed with a traceback instead of reporting an actual error. This bug is now fixed and when the
yum history statscommand fails after creating a new yum history file, it displays an error message.
- Previously, when running the
yum makecachecommand, followed by the
yum -C updateinfocommand, the second command failed to execute because although the updateinfo file had been downloaded by
yum makecacheit was uncompressed and treated as unavailable by
yum -C updateinfo. This bug is now fixed and
yum -C updateinfoworks as expected in this scenario.
- Previously, when trying to install an obsoleted package from a repository, Yum reported Nothing to do instead of providing an "obsolete" error message. This bug is now fixed and Yum now correctly warns users about obsolete packages.
- Previously, when the
yum upgradecommand failed to execute, Yum displayed a misleading Protected multilib versions error message instead of the accurate one. This bug is now fixed and if Yum fails, it displays the correct error message.
- When Yum was executed by a regular user, Yum downloaded metadata even if the "root" metadata were up-to-date. This bug is now fixed and Yum does not download unnecessary data if the "root" metadata are up-to-date.
- A typo in the yum(8) man page has been fixed.
- After a rebase update of the createrepo utility, execution of the
createrepo --updatecommand took significantly longer. This update reduces the time for executing the
- Previously, when the
yum updateinfocommand, provided by the yum-security plug-in, was used, Yum did not merge the version information from multiple repositories. This could prevent the latest version of a package that was present in multiple repositories to not be installed. Now, when installing packages from multiple repositories, Yum installs only the latest packages available.
- Previously, when trying to reinstall an unavailable package and the execution failed, the exit code had the value of 0. This bug is now fixed and when reinstallation of an unavailable package fails, it returns an exit code with the value of 1.
- Previously, when the
yum-debug-restorecommand was used to restore multiple installonly packages, Yum tried to keep a limit of packages that were installed simultaneously and removed packages that were present in the system. Also, Yum restored multiple packages but assumed that just one would be installed. Yum's
installonly_limitconfiguration now determines what to install and remove correctly when multiple items are installed at once. This is most noticeable when using commands like
- When using the
yum.yumBase().update()function to specify a package name, version, and/or release of a certain package, the function terminated and failed to update the aforementioned variables. This bug is now fixed and the
yum.yumBase().update()function can be used successfully to specify a package name, version, and release.
- Previously, when trying to resolve dependencies while updating packages that had dependencies, Yum entered a loop and no packages were installed after execution of the
yum updatecommand. After this update, the
yum updatecommand now handles packages with obsoleting dependencies as expected.
- Due to an incorrect prioritization of actions performed by Yum after entering a command with a syntactically incorrect subcommand, Yum performed a series of unnecessary actions before acknowledging the typo. This bug has been fixed and Yum performs an immediate syntax check in the described scenario.
- When updateinfo.xml was generated via the update_md.UpdateNotice() method, the yum API only accounted for the "issued date" element and ignored the updated date element. Now, the yum API accounts for the "updated date" element and the "updated date" element is displayed in the XML file.
- Previously, users were not notified that different certificate files with the same basename were treated as identical, which could lead to various problems. With this update, Yum checks certificate files for such duplicates and displays an error message appropriately.