[EPEL-devel] Re: Broken %python_provide macro for Koji's epel8-playground target?
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 epel8-playground > branch? There is no such rule, but in my opinion, it is welcomed for exactly the terrible experience anybody gets when he tries to use epel8-playground. The purpose of epel8-playground is to diverge when needed. That's why the epel8 branch contains package.cfg by default. -- Petr signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
[EPEL-devel] Re: Broken %python_provide macro for Koji's epel8-playground target?
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@lists.fedoraproject.org/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@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
[EPEL-devel] Re: Broken %python_provide macro for Koji's epel8-playground target?
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@lists.fedoraproject.org/message/WRXXXFNG2E6TIKXR43RUS526KQNUK3V6/ Might this be relevant? python-rpm-macros come from RHEL, not EPEL, in 8. No idea what's wrong. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
[EPEL-devel] Re: Broken %python_provide macro for Koji's epel8-playground target?
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 epel8-playground is fetching python-rpm-macros-3-38, while
my Mock is using 3-37, but if the CentOS AppStream build is comparable
to the RHEL build, the only difference is this:
❯ diff -ru 37 38
diff -ru 37/usr/lib/rpm/macros.d/macros.python
38/usr/lib/rpm/macros.d/macros.python
--- 37/usr/lib/rpm/macros.d/macros.python 2020-04-29
19:49:02.558205301 -0700
+++ 38/usr/lib/rpm/macros.d/macros.python 2020-04-29
19:49:13.547141007 -0700
@@ -5,7 +5,7 @@
# the macro
%py_build() %{expand:\\\
CFLAGS="${CFLAGS:-${RPM_OPT_FLAGS}}"
LDFLAGS="${LDFLAGS:-${RPM_LD_FLAGS}}"\\\
- %{__python} %{py_setup} %{?py_setup_args} build
--executable="%{__python2} %{py_shbang_opts}" %{?*}
+ %{__python} %{py_setup} %{?py_setup_args} build
--executable="%{__python} %{py_shbang_opts}" %{?*}
sleep 1
}
Intrigued,
--
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@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
