Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1899474
Summary: | python-asyncssh fails to build with Python 3.10: AssertionError: ValueError not raised | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomáš Hrnčiar <thrnciar> |
Component: | python-asyncssh | Assignee: | Georg Sauthoff <fedora> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | fedora, mhroncok, thrnciar |
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-01-26 22:26:02 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: | 1890881 |
Description
Tomáš Hrnčiar
2020-11-19 11:01:04 UTC
I've reported it upstream and the asyncssh author is investigating the root cause: https://github.com/ronf/asyncssh/issues/326 Two days ago, I pushed a new asyncssh version to rawhide that fixes the issue there. Thus, it should now work in your Copr python 3.10 branch, as well. I thought that a rebuild is automatically triggered in that branch, when a new package version is pushed, but this doesn't seem to have worked. it worked: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/python-asyncssh/ thanks Ok, I somehow expected that the build job would also update this issue then. Sorry, we don't have such automation. Sometimes, we build packages with tests disabled in that copr etc., so it would need to be very careful. |