No description
Find a file
2025-08-14 13:12:45 +02:00
LICENSES Update REUSE.toml 2025-08-01 01:08:43 +02:00
.nvchecker.toml upgpkg: 1.24.11-1: New upstream release 2024-11-19 09:56:21 +01:00
.SRCINFO Add 'unzip' as missing dep 2025-08-14 13:12:45 +02:00
LICENSE License package as 0BSD 2025-07-26 12:33:10 +02:00
mupdf-1.23.9-cpp_ldflags.patch upgpkg: 1.24.8-1: New upstream release 2024-07-25 10:21:44 +02:00
mupdf-1.23.9-install_targets.patch upgpkg: 1.26.0-1: New upstream release 2025-05-13 20:19:50 +02:00
mupdf.desktop * new upstream release 2017-12-13 16:11:13 +00:00
mupdf.pc upgpkg: 1.24.2-2 Add mupdf.pc file in the libmupdf package 2024-05-28 19:39:05 +02:00
mupdf.xpm new upstream release 2014-06-13 18:25:58 +00:00
PKGBUILD Add 'unzip' as missing dep 2025-08-14 13:12:45 +02:00
README.md Update README 2025-05-13 20:20:46 +02:00
REUSE.toml Update REUSE.toml 2025-08-01 01:08:43 +02:00

mupdf

Soname bump on new upstream releases

Each new upstream release includes a soname bump in libmupdf (which is a part of this mupdf split package).
You can run sogrep on the built libmupdf package to identify the list of packages to rebuilb against it (e.g. for repo in core extra; do for lib in $(find-libprovides libmupdf-1.24.8-1-x86_64.pkg.tar.zst | sed 's/=.*//g'); do sogrep -r $repo $lib; done; done | sort | uniq).

Creating ToDos to track those rebuilds (in staging) is encouraged. For instance: https://archlinux.org/todo/mupdf-1248-rebuild/

PS: It happens sometimes that upstream do not sync mupdf and (python-)pymupdf releases, creating some incompatibilities between them. See the python-pymupdf package README for more details.