4.365. yum

When uninstalling a package, the "yum remove" command may have previously reported success even when the package could not be removed due to an error in the %pre scriptlet. With this update, this error has been fixed, and when yum fails to remove a package, it no longer claims that it succeeded.

When running the "yum -v repolist" command, the previous version of the yum utility may have incorrectly displayed a duplicate "Repo-baseurl" line for a repository with no mirrors. This update applies a patch that corrects this error, and the output of the "yum -v repolist" command no longer contains duplicate lines.

Previously, an attempt to install a package that was larger than 4 GB on a 32-bit architecture caused yum to terminate unexpectedly with a traceback. With this update, the underlying source code has been adapted to work around this problem, and packages larger than 4 GB can now be installed as expected.

Prior to this update, running a yum command with the "--installroot" command line option caused it to report the following warning:

Ignored option -c (probably due to merging -yc != -y -c)

This update adapts the underlying source code not to display this warning when the "--installroot" option is in use, resolving this issue.

Under certain circumstances, an attempt to use the RepoStorage API may have failed with an AttributeError. With this update, this error has been fixed, and the RepoStorage API can now be used as expected.

Previously, the repodiff utility used a stale metadata cache in subsequent runs. When two repodiff commands were executed in succession, the second run reused cached data from the first. This bug has been fixed and repodiff now properly validates the metadata if a connection cannot be established or the cached data are about to be reused.

Prior to this update, when the "yum -q history addon-info last saved_tx" command was used to store transaction data in a file, an attempt to supply this file to the "yum load-transaction" command in order to repeat the transaction failed with an error, because the output contained extra lines. This update corrects the underlying source code to make sure the "yum -q history addon-info last saved_tx" command produces valid output, and adapts "yum load-transaction" to accept older version of the output as well.

In very rare cases, the yum utility may have incorrectly kept using old updateinfo, pkgtags, and groups metadata. When this happened, users may have been unaware of available updates for up to 6 hours. This update applies a patch that prevents yum from using outdated metadata, resolving this issue.

The "yum history" command has been adapted to store and display yumdb and rpmdb information, such as from which repository was a particular package installed.

The "yum update" command can now be used to update a package to a specific version.

The yum utility no longer asks the user to report a bug when the dependency solver (depsolve) encounters an error.

The anacron scheduler starts the yum-cron utility with the "nice" value of 10. This caused Yum's RPM transactions to run at very low priority level. Also, any updated service inherited this "nice" value, which influenced the system behavior. This update adds the "reset_nice" configuration option, which allows Yum to reset the "nice" value to 0 before running an RPM transaction. With this option set, Yum's RPM transactions run at normal priority level so that updated services are restarted with normal priority as expected.