On Wed, Oct 9, 2019 at 5:33 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
>
> On 09. 10. 19 4:34, Nico Kadel-Garcia wrote:
> > On Tue, Oct 8, 2019 at 1:56 PM Irina Boverman <iboverma@xxxxxxxxxx> wrote:
> >>
> >> Using "BuildRequires: python%{python3_pkgversion}-devel" results in this error:
> >>
> >> fedpkg scratch-build
> >> DEBUG util.py:593: No matching package to install: 'python36-devel'
> >
> > A lot of Fedora .spec files use "python3-devel" and various "pyton3-"
> > modules. If you switch this to "python%{python3_pkgversion}-", *AND*
> > if you add "BuildRequires: epel-rpm-mocros" for rhel based
> > environments, it works much better to play nicely with the new RHEL
> > and the existing EPEL packages.
>
> Why do you need to add "BuildRequires: epel-rpm-mocros"?
It's going to be a while before EPEL gets all of the "python36"
labeled packages rebuilt to say "Provides: python3-module" as well as
"Provides: python36-module" for complete consistency with the altered
name used by RHEL. The epel-rpm-macros package sets the python modules
to set "python3_pkgversion" to be "36" instead of plain "3", and helps
find and resolve the python dependencies from the slightly older EPEL
versions. It also helps distinguish new built modules as being EPEL
based instead of merely RHEL or CentOS based.
I'm not happy that RHEL upstream selected to use "python3" instead of
"python36" as the package name for their release of Python 3.6. Like
modularity, it's solving one problem but generating others.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
