On Tue, Nov 12, 2019 at 5:05 AM Miro Hrončok <mhroncok(a)redhat.com> wrote:
On 12. 11. 19 7:52, Mike DePaulo wrote:
> Hi everyone,
>
> Background:
> The Pulp 3 upstream project is written in Python 3.
> Our installer normally uses PyPI for pure python packages, and OS
> packages for C libraries & their python bindings.
>
> Problem:
> With RHEL7/CentOS7, we often run into the following thorny situation:
> - Package libjuicy, written in C, exists in EL7 (main, optional, or extras).
> - Subpackage python2-libjuicy with python2 bindings exists in EL7.
> - Subpackage python3-libjuicy does not exist at all for EL7.
>
> Note: libjuicy is a made up name :)
If you post the actual libraries, I would bring that up with my team (Python
Maint @ Red Hat).
I'm mostly certain this is only this one we strictly "need" right now:
libcomps
We might need this in the future:
dnf
This would be helpful, but the current EL7 version is too old for
Pulp's needs (and we currently have a workaround: a C-compiling
package on PyPI [1] [2]):
createrepo_c
- Mike
[1]
https://pypi.org/project/createrepo-c/
[2]
https://github.com/rpm-software-management/createrepo_c/pull/103
>
> > I am not sure how to provide the python3 bindings .
> >
> > Solutions I've thought of:
> >
> > 1. I see that for pure python packages ("chardet" being an example I
> > stumbled upon), there's often a python2 package in EL7, but a python3
> > package in EPEL7. Often at different versions. And I found guidelines
> > for this. [1]
> >
> > However, I am worried about robustness (& feasibility) of a
> > python3-libjuicy bindings-only source package in EPEL7 for an EL7
> > libjuicy. What if there's a libjuicy update and it breaks the bindings
> > until we (Pulp / Fedora contributors) update them? And would it be
> > permissible in EPEL 7?
>
> You would need to be ready to update the package every time it updates in EL.
> That is usually not very often.
>
> It would be permissible. See for example:
>
>
https://src.fedoraproject.org/rpms/python3-rpm
>
> > 3. We can request that RHEL7 provides an updated libjuicy with the
> > python3-libjuicy subpackage.
> >
> > However, even if they say yes, it would take too long for upstream
> > release schedule.
>
> Also note that RHEL 7 is slowly getting to a phase where feature request might
> end up being denied. Here is a potentially successful one, but it already took
> half a year:
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=1719978
>
> > Suggestions?
> >
> > BTW, thank you for all the hard work on EPEL7 Python 3 support. I've
> > been following the RHEL 7.7 situation.
>
> Thanks for the kind words!
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> _______________________________________________
> epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-leave(a)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.fedoraproj...