chore: update pyMuPDF dependency #77

mahlzahn commented 2026年01月14日 14:40:27 +01:00

(削除) Currently, 1.25.5 is pinned from 2025年03月31日. Would be great to use latest version 1.26.7 (2025年11月05日), (削除ここまで) which also includes newer version of MuPDF. See https://pymupdf.readthedocs.io/en/latest/changes.html

Edit: now, on version 1.27.1, see censor/Censor!79.

Only needs to change https://codeberg.org/censor/Censor/src/branch/main/python3-pymupdf.json, build and manual testing and possibly fixes, if the used API changed.

Optimally, the dependency is semi-automatically (ci? renovate?) updated on new releases.

~Currently, 1.25.5 is pinned from 2025年03月31日. Would be great to use latest version 1.26.7 (2025年11月05日),~ which also includes newer version of MuPDF. See https://pymupdf.readthedocs.io/en/latest/changes.html Edit: now, on version 1.27.1, see censor/Censor!79. Only needs to change https://codeberg.org/censor/Censor/src/branch/main/python3-pymupdf.json, build and manual testing and possibly fixes, if the used API changed. Optimally, the dependency is semi-automatically (ci? renovate?) updated on new releases.

martin762green commented 2026年02月23日 13:57:12 +01:00

Apologies if this is the incorrect place to add my comment.
I have taken the latest pyMuPDF version 1.27.1 and added the apppropriate URL's to the above file and used flatpak builder to build and install an updated flatpak on my host. I have used both a aarch64 (raspberrypi) and x86_64 (desktop/server) using ubuntu OS in both cases).

I am unable to test ms windows and macos.

I had no errors and the application appears to work correctly in both linux cases.
I appreciate that this is the easy bit (good learning curve for building flatpaks and own repository). Should I raise a pull request?

The part two about semi-automatically updating the dependency is beyond me at present but I will persevere.
cheers, Martin

Apologies if this is the incorrect place to add my comment. I have taken the latest pyMuPDF version 1.27.1 and added the apppropriate URL's to the above file and used flatpak builder to build and install an updated flatpak on my host. I have used both a aarch64 (raspberrypi) and x86_64 (desktop/server) using ubuntu OS in both cases). I am unable to test ms windows and macos. I had no errors and the application appears to work correctly in both linux cases. I appreciate that this is the easy bit (good learning curve for building flatpaks and own repository). Should I raise a pull request? The part two about semi-automatically updating the dependency is beyond me at present but I will persevere. cheers, Martin

mahlzahn commented 2026年02月23日 14:51:45 +01:00

Hi @martin762green,

I am unable to test ms windows and macos.

I think flatpak is only supported by Linux, thus no need to worry here.

Should I raise a pull request?

I'd appreciate that!

The part two about semi-automatically updating the dependency is beyond me at present

No need to have this done, now.

Hi @martin762green, > I am unable to test ms windows and macos. I think flatpak is only supported by Linux, thus no need to worry here. > Should I raise a pull request? I'd appreciate that! > The part two about semi-automatically updating the dependency is beyond me at present No need to have this done, now.

martin762green commented 2026年02月23日 15:34:00 +01:00

Ha! Brainstorm concerning the non Linux cmment.
I don't sem to have permission to raise a PR (P button hot highlighted). I am probably missing some preliminaries
M

Ha! Brainstorm concerning the non Linux cmment. I don't sem to have permission to raise a PR (P button hot highlighted). I am probably missing some preliminaries M

mahlzahn commented 2026年02月23日 16:12:43 +01:00

If you want to edit the files within Forgejo, you need to clone the repo first and then edit the file and propose the PR. Cloning is only not needed if the AGit workflow is used directly from the command line.

If you want to edit the files within Forgejo, you need to [clone the repo first and then edit the file and propose the PR](https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/). Cloning is only not needed if the [AGit workflow](https://forgejo.org/docs/latest/user/agit-support/) is used directly from the command line.