Bug 2051843

Summary: Not compatible with python 3.10
Product: [Fedora] Fedora Reporter: Spike <SpikeFedora>
Component: condaAssignee: Zbigniew Jędrzejewski-Szmek <zbyszek>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: orion, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: conda-4.11.0-3.fc35 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-18 01:36:57 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 Spike 2022-02-08 07:35:23 UTC
Description of problem:
https://github.com/conda/conda/issues/10969

Version-Release number of selected component (if applicable):
conda-4.10.3-1.fc35.noarch

How reproducible:
Always

Additional info:
This seems to be fixed with conda 4.11.0 which has already landed in rawhide. There's no 4.11.0 build for Fedora 35 though which makes currently conda somewhat unusable.

Comment 1 Fedora Update System 2022-02-09 03:50:46 UTC
FEDORA-2022-f4a74ef332 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f4a74ef332

Comment 2 Fedora Update System 2022-02-10 02:56:42 UTC
FEDORA-2022-f4a74ef332 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-f4a74ef332`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f4a74ef332

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

Comment 3 Fedora Update System 2022-02-18 01:36:57 UTC
FEDORA-2022-f4a74ef332 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.