Bug 1530206

Summary: RPM packages are supposed to be built in %build
Product: Red Hat Enterprise Linux 7 Reporter: Dhiru Kholia <dkholia>
Component: libyamiAssignee: Josef Ridky <jridky>
Status: CLOSED ERRATA QA Contact: Leos Pol <lpol>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: kdudka, lpol, ovasik
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libyami-1.2.0-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 19:01:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dhiru Kholia 2018-01-02 09:14:56 UTC
Description of problem:

The libyami.spec file is missing a call to "make" in the %build section.

Here is a patch to fix this problem,

diff --git a/libyami.spec b/libyami.spec
index ca427c7..ab52331 100644
--- a/libyami.spec
+++ b/libyami.spec
@@ -24,6 +24,7 @@ autoreconf -vif

 %build
 %configure --disable-static
+make %{?_smp_mflags}


 %install


Actual results:

rpmbuild -bc libyami.spec builds nothing.


Additional info:

This flaw prevents the package from being automatically scanned by covscan.

This bug is similar to the following bugs,

https://bugzilla.redhat.com/708157
https://bugzilla.redhat.com/796114
https://bugzilla.redhat.com/1038268

This bug was diagnosed by kdudka too.

Comment 5 Kamil Dudka 2018-01-15 14:00:14 UTC
Thanks to all involved!  I can confirm that Covscan now works with this package.

Comment 6 Leos Pol 2018-02-15 09:48:36 UTC
$ rpm -i libyami-1.2.0-2.el7.src.rpm 
$ rpmbuild -bc rpmbuild/SPECS/libyami.spec 
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.4FnvGa
...
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.3M6f8l
...
+ exit 0

Comment 9 errata-xmlrpc 2018-04-10 19:01:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1022