I have come upon a problem building python packages.
The upstream spec file I am using makes heavy use of %py2_build macro which causes builds to fail in cbs because
this macro is provided by python2-rpm-macros. That macro is in EPEL and not available for cbs builds.
Should I just replace py2_build with its expansion as found in
python2-rpm-macros?
--TFH
On 04/09/17 23:20, Thomas F Herbert wrote:
I have come upon a problem building python packages.
The upstream spec file I am using makes heavy use of %py2_build macro which causes builds to fail in cbs because
this macro is provided by python2-rpm-macros. That macro is in EPEL and not available for cbs builds.
Should I just replace py2_build with its expansion as found in
python2-rpm-macros?
--TFH
-- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat*
If you need a specific pkg to always be in the buildroots, you can create a ticket on https://bugs.centos.org so that Thomas (or someone else) can add it in the pkgs manifests for that tag/target. IIRC RDO already uses their own macros (https://cbs.centos.org/koji/packageinfo?packageID=1873)
Thanks.
I added local python build macros to the spec file for now.
I have question below though.
On 09/05/2017 01:43 AM, Fabian Arrotin wrote:
On 04/09/17 23:20, Thomas F Herbert wrote:
I have come upon a problem building python packages.
The upstream spec file I am using makes heavy use of %py2_build macro which causes builds to fail in cbs because
this macro is provided by python2-rpm-macros. That macro is in EPEL and not available for cbs builds.
Should I just replace py2_build with its expansion as found in
python2-rpm-macros?
--TFH
-- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat*
If you need a specific pkg to always be in the buildroots, you can create a ticket on https://bugs.centos.org so that Thomas (or someone else) can add it in the pkgs manifests for that tag/target. IIRC RDO already uses their own macros (https://cbs.centos.org/koji/packageinfo?packageID=1873)
Is this also the best solution for testing build with several other packages on which we have dependencies but plan to add in NFV SIG?
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Fabian Arrotin -
Thomas F Herbert