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.

Description of problem:
Attempting to build the latest perl-Sys-Virt RPM, I encountered an unresolvable dependency in Systemtap on PPC architectures:

http://download.devel.redhat.com/brewroot/work/tasks/7361/3927361/root.log

DEBUG util.py:256:  Error: Missing Dependency: kernel-devel is needed by package systemtap-1.6-4.el6.ppc (build)


The problem is that 'kernel-devel' is not built on PPC architecture in RHEL-6. So AFAICT, there is no way that the 'systemtap' RPM can ever be installed on the PPC archictecture, despite it being built.

Version-Release number of selected component (if applicable):
systemtap-1.6-4.el6.ppc

How reproducible:
Always

Steps to Reproduce:
1. yum install systemtap  on a 'ppc' RHEL-6 root. (ie *not* ppc64)
2.
3.
  
Actual results:
DEBUG util.py:256:  Error: Missing Dependency: kernel-devel is needed by package systemtap-1.6-4.el6.ppc (build)

Expected results:
It is unclear what we should do here, but I can see two options

 - Don't build systemtap on PPC architectures
 - Built systemtap on PPC, but don't put a dep on kernel-devel which doesn't exist


Additional info:

Dan, what kernel RPMs are used on your installation?

This is not a host install, this is a mock build root - see the URL in the comment above. I guess that brew does 'ppc' build roots on a ppc64 host, but that's not relevant to the dependency resolution of mock inside the root.

Sorry, I don't understand.  What kernel would be installed in a mock buildroot?
Or do mock buildroots simply lack kernels entirely?  I see no ppc (32-bit) kernel
build, and a 32-bit systemtap.ppc should be quite happy with a 64-bit
kernel-devel.ppc64 installed.

There's no kernel package installed in the mock buildroot at all - only a noarch  kernel-headers package. IIUC, The ppc build roots won't ever pull in RPMs from ppc64 RPMs.

So even though systemtap.ppc can work fine with a kernel-devel.ppc64, AFAICT, you can't install that combo inside mock :-(

That seems like a mock problem, rather than a systemtap one.

It appears as though mock isn't in RHEL, so we can't file a bug against it
for its treatment of kernel-* prereqs.  It is not wrong for systemtap to
prereq kernel-devel.