Bug 1213356 - Attempted update update through KDE Discover, system software updates and zypper dup failes because of python incompatibility
Summary: Attempted update update through KDE Discover, system software updates and zyp...
Status: RESOLVED DUPLICATE of bug 1210671
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Applications (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-15 01:52 UTC by John Stathopoulos
Modified: 2023-07-15 10:54 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Stathopoulos 2023-07-15 01:52:10 UTC 
<html>Dependency resolution failed:<br/><br/>the to be installed python310-jupyter-events-0.6.3-3.1.noarch requires &apos;(python310-jsonschema-format-nongpl &gt;= 3.2.0 with python310-jsonschema-format-nongpl &lt; 4.18)&apos;, but this requirement cannot be provided
the to be installed python310-nbformat-5.9.0-2.1.noarch requires &apos;(python310-jsonschema &gt; 2.6 with python310-jsonschema &lt; 4.18)&apos;, but this requirement cannot be provided
the to be installed python311-jupyter-events-0.6.3-3.1.noarch requires &apos;(python311-jsonschema-format-nongpl &gt;= 3.2.0 with python311-jsonschema-format-nongpl &lt; 4.18)&apos;, but this requirement cannot be provided
the to be installed python311-nbformat-5.9.0-2.1.noarch requires &apos;(python311-jsonschema &gt; 2.6 with python311-jsonschema &lt; 4.18)&apos;, but this requirement cannot be provided</html>
Comment 1 Andreas Stieger 2023-07-15 10:54:30 UTC 
You keep reporting the same user issue without any reflection, self-service or steps to reproduce. If any random message had exactly one solution that always works we would just make that the default:

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