Bug 1885139

Summary: nothing provides python3.6dist(pyasn1) >= 0.4.6 needed by python3-ldap3-2.8.1-1.el8.noarch
Product: [Fedora] Fedora EPEL Reporter: Thomas Oulevey <thomas.oulevey>
Component: python-ldap3Assignee: Avram Lubkin <aviso>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel8CC: aviso, igor.raits, karlthered, matt, m.cyprian, mhroncok, python-sig
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ldap3-2.8.1-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-09 15:00:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thomas Oulevey 2020-10-05 08:36:25 UTC
Description of problem:

$ yum install python3-ldap3

fails with 

Error: 
 Problem: conflicting requests
  - nothing provides python3.6dist(pyasn1) >= 0.4.6 needed by python3-ldap3-2.8.1-1.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

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


How reproducible: always


Steps to Reproduce:
1. yum install python3-ldap3

Actual results:
nothing provides python3.6dist(pyasn1) >= 0.4.6 needed by python3-ldap3-2.8.1-1.el8.noarch

Expected results:
python3-ldap3 installs fine.

Comment 1 Avram Lubkin 2020-10-05 12:30:13 UTC
Looks like the requirements file changed in 2.7 though they started testing against pyasn 0.4.6 with 2.6.1.
pyasn is include with RHEL and is pinned to 0.3.7, so I think the best course is to add an epel8 branch to the python3-pyasn1 repo and provide it as an alternative to the base one. I've requested that here.
https://pagure.io/releng/fedora-scm-requests/issue/29362

Comment 2 Miro Hrončok 2020-10-05 12:59:15 UTC
That unfortunately is against the EPEL policy:


https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy_for_Conflicting_Packages

Comment 3 Avram Lubkin 2020-10-05 13:36:19 UTC
Miro, how do you recommend resolving it?

Comment 4 Miro Hrončok 2020-10-05 13:51:01 UTC
There are several ways:

a) downgrade ldap3 to a version that is installable

b) figure out why ldap3 2.8 requires new pyasn1 and request a backport of that feature / fix (or drop the limit, if it is artifitial)

Note that even with b), you might need to do a) before the backport happens.

Comment 5 Thomas Oulevey 2020-10-05 13:52:54 UTC
yes p[ease do a)

Comment 6 Fedora Update System 2020-10-05 22:47:50 UTC
FEDORA-EPEL-2020-1f361092e3 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1f361092e3

Comment 7 Avram Lubkin 2020-10-05 22:59:15 UTC
Limit seems artificial. Upstream started testing against 0.4.6 with 2.6.1 which didn't raise any issues and that's been in the repo for a year. The improvements in pyasn1 are primarily bug fixes and additional features.

Hopefully some volunteers will test their specific use case against this release and provide feedback.

https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1f361092e3

Comment 8 Fedora Update System 2020-10-06 01:06:48 UTC
FEDORA-EPEL-2020-1f361092e3 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1f361092e3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2020-10-09 15:00:27 UTC
FEDORA-EPEL-2020-1f361092e3 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.