Bug 1526627 - Python 3.4 python-dns is not available in EPEL 7
Summary: Python 3.4 python-dns is not available in EPEL 7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-dns
Version: epel7
Hardware: noarch
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Avram Lubkin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-15 21:58 UTC by Matt Lewandowsky
Modified: 2018-01-25 10:38 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-01-25 10:38:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matt Lewandowsky 2017-12-15 21:58:56 UTC
Description of problem:
Python 3 python-dns is only available in Fedora builds, which is inconvenient for EPEL 7 users.

Version-Release number of selected component (if applicable): Not directly applicable.


How reproducible:
Always

Steps to Reproduce:
1. # yum install python3-dns

Actual results:
==> No package python3-dns available.

Expected results:
Package is available and installs.

Additional info:
This commit added EPEL 7 support: https://src.fedoraproject.org/rpms/python-dns/c/be10c570adf03d9246cc0cf0e07f53cf402d90ca?branch=master
However, according to https://apps.fedoraproject.org/packages/python-dns an EPEL 7 package was never built.

Comment 1 Avram Lubkin 2017-12-15 23:19:10 UTC
I agree there should be a package, and the python-dns SRPM will build a python34 package for EPEL since it was my intent to support it.

The problem is the python-dns package already exists in RHEL and the SRPM name of an EPEL package can't match the name of a RHEL package. The SRPM name must also match the Fedora project name.

So, essentially, this never got deployed because no one cared enough to create and maintain a python3-dns project which only supported el7. I had been trying to get the infrastructure to be more flexible, but that was an uphill battle and I was busy with other things. It's possible things are easier to change with the new infrastructure, but I'm not sure.

Comment 2 Matt Lewandowsky 2017-12-16 00:11:48 UTC
Is my best bet at this juncture to locally build the package and deploy it using my internal infrastructure?

As a rule, I prefer to bug maintainers if it looks like it should be provided by a distro (or EPEL or its ilk), as that benefits more people for approximately the same amount of total work. :)

Comment 3 Avram Lubkin 2017-12-16 00:57:57 UTC
Actually, it's a lot more work, which I thought I explained clearly above. You're always welcome to volunteer your time to help out.

If you want it now, then yes, build it from the srpm, it's one command, rpmbuild --rebuild, or use mock. You should be able to use the SRPM for the fedora package.

I did request a new package in Bug 1526662, but it will take some time.

I also created an issue with the infrastructure folks to add better support for this in the future. I didn't get very far the last time I tried, but maybe they will be more interested this time around.

Comment 4 Fedora Update System 2018-01-10 05:56:36 UTC
python3-dns-1.15.0-7.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-72b2cdeba8

Comment 5 Fedora Update System 2018-01-10 14:07:48 UTC
python3-dns-1.15.0-7.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-72b2cdeba8

Comment 6 Fedora Update System 2018-01-25 10:38:54 UTC
python3-dns-1.15.0-7.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.