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:
spec file created by rpmdev-newspec can not be validated by spectool. It used to work with previous rpmdevtools packages in previous RHEL versions. Now spectools throws away a traceback.
Version-Release number of selected component (if applicable):
rpmdevtools-9.3-7.el9
How reproducible:
always
Steps to Reproduce:
# rpmdev-newspec new.spec
new.spec created; type minimal, rpm version >= 4.16.
# spectool new.spec
error: line 2: Empty tag: Version:
Traceback (most recent call last):
File "/usr/bin/spectool", line 524, in <module>
exit(main())
File "/usr/bin/spectool", line 449, in main
spec = Spec(path)
File "/usr/bin/spectool", line 286, in __init__
self.spec = rpm.spec(self.path)
ValueError: can't parse specfile
# echo $?
1
Actual results:
Traceback with "ValueError: can't parse specfile" and exit code 1.
Expected results:
This is how it works on RHEL-8:
# rpmdev-newspec new.spec
new.spec created; type minimal, rpm version >= 4.14.
# spectool new.spec
# echo $?
0
# rpm -q rpmdevtools
rpmdevtools-8.10-8.el8.noarch
The bug is actually backwards. The template spec created by "rpmdev-newspec new.spec" is *nowhere near* a valid spec, so current spectool is right to error out on it and the actual bug is that in older versions, spectool did not complain on this very incomplete spec.
Description of problem: spec file created by rpmdev-newspec can not be validated by spectool. It used to work with previous rpmdevtools packages in previous RHEL versions. Now spectools throws away a traceback. Version-Release number of selected component (if applicable): rpmdevtools-9.3-7.el9 How reproducible: always Steps to Reproduce: # rpmdev-newspec new.spec new.spec created; type minimal, rpm version >= 4.16. # spectool new.spec error: line 2: Empty tag: Version: Traceback (most recent call last): File "/usr/bin/spectool", line 524, in <module> exit(main()) File "/usr/bin/spectool", line 449, in main spec = Spec(path) File "/usr/bin/spectool", line 286, in __init__ self.spec = rpm.spec(self.path) ValueError: can't parse specfile # echo $? 1 Actual results: Traceback with "ValueError: can't parse specfile" and exit code 1. Expected results: This is how it works on RHEL-8: # rpmdev-newspec new.spec new.spec created; type minimal, rpm version >= 4.14. # spectool new.spec # echo $? 0 # rpm -q rpmdevtools rpmdevtools-8.10-8.el8.noarch