--WVf18ZLo9bznw8Mz
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 04/14 13:17, Nir Soffer wrote:
On Thu, Apr 14, 2016 at 12:55 PM, Vinzenz Feenstra
<vfeenstr(a)redhat.com> =
wrote:
>
>> On Apr 14, 2016, at 11:52 AM, Nir Soffer <nsoffer(a)redhat.com> wrote:
>>
>> On Thu, Apr 14, 2016 at 12:23 PM, David Caro <dcaro(a)redhat.com> wrote:
>>> On 04/14 12:06, Dan Kenigsberg wrote:
>>>> On Thu, Apr 14, 2016 at 11:56:10AM +0300, Dan Kenigsberg wrote:
>>>>>
>>>>> I've added the package it check-patch.packages, but not to
>>>>> build-artifacts.packages. should be fixed in a minutes. Sorry.
>>>>
>>>> Actually, it's not that, as build-artifacts.packages is a softlink
>>>>
>>>> build-artifacts.packages.fc23 -> check-merged.packages.fc23
>>>>
>>>> despite that,
>>>>
>>>>
http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc23-x86_64=
/823/consoleText
>>>>
>>>> mock \
>>>>
--configdir=3D"/home/jenkins/workspace/vdsm_master_build-arti=
facts-fc23-x86_64/vdsm" \
>>>>
--root=3D"mocker-fedora-23-x86_64.fc23" \
>>>> --install "autoconf automake git lago lago-ovirt
libguestfs-t=
ools-c m2crypto make mom policycoreutils-python pyflakes python-blivet
pyth=
on-coverage python-devel python-inotify python-ioprocess python-netaddr pyt=
hon-nose python-pep8 python-pthreading python-rtslib python-six python3-nos=
e python3-six rpm-build sudo yum yum-utils grubby" \
>>>>
--resultdir=3D"logs/mocker-fedora-23-x86_64.fc23.install_pack=
ages"
>>>>
>>>> does not list python3-netaddr. Any idea why?
>>>
>>> That package is not in the packages list of the check-merged.packages=
=2Efc23 file
>>> for that patch:
>>
>> We have single place for build requirements - vdsm.spec. How about
>> using yum builddep to
>> install dependencies instead of duplicating the data?
>
> That=E2=80=99s not really feasible, since we are generating vdsm.spec d=
uring
the run of configure, then again configure requires some packages to =
be available=E2=80=A6.
> Not really the best of ideas
=20
Suggest a better way?
Maybe you should try to avoid generating the spec? at least, not the
'buildrequires' section? (so it would be usable to extract the requirements
even if some sections of it will be changed later by autotools/make/whateve=
r)
=20
Nir
=20
>
>>
>> Keeping multiple requirements lists is not maintainable.
>>
>> Nir
>> _______________________________________________
>> Devel mailing list
>> Devel(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/devel
>
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web:
www.redhat.com
RHT Global #: 82-62605
--WVf18ZLo9bznw8Mz
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJXD26uAAoJEEBxx+HSYmnDYn0IAJzLnpFXeOxdudUs9I/6IQc9
fmgRwzViLCxPQkYDr/TIat4hZUnnim7s+sKllAMfd2kRSxqCm1jKSwoSBpnrECUA
/dTW7CC2LDrHEDsULHyNgCTLdcNLGe6BRWSgU26GMU7Qw5R2Brh0lYqtiP/Iv8JW
lJfpRFTHO2hYlRdiM6GWGpNF2SZ1geIHO+nr6zqxIdZi0bx6GAAe6JQIu8SiIhF7
CR9ebBzf9BSQ07WIqqXkXVmijK+gewICuug6vxv13Dvi8W6Gx1opF5T59gcZaQxE
5QSSWYcVDOPh/mXnq21oliSayEQLvVoK3AJpQrNrVk+CNXUQqVOVKHdZym5Nha0=
=gPFD
-----END PGP SIGNATURE-----
--WVf18ZLo9bznw8Mz--