4.93. rpm

Bug Fixes

BZ#648516

Previously, the package size was recorded incorrectly for packages built on big-endian platforms (PowerPC or IBM S/390), which would show up in Anaconda as packages having zero bytes. With this update, package sizes are correctly recorded on all platforms, but older packages built with the flawed versions of RPM still show incorrect sizes.

BZ#671194

Previously, when multiple packages failed to update correctly, the failed packages could get removed from the system entirely. With this update, the rpm and yum utilities can handle multiple failures during updates without unexpected package removals.

BZ#706935

Previously, attempts to install packages with a large number of files (approximately 80,000 or more), could have caused RPM to terminate unexpectedly with a segmentation fault due to the RPM header exceeding its upper limit. This update increases the header limit so RPM is able to handle larger package installs, and crashes no longer occur in the described scenario.

BZ#716853

A new size check recently added to rpmbuild caused rpmbuild to display an error message and exit if the contents of the RPM file exceeded 2GB in size. This size check was performed prior to the elimination of duplicate files, however, in some cases it was possible for rpmbuild to exit with a ">2GB" warning even if the contents of the RPM file were actually smaller than 2GB. With this update, the size check for rpmbuild is expanded, and it is possible to build RPM files larger than 2GB.

Bug Fix

BZ#906019

Previously, when updating packages with the rpm or yum utilities, users experienced multiple failures and the failed packages were removed from the system entirely. With this update, the rpm and yum utilities can handle multiple failures during updates without unexpected package removals.