Red Hat Bugzilla – Bug 1434656
rpm installation failed with --relocate option due to large header size
Last modified: 2018-04-10 11:59:42 EDT
Description of problem: This is related with a old fedora bug. https://bugzilla.redhat.com/show_bug.cgi?id=982348 A customer has a custom package with a large number of files. He could not install it on RHEL7.3 with --relocate option. I put the actual command and the result in another private comment. After investigation, it failed with the following code (hdrchkData) in headerExport(). /* Sanity checks on header intro. */ if (hdrchkTags(il) || hdrchkData(dl)) goto errxit; (gdb) print il $3 = 68 (gdb) print/x dl $2 = 0x1496158 In lib/header_internal.h: /** * Sanity check on data size and/or offset and/or count. * This check imposes a limit of 16 MB, more than enough. */ #define HEADER_DATA_MAX 0x00ffffff #define hdrchkData(_nbytes) ((_nbytes) & (~HEADER_DATA_MAX)) It failed in hdrchkData(). Can we remove this limitation by increasing the maximum header data? Version-Release number of selected component (if applicable): Red Hat Enterprise Linux 7 How reproducible: Always Steps to Reproduce: I will write this in a separated private comment. Actual results: installation failed. rpmdb was not updated. But, the files are installed on the system. Expected results: installation doesn't fail Additional info: C#1 in https://bugzilla.redhat.com/show_bug.cgi?id=982348 > But yes, this needs fixing sooner than later. This comment was created in 2013, so I want to know if it can be fixed in RHEL7 at this stage.
Also, it seems that BZ#953719 referred from above bugzilla (BZ#982348, C#4) The patch should be https://github.com/rpm-software-management/rpm/commit/da3a3a14e757ccd517e2eb2a3f0293ff48b3ff7f, and it has already been applied to RHEL7.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0877