[EPEL-devel] Re: Broken %python_provide macro for Koji's epel8-playground target?

2020-05-01 Thread Petr Pisar
On Thu, Apr 30, 2020 at 12:32:26PM -0700, Michel Alexandre Salim wrote: > Generally speaking (I can make this a separate thread if that helps) - do we > expect every package in EPEL8 to also be built for EPEL8-playground, either > through package.cfg or by building directly from the

[EPEL-devel] Re: Broken %python_provide macro for Koji's epel8-playground target?

2020-04-30 Thread Michel Alexandre Salim
On 4/30/20 1:46 AM, Miro Hrončok wrote: On 30. 04. 20 3:58, Michel Alexandre Salim wrote: Is the epel8-playground builder somehow using an different version of python-rpm-macros? Happy to file a bug if I know where this should go. I have an active buildroot override for epel8 epel-rpm-macros:

[EPEL-devel] Re: Broken %python_provide macro for Koji's epel8-playground target?

2020-04-30 Thread Miro Hrončok
On 30. 04. 20 3:58, Michel Alexandre Salim wrote: Is the epel8-playground builder somehow using an different version of python-rpm-macros? Happy to file a bug if I know where this should go. I have an active buildroot override for epel8 epel-rpm-macros:

[EPEL-devel] Re: Broken %python_provide macro for Koji's epel8-playground target?

2020-04-29 Thread Michel Alexandre Salim
On 4/29/20 6:58 PM, Michel Alexandre Salim wrote: sh-4.4# rpm -q python-rpm-macros python-rpm-macros-3-37.el8.noarch ``` Is the epel8-playground builder somehow using an different version of python-rpm-macros? Happy to file a bug if I know where this should go. root.log says