Bug 2397792

Summary: zathura-0.5.14 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: zathuraAssignee: Alain V. <alain.vigne.14>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: alain.vigne.14, mjg, moceap, psabata, sanjay.ankur
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: zathura-0.5.14-1.fc44 zathura-0.5.14-1.fc43 zathura-0.5.14-1.fc42 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-10-30 11:57:37 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.5.13 (#2397792)
none
Update to 0.5.14 (#2397792) none

Description Upstream Release Monitoring 2025-09-24 13:13:32 UTC
Releases retrieved: 0.5.13
Upstream release that is considered latest: 0.5.13
Current version/release in rawhide: 0.5.12-1.fc44
URL: http://pwmt.org/projects/zathura/download/

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/5298/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/zathura

Comment 1 Upstream Release Monitoring 2025-09-24 13:13:41 UTC
Created attachment 2107468 [details]
Update to 0.5.13 (#2397792)

Comment 2 Upstream Release Monitoring 2025-09-24 15:47:39 UTC
the-new-hotness/release-monitoring.org's scratch build of zathura-0.5.13-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=137440172

Comment 3 Upstream Release Monitoring 2025-10-27 21:22:46 UTC
Releases retrieved: 0.5.14
Upstream release that is considered latest: 0.5.14
Current version/release in rawhide: 0.5.12-1.fc44
URL: http://pwmt.org/projects/zathura/download/

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/5298/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/zathura

Comment 4 Upstream Release Monitoring 2025-10-27 21:22:52 UTC
Created attachment 2111054 [details]
Update to 0.5.14 (#2397792)

Comment 5 Upstream Release Monitoring 2025-10-27 21:32:19 UTC
the-new-hotness/release-monitoring.org's scratch build of zathura-0.5.14-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=138494399

Comment 6 Fedora Update System 2025-10-30 11:54:36 UTC
FEDORA-2025-70cd77b1f4 (zathura-0.5.14-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-70cd77b1f4

Comment 7 Fedora Update System 2025-10-30 11:57:37 UTC
FEDORA-2025-70cd77b1f4 (zathura-0.5.14-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-10-30 12:17:56 UTC
FEDORA-2025-e0bcc52f39 (zathura-0.5.14-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e0bcc52f39

Comment 9 Fedora Update System 2025-10-30 12:30:37 UTC
FEDORA-2025-5a1a2f0773 (zathura-0.5.14-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5a1a2f0773

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

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

Comment 11 Fedora Update System 2025-10-31 01:42:26 UTC
FEDORA-2025-e0bcc52f39 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-e0bcc52f39`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e0bcc52f39

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

Comment 12 Fedora Update System 2025-11-08 01:06:53 UTC
FEDORA-2025-e0bcc52f39 (zathura-0.5.14-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2025-11-08 01:28:05 UTC
FEDORA-2025-5a1a2f0773 (zathura-0.5.14-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.