Description of problem:
Packages built on RHEL6 fail to install on EL5 due to rpm changes
Version-Release number of selected component (if applicable):
on RHEL6 Beta, packages were built using : rpm-4.8.0-8.el6.x86_64
Client installed attempted using : rpm-22.214.171.124-18.el5
Installing the package using yum results in :
ERROR with rpm_check_debug vs depsolve:
rpmlib(FileDigests) is needed by areca_cli
rpmlib(PayloadIsXz) is needed by areca_cli
The same messages and errors are reported when using rpm directly off the command line
The package should just install
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
This is intentional... they're both features that we intend to use in RHEL 6 packages.
You can pass:
--define "_source_filedigest_algorithm 1" \
--define "_binary_filedigest_algorithm 1"
to rpm at build time to use older hashes, and you can pass:
--define "_binary_payload w9.gzdio"
to rpm at build time to use older compression.
Certaily, an RFE could be entered to support these features on older RHEL, but that RFE would be against RHEL 4/RHEL 5.
Shall I create such an RFE?
To my knowledge, Fedora/EPEL people regularly backport newer RPM features to enable their RHEL5 builders to cross-build packages for newest Fedora and RHEL6, so including this into at least into RHEL5 after an appropriate testing phase would be straightforward.
As it turns out, RFEs for both features (stronger hashes and xz payload) are already filled: