Bug 2012544 - Upgrade to cpmtools 2.21
Summary: Upgrade to cpmtools 2.21
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cpmtools
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lucian Langa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-10 07:24 UTC by Jacob Kroon
Modified: 2021-10-20 19:22 UTC (History)
1 user (show)

Fixed In Version: cpmtools-2.22-2.fc34
Clone Of:
Environment:
Last Closed: 2021-10-20 19:22:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jacob Kroon 2021-10-10 07:24:08 UTC 
cpmtools 2.20 is buggy in my setup, please upgrade to 2.21, which I have tested resolves the issues I have.
Comment 1 Lucian Langa 2021-10-12 13:17:55 UTC 
Actually I already have 2.22 in f35 so I'll merge that for f34, it has been available since January, however I do not know
why it hasn't made the release page. There is also 2.23 but still in snapshot.
I do not want to backport 2.21 only for a short period of time and it's already more than 1 year old.
Comment 2 Fedora Update System 2021-10-12 13:20:30 UTC 
FEDORA-2021-bb5744b0d9 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-bb5744b0d9
Comment 3 Fedora Update System 2021-10-12 23:44:17 UTC 
FEDORA-2021-bb5744b0d9 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-bb5744b0d9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-bb5744b0d9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2021-10-20 19:22:56 UTC 
FEDORA-2021-bb5744b0d9 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.