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:
For some reason, I had to use RHEL7 machine to test and scratch build Fedora rawhide packages. I checkout master branch of libreoffice and tried "fedpkg srpm" on RHEL7

I got error
"error: line 289: Unknown tag: Recommends: libreoffice-calc(x86-64) = 1:5.1.1.1-4.fc24
error: query of specfile /home/parag/libreoffice/libreoffice.spec failed, can't parse

Could not execute srpm: Could not get n-v-r-e from '\n'
"

I assume this mean rpm got no support of weakdeps in RHEL7. But is there no way then to have some kind of forceful generation of srpm, I can use then koji for official or scratch build.

Version-Release number of selected component (if applicable):
rpm-4.11.3-17.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.fedpkg co libreoffice
2.cd libreoffice
3. fedpkg srpm

Actual results:
as reported above, could not execute srpm

Expected results:
should give me srpm at least.

Additional info:
Considering above bug, does that mean one cannot use RHEL7 box to fix Fedora packages? I mean just module checkout, apply changes, push them, build the fedora package.