Re: [ovirt-devel] Introduce new package decencies in vdsm

2016-11-17 Thread Barak Korren
On 16 November 2016 at 12:31, Martin Sivak wrote: > I agree, the spec file should be the ultimate source of truth. The > question is if our automation supports that. > You can certainly use yum-builddep in the automation scripts. Engine does:

Re: [ovirt-devel] Introduce new package decencies in vdsm

2016-11-16 Thread Yaniv Bronheim
On Wed, Nov 16, 2016 at 4:56 PM, Nir Soffer wrote: > On Wed, Nov 16, 2016 at 9:35 AM, Yaniv Bronheim > wrote: > > Hi > > > > After merging > > https://gerrit.ovirt.org/#/q/status:open+project:vdsm+ > branch:master+topic:cross-imports > > This is not

Re: [ovirt-devel] Introduce new package decencies in vdsm

2016-11-16 Thread Nir Soffer
On Wed, Nov 16, 2016 at 9:35 AM, Yaniv Bronheim wrote: > Hi > > After merging > https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:cross-imports This is not related to this patch, we had to keep correct spec, automation and dockerfile before this

Re: [ovirt-devel] Introduce new package decencies in vdsm

2016-11-16 Thread Martin Sivak
I agree, the spec file should be the ultimate source of truth. The question is if our automation supports that. Martin On Wed, Nov 16, 2016 at 8:35 AM, Yaniv Bronheim wrote: > Hi > > After merging >

[ovirt-devel] Introduce new package decencies in vdsm

2016-11-15 Thread Yaniv Bronheim
Hi After merging https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:cross-imports we need now for any new requirement to add a line in: check-patch.packages.el7 check-patch.packages.fc24 check-merged.packages.el7 check-merged.packages.fc24 vdsm.spec.in Dockerfile.centos