Bug 2186919

Technically, this depends on the mupdf update.

I'll prepare copr test builds in https://copr.fedorainfracloud.org/coprs/mjg/python-PyMuPDF/ (and https://copr.fedorainfracloud.org/coprs/mjg/zathura-pdf-mupdf/) before setting up a side-tag for us. Might want to go with rawhide only for now and let F38 settle in first (though it's looking absolutely painless), dunno ;)

OK, it builds, but big caveat:

There are a new test suite failures in test_default_font, test_font and test_colour_count.

This can get missed easily since Sandro suppressed the test suite outcome unconditionally. The core dump on s390x is still there and masks the other tests.

So we will have to look at this update more closely, it seems.

Releases retrieved: 1.22.1
Upstream release that is considered latest: 1.22.1
Current version/release in rawhide: 1.21.1-6.fc39
URL: https://github.com/pymupdf/PyMuPDF

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


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

(In reply to Michael J Gruber from comment #2)
> This can get missed easily since Sandro suppressed the test suite outcome
> unconditionally. The core dump on s390x is still there and masks the other
> tests.

Perhaps for a slightly better solution, we could just disable the tests on s390x for now?

Yes, that makes sense when the suite passes ...

I have a fix for the failing font test (due to different bundled fonts), and I'm discussing the jpg test failure with upstream. It seems to be due to different decoding results (libjpeg vs libjpeg-turbo): https://github.com/pymupdf/PyMuPDF/issues/2347

Releases retrieved: 1.22.2
Upstream release that is considered latest: 1.22.2
Current version/release in rawhide: 1.21.1-6.fc39
URL: https://github.com/pymupdf/PyMuPDF

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


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

Releases retrieved: 1.22.3
Upstream release that is considered latest: 1.22.3
Current version/release in rawhide: 1.21.1-6.fc39
URL: https://github.com/pymupdf/PyMuPDF

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


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

FEDORA-2023-a2375e1571 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a2375e1571

FEDORA-2023-a2375e1571 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2023-a5815ceafb has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a5815ceafb

FEDORA-2023-a5815ceafb 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-a5815ceafb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a5815ceafb

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

FEDORA-2023-b8a2c3b01f has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b8a2c3b01f

FEDORA-2023-b8a2c3b01f has been pushed to the Fedora 37 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-b8a2c3b01f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b8a2c3b01f

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

FEDORA-2023-a5815ceafb has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2023-b8a2c3b01f has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.