Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mupdf: 1.16.1 -> 1.17.0 #87238

wants to merge 1 commit into from

mupdf: 1.16.1 -> 1.17.0 #87238

wants to merge 1 commit into from


Copy link

r-ryantm commented May 8, 2020

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from

meta.description for mupdf is: "Lightweight PDF, XPS, and E-book viewer and toolkit written in portable C"

meta.homepage for mupdf is: ""

Updates performed
  • Version update
To inspect upstream changes
Checks done (click to expand)

Rebuild report (if merged into master) (click to expand)
41 total rebuild path(s)

13 package rebuild(s)

13 x86_64-linux rebuild(s)
13 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
13 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
Instructions to test this update (click to expand)

Either download from Cachix:

nix-store -r /nix/store/i8x001kg06f2q4pw1a8xkz058yya2i9c-mupdf-1.17.0-bin \
  --option binary-caches '' \
  --option trusted-public-keys '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A mupdf

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/i8x001kg06f2q4pw1a8xkz058yya2i9c-mupdf-1.17.0-bin
ls -la /nix/store/i8x001kg06f2q4pw1a8xkz058yya2i9c-mupdf-1.17.0-bin/bin

Security vulnerability report
Security report (click to expand)

CVEs resolved by this update:

CVEs introduced by this update:

CVEs present in both versions:

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

Result of nixpkgs-review 1

6 packages failed to build:
- llpp
- python27Packages.pymupdf
- python37Packages.pymupdf
- python38Packages.pymupdf
- termpdfpy
- zathura
7 packages built:
- cups-filters (cups_filters)
- jfbpdf
- jfbview
- k2pdfopt
- mupdf
- splix
- system-config-printer (system_config_printer)

Maintainer pings

cc @vrthra @fpletz for testing.

Copy link

wamserma commented May 8, 2020

Last status of llpp = Succeeded
Last status of python27Packages.pymupdf = Succeeded
Last status of python37Packages.pymupdf = Succeeded
Last status of python38Packages.pymupdf = Succeeded
Last status of termpdfpy = Succeeded
Last status of zathura = Succeeded

On release-20.03 and trunk-combined.

Copy link

wamserma commented May 8, 2020

The build errors are indeed relatable to the mupdf-update.
This update of mupdf brings a huge change of the (internal) API, thereby breaking the depending packages. Updates of these packages should be synchronized with this PR as soon as they are available from upstream.

Upstream issues:

Copy link

wamserma commented Jun 6, 2020

Closed by #88919

@r-ryantm r-ryantm closed this Jun 11, 2020
@r-ryantm r-ryantm deleted the r-ryantm:auto-update/mupdf branch Jun 11, 2020
@ryantm ryantm restored the r-ryantm:auto-update/mupdf branch Jun 11, 2020
@ryantm ryantm deleted the r-ryantm:auto-update/mupdf branch Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.