Bug 2245360

Summary: kobo-0.32.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: koboAssignee: Lukáš Zaoral <lzaoral>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: daniel.mach, kdudka, lzaoral, rohan, svashisht
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kobo-0.32.0-1.fc40 kobo-0.32.0-1.el9 kobo-0.32.0-1.el8 kobo-0.32.0-1.fc39 kobo-0.32.0-1.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-23 09:58:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Update to 0.32.0 (#2245360) none

Description Upstream Release Monitoring 2023-10-20 23:45:22 UTC 
Releases retrieved: 0.32.0
Upstream release that is considered latest: 0.32.0
Current version/release in rawhide: 0.31.0-1.fc40
URL: https://github.com/release-engineering/kobo

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/12359/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/kobo
Comment 1 Upstream Release Monitoring 2023-10-20 23:45:28 UTC 
Created attachment 1994912 [details]
Update to 0.32.0 (#2245360)
Comment 2 Upstream Release Monitoring 2023-10-20 23:50:23 UTC 
the-new-hotness/release-monitoring.org's scratch build of kobo-0.32.0-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=107848912
Comment 3 Fedora Update System 2023-10-23 08:08:02 UTC 
FEDORA-2023-aec40b57a3 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-aec40b57a3
Comment 4 Fedora Update System 2023-10-23 08:15:36 UTC 
FEDORA-EPEL-2023-8368219f21 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8368219f21
Comment 5 Fedora Update System 2023-10-23 08:15:36 UTC 
FEDORA-2023-d15842c4f3 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d15842c4f3
Comment 6 Fedora Update System 2023-10-23 08:15:38 UTC 
FEDORA-2023-a9f2d4c388 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a9f2d4c388
Comment 7 Fedora Update System 2023-10-23 08:15:38 UTC 
FEDORA-EPEL-2023-c31e3eec97 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c31e3eec97
Comment 8 Fedora Update System 2023-10-23 09:58:14 UTC 
FEDORA-2023-aec40b57a3 has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 9 Fedora Update System 2023-10-24 02:24:07 UTC 
FEDORA-2023-a9f2d4c388 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a9f2d4c388`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a9f2d4c388

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 10 Fedora Update System 2023-10-24 02:30:54 UTC 
FEDORA-EPEL-2023-8368219f21 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8368219f21

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 11 Fedora Update System 2023-10-24 02:40:09 UTC 
FEDORA-EPEL-2023-c31e3eec97 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c31e3eec97

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 12 Fedora Update System 2023-10-24 02:40:22 UTC 
FEDORA-2023-d15842c4f3 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d15842c4f3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d15842c4f3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 13 Fedora Update System 2023-11-01 01:51:44 UTC 
FEDORA-EPEL-2023-8368219f21 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 14 Fedora Update System 2023-11-01 02:12:12 UTC 
FEDORA-EPEL-2023-c31e3eec97 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 15 Fedora Update System 2023-11-08 01:25:42 UTC 
FEDORA-2023-a9f2d4c388 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 16 Fedora Update System 2023-11-08 01:38:58 UTC 
FEDORA-2023-d15842c4f3 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.