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:
https://bodhi.fedoraproject.org/overrides/epel-rpm-macros-8-10
There has been no sync to playground since. See
https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/WRXXXFNG2E6TIKXR43RUS526KQNUK3V6/
Might this be relevant? python-rpm-macros come from RHEL, not EPEL, in
8. No idea what's wrong.
I'm not sure, I'll try and compare the two root.log more closely, thanks.
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 epel8-playground branch? This whole deep dive started when one
of my package didn't build in playground, and tracing its missing
dependencies I'm noticing more packages where the epel8 branch is
somehow fully synced with master and so never contains package.cfg and
never builds for epel8-playground...
--
Michel Alexandre Salim
profile: https://keybase.io/michel_slm
chat via email: https://delta.chat/
GPG key: 96A7 A6ED FB4D 2113 4056 3257 CAF9 AD10 ACB1 BEF2
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
