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:
Trying to use `dnf builddep` on the kernel package on a x86_64 system, the tool complains about a missing package:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# dnf builddep kernel-4.18.0-425.10.1.el8_7.src.rpm
[...]
No matching package to install: 'opencsd-devel >= 1.0.0-2'
[...]
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
This package is used on aarch64 only, from the spec file:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
%ifarch aarch64
BuildRequires: opencsd-devel >= 1.0.0-2
%endif
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
I then tried using global option `--forcearch=x86_64` but this doesn't help either.
Would it be possible to force using a specific arch and/or default to system's arch?
Version-Release number of selected component (if applicable):
dnf-4.7.0-11.el8.noarch
How reproducible:
Always, see above.
builddep on an src.rpm uses the exact recorded dependencies in the src.rpm header, which are specific to the platform and environment the src.rpm was built on. That's a feature on which our buildsystems rely on, but in the buildsystem the src.rpm is always specific to that architecture. Where this all goes missing is when an src.rpm of a random arch is thrown into the repo, and then used in the same manner for other platforms.
Using src.rpm recorded data is only valid for the platform and the distro it was created on, everything else needs to parse the spec to get something meaningful. For that, unpack the src.rpm and run 'dnf builddep kernel.spec' instead.
What the builddep plugin could and should do is check whether the architecture matches and complain when it doesn't. And have an option to automatically pull the spec from an src.rpm and parse for dependencies.
Comment 5RHEL Program Management
2023-09-01 22:36:48 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6RHEL Program Management
2023-09-01 22:37:34 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.
Users watching this BZ may not be automatically added to the Jira ticket. Be sure to add yourself to the Watchers field in the Jira issue if you desire to continue following this issue.