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.

Description of problem:

I have here systemtap-1.2-1.el6.src.rpm which I'd like to rebuild. Some BRs are missing so I run `yum-builddep systemtap-1.2-1.el6.src.rpm` it resolves them and installs. Then I try to rebuild package `rpmbuild --rebuild systemtap-1.2-1.el6.src.rpm` but it fails:

[root@auto-i386-001 ~]# rpmbuild --rebuild systemtap-1.2-1.el6.src.rpm 
Installing systemtap-1.2-1.el6.src.rpm
[...]
error: Failed build dependencies:
	crash-devel is needed by systemtap-1.2-1.el6.i686

systemtap spec file looks like this:

%ifarch ppc
# crash is not being built on rhel6 beta on ppc
%{!?with_crash: %global with_crash 0}
%else
%{!?with_crash: %global with_crash 1}
%endif

[...]

%if %{with_crash}
BuildRequires: crash-devel zlib-devel
%endif

[...]

%if %{with_crash}
Requires: crash
%endif

etc.


It seems that yum-builddep fails to resolve BuildRequire if it is "hidden" by %global definition.

Version-Release number of selected component (if applicable):

yum-3.2.27-4.el6.noarch
yum-utils-1.1.26-7.el6.noarch
systemtap-1.2-1.el6.i686

How reproducible:

always. all archs.

Expected results:

crash-devel resolved & installed as others BRs.

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

can you run:

rpm -qpR systemtap-1.2-1.el6.src.rpm

I suspect the buildreq is not listed there, either.

yum-builddep cannot read the spec file and parse the deps that show up there. It only gets the buildreqs from the requires in the src rpm header.

Specifically, this is the same "bug" as using %{_isa} in BuildRequires ... they are then "fixed" at the point rpmbuild creates the .src.rpm, so you either need to create a .src.rpm for each arch. ... or do something else.

I can see. Thanks for clarification.