Description of problem:
system-profile-transition rpm should avoid using advanced rpmlib capabilities. hammer import content-host command shows build instruction how to create on Sat6 an rpm for systems transition. Built rpm "system-profile-transition-*.rpm" requires some advanced rpmlib capabilities!
Just imagine situation Sat6 is on RHEL6 machine, therefore built rpm will require rpmlib capabilities like FileDigests, PayloadIsXz, according to building OS. These capabilities cannot be handled on RHEL5. And the rpm is going to be installed on Sat5 machine, which can have various OSes. The problem can arise if build_OS > install_OS.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. @sat6 obtain wrong build instruction:
# hammer import content-host --csv-file=/tmp/export/system-profiles.csv --export-directory=/root/content-hosts
2. @sat6 build the rpm:
# rpmbuild -ba --define "_topdir /root/content-hosts" /root/content-hosts/SPECS/system-profile-transition-*.spec
3. @sat5 built rpm requires advanced rpmlib capabilities:
# rpm -ivh /root/system-profile-transition-<fqdn>-1409658421-0.0.1-1.noarch.rpm
error: Failed dependencies:
rpmlib(FileDigests) <= 4.6.0-1 is needed by system-profile-transition-<fqdn>-1410316694-0.0.1-1.noarch
rpmlib(PayloadIsXz) <= 5.2-1 is needed by system-profile-transition-<fqdn>-1410316694-0.0.1-1.noarch
the rpm built on rhel6/7 cannot be installed on rhel5
the rpm built on rhel6/7 can be installed on rhel5
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Right, we need to add more defines to the rpmbuild, see
for more info.
We need to add these:
%define _binary_filedigest 1
%define _binary_payload w9.gzdio
Note: The implication of this bug is that customers running Sat5 on RHEL5 will not be able to use the sat5to6 transition tool.
upstream commit 8cb9d13800ac83916d244425972c8b2a633ed691
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.