Bug 2352660

Summary: mupdf-1.26.3 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: mupdfAssignee: Michael J Gruber <mjg>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: lizhenbo, mjg
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mupdf-1.26.3-2.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-07-07 21:08:46 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:

Description Upstream Release Monitoring 2025-03-15 01:11:00 UTC
Releases retrieved: 1.25.5
Upstream release that is considered latest: 1.25.5
Current version/release in rawhide: 1.25.4-1.fc43
URL: http://mupdf.com

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


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

Comment 1 Michael J Gruber 2025-03-15 21:16:24 UTC
ABI unchanged but SONAME bumped, so this will need to go into a side-tag with rebuilds of dependencies.

Comment 2 Upstream Release Monitoring 2025-03-31 20:17:36 UTC
Releases retrieved: 1.25.6
Upstream release that is considered latest: 1.25.6
Current version/release in rawhide: 1.25.4-1.fc43
URL: http://mupdf.com

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


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

Comment 3 Upstream Release Monitoring 2025-05-13 04:44:10 UTC
Releases retrieved: 1.26.0
Upstream release that is considered latest: 1.26.0
Current version/release in rawhide: 1.25.4-1.fc43
URL: http://mupdf.com

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


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

Comment 4 Michael J Gruber 2025-05-14 07:12:09 UTC
While mupdf 1.26.0 builds in fedora in principle, it makes a test fail in PyMuPDF which hints at a problem in mupdf rather than PyMuPDF or its test. Known and reported upstream. 1.26.x series will have to wait for a fix.

Comment 5 Upstream Release Monitoring 2025-05-20 14:39:49 UTC
Releases retrieved: 1.26.1
Upstream release that is considered latest: 1.26.1
Current version/release in rawhide: 1.25.4-1.fc43
URL: http://mupdf.com

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


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

Comment 6 Michael J Gruber 2025-05-21 12:07:32 UTC
While mupdf 1.26.1 fixes the issue mentioned in comment #4, there is no fully compatible PyMuPDF release yet. So this will be on hold a bit longer.

Comment 7 Upstream Release Monitoring 2025-06-03 15:25:08 UTC
Releases retrieved: 1.26.2
Upstream release that is considered latest: 1.26.2
Current version/release in rawhide: 1.25.4-1.fc43
URL: http://mupdf.com

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


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

Comment 8 Upstream Release Monitoring 2025-06-29 04:31:24 UTC
Releases retrieved: 1.26.3
Upstream release that is considered latest: 1.26.3
Current version/release in rawhide: 1.25.4-3.fc43
URL: http://mupdf.com

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


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

Comment 9 Fedora Update System 2025-07-07 21:05:11 UTC
FEDORA-2025-4eb0f03805 (mupdf-1.26.3-2.fc43, python-PyMuPDF-1.26.3-2.fc43, and 2 more) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4eb0f03805

Comment 10 Fedora Update System 2025-07-07 21:08:46 UTC
FEDORA-2025-4eb0f03805 (mupdf-1.26.3-2.fc43, python-PyMuPDF-1.26.3-2.fc43, and 2 more) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.