Issued:

2013-11-20

Updated:

2013-11-20

RHBA-2013:1665 - rpm bug fix update

Synopsis

rpm bug fix update

Type/Severity

Bug Fix Advisory

Topic

Updated rpm packages that fix several bugs are now available for Red Hat Enterprise Linux 6.

Description

The RPM Package Manager (RPM) is a command-line driven package management system capable of installing, uninstalling, verifying, querying, and updating software packages.

This update fixes the following bugs:

• Previously, the brp-python-bytecompile script skipped those paths that included "/usr/lib.*/python.+/" string. Consequently, when creating an RPM that contained Python modules in paths (like "/opt/myapp/usr/lib64/python2.6/site-packages/mypackage/"), bytecode was not created. The reproducer specification has been changed, and bytecode is now created for all paths. (BZ#868332)

• When wildcard characters were used with the "%caps" tag in the spec file, the rpmbuild utility terminated unexpectedly. The provided patch corrects the problem by making a copy of the caps data for each file it applies to, and thus rpmbuild no longer crashes in the described scenario. (BZ#904818)

• Previously, when installing a package with a high (80k) number of files, the RPM Package Manager terminated unexpectedly with a segmentation fault. As a workaround, the segmentation fault has been replaced with an error message when a package with a high number of files fails to install. (BZ#919435)

• Previously the rpm program attempted to unconditionally process any "%include" directive it found in a spec file, either leading to unwanted content in the package or error messages. The updated rpm package properly honours various spec conditionals for "%include". (BZ#920190)

• With this update, Red Hat Enterprise Linux 5 backwards-compatibility option, "%_strict_script_errors macro", has been added. The default behavior of Red Hat Enterprise Linux 6 does not change with this update and users that do not demand this option specifically are not advised to use it. (BZ#963724)

Users of rpm are advised to upgrade to these updated packages, which fix these bugs. All running applications linked against the RPM library must be restarted for this update to take effect.

Solution

Before applying this update, make sure all previously released errata relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258

Affected Products

Updated Packages

• rpm-libs-4.8.0-37.el6.i686.rpm
• rpm-devel-4.8.0-37.el6.s390x.rpm
• rpm-debuginfo-4.8.0-37.el6.i686.rpm
• rpm-build-4.8.0-37.el6.s390x.rpm
• rpm-libs-4.8.0-37.el6.x86_64.rpm
• rpm-cron-4.8.0-37.el6.noarch.rpm
• rpm-debuginfo-4.8.0-37.el6.s390x.rpm
• rpm-debuginfo-4.8.0-37.el6.ppc.rpm
• rpm-devel-4.8.0-37.el6.ppc64.rpm
• rpm-devel-4.8.0-37.el6.ppc.rpm
• rpm-devel-4.8.0-37.el6.s390.rpm
• rpm-libs-4.8.0-37.el6.s390.rpm
• rpm-libs-4.8.0-37.el6.ppc64.rpm
• rpm-python-4.8.0-37.el6.s390x.rpm
• rpm-build-4.8.0-37.el6.i686.rpm
• rpm-apidocs-4.8.0-37.el6.noarch.rpm
• rpm-4.8.0-37.el6.i686.rpm
• rpm-build-4.8.0-37.el6.ppc64.rpm
• rpm-debuginfo-4.8.0-37.el6.s390.rpm
• rpm-debuginfo-4.8.0-37.el6.x86_64.rpm
• rpm-4.8.0-37.el6.src.rpm
• rpm-build-4.8.0-37.el6.x86_64.rpm
• rpm-python-4.8.0-37.el6.x86_64.rpm
• rpm-python-4.8.0-37.el6.i686.rpm
• rpm-4.8.0-37.el6.x86_64.rpm
• rpm-libs-4.8.0-37.el6.s390x.rpm
• rpm-devel-4.8.0-37.el6.x86_64.rpm
• rpm-4.8.0-37.el6.s390x.rpm
• rpm-libs-4.8.0-37.el6.ppc.rpm
• rpm-python-4.8.0-37.el6.ppc64.rpm
• rpm-debuginfo-4.8.0-37.el6.ppc64.rpm
• rpm-devel-4.8.0-37.el6.i686.rpm
• rpm-4.8.0-37.el6.ppc64.rpm

Fixes

• This content is not included.BZ - 904818
• This content is not included.BZ - 919435
• This content is not included.BZ - 920190

CVEs

(none)

References

(none)

Additional information

• The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
• Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.