Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Note that full support of 4G+ rpms is well known limitation of rpm and it's not one that is simple to fix. We have been working on this for past several months and IIRC the full support is not even in stable upstream release yet. I won't close this bug as wontfix but I certainly don't recommend providing this extension in RHEL7.0.
The support for large files is not something we can ever backport to rpm 4.11 (and thus rhel-7) within reason, the related changes are way, way too intrusive.
CLOSED DEFERRED, this is rhel-8 material.
Description of problem: rpm is not able to build packages bigger than 4GB. Version-Release number of selected component (if applicable): rpm-4.11.1-9.el7 How reproducible: Always Steps to Reproduce: 1. create a spec file, create big files (use "dd" for example) 2. rpmbuild --clean -bb specfile.spec Actual results: Processing files: 4GBpluspkg-1.0-1.noarch Provides: 4GBpluspkg = 1.0-1 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /root/rpmbuild/BUILDROOT/4GBpluspkg-1.0-1.x86_64 error: create archive failed on file /root/rpmbuild/BUILDROOT/4GBpluspkg-1.0-1.x86_64/usr/local/4GBpluspkg.tar: cpio: File too large for archive RPM build errors: create archive failed on file /root/rpmbuild/BUILDROOT/4GBpluspkg-1.0-1.x86_64/usr/local/4GBpluspkg.tar: cpio: File too large for archive End time: Thu Nov 28 09:03:14 EST 2013 Expected results: build successful Additional info: spec file: # cat 4GBpluspkg.spec Summary: 4GBpluspkg Package Name: 4GBpluspkg Version: 1.0 Release: 1 Group: System Environment/Base License: GPL BuildArch: noarch %description This is 4GBpluspkg test package %build # more-than-4G-file more-than-2G-file more-than-1G-file 10M-file 1M-file tar -cf 4GBpluspkg.tar more-than-4G-file more-than-2G-file more-than-1G-file 10M-file 1M-file %install mkdir -p %{buildroot}/usr/local/ mv 4GBpluspkg.tar %{buildroot}/usr/local/ %files /usr/local/4GBpluspkg.tar