Bug 2111382
Summary: | Transmission rpm not available for Fedora 36 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Didier G <didierg-divers> |
Component: | transmission | Assignee: | Gwyn Ciesla <gwync> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 36 | CC: | admiller, denis, gwync, helio, jspaleta, raghusiddarth |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | transmission-3.00-13.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-08-24 20:31:26 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: | 2021895 | ||
Bug Blocks: |
Description
Didier G
2022-07-27 08:16:17 UTC
This is due to a problem with transmission's use of insecure ciphers in openssl that are no longer available as of Fedora 36. I've been trying to get transmission's developers to release a new version that includes the changes they've made to fix this, to no avail so far. FEDORA-2022-740fc91db3 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-740fc91db3 FEDORA-2022-740fc91db3 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-740fc91db3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-740fc91db3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-740fc91db3 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |