rpmbuild should error and/or toss out EMPTY provides/requires/conflicts/obsoletes entries
Bug #637207 reported by
Jeff Johnson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
RPM |
New
|
Undecided
|
Unassigned | ||
CentOS |
Fix Released
|
Unknown
|
|||
Fedora |
Fix Released
|
Medium
|
Bug Description
tracker
tags: | added: deps rpm.org rpmbuild |
tags: |
added: autodeps removed: deps |
Changed in centos: | |
status: | Unknown → Confirmed |
Changed in centos: | |
status: | Confirmed → Fix Released |
Changed in fedora: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
To post a comment you must log in.
Description of problem:
RPM has empty Provides, i.e. a rpm provides with a name=""
Version-Release number of selected component (if applicable):
opal-3.4.2-1.fc10
How reproducible:
Package is wrong
Steps to Reproduce: 4.2-1.fc10. i386.rpm
1. rpm -qp --xml opal-3.
Actual results:
rpmTag name="Providename"> g726</string> gsm0610< /string>
<string/>
<string>
<string>
Expected results:
rpmTag name="Providename"> g726</string> gsm0610< /string>
<string>
<string>
Additional info:
Trying to add "Provides:" to a .spec causes a build error,
so it must be some automatic provides that has gone wrong.