Bug 2008855

Summary: F36FailsToInstall: python3-spyder-kernels
Product: [Fedora] Fedora Reporter: Mamoru TASAKA <mtasaka>
Component: python-spyder-kernelsAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-29 11:15:31 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:
Bug Depends On:    
Bug Blocks: 1992487    

Description Mamoru TASAKA 2021-09-29 11:10:09 UTC 
Description of problem:
Currently python3-spyder-5.1.5-1.fc36 FailsToInstall on F-36:

 Problem: conflicting requests
  - package python3-spyder-5.1.5-1.fc36.noarch requires (python3.10dist(spyder-kernels) < 2.2 with python3.10dist(spyder-kernels) >= 2.1.1), but none of the providers can be installed
  - nothing provides (python3.10dist(jupyter-client) < 7 with python3.10dist(jupyter-client) >= 5.3.4) needed by python3-spyder-kernels-1:2.1.1-1.fc36.noarch


Version-Release number of selected component (if applicable):
python3-spyder-5.1.5-1.fc36

How reproducible:
100%

Additional info:
This currently blocks Fedora-Astronomy_KDE-Live and Fedora-Scientific_KDE-Live
https://koji.fedoraproject.org/koji/taskinfo?taskID=76454150
https://koji.fedoraproject.org/koji/taskinfo?taskID=76454280

Recently python-jupyter-client is updated to 7.0.3:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1836157
Comment 1 Mamoru TASAKA 2021-09-29 11:13:22 UTC 
Oops... This bug should be against python-spyder-kernels. Reassigning.
Comment 2 Mamoru TASAKA 2021-09-29 11:15:31 UTC 
... And this is already reported.

*** This bug has been marked as a duplicate of bug 2007627 ***