Why is `pymupdf` pinned with `<1.26.6`?

[doronbehar]

On NixOS, we tested the build of svgdigitizer 0.14.0 and had no failures with pymupdf 1.26.6 .

https://github.com/echemdb/svgdigitizer/blob/da0159a6eef9fc1bc4aee04759c16cdcaf2d375b/ChangeLog#L45

[linuxrider]

There was some errors with v1.26.6 pymupdf when installing. I don't remember excactly. I relaxed the constraint again and the only thing now failing is our nix flake workflow for macos.

[linuxrider]

https://github.com/echemdb/svgdigitizer/actions/runs/19527751303/job/55903848090

[doronbehar]

Indeed it fails on Hydra too:

https://cache.nixos.org/log/bi8yy93j9bz4zn49lbgx60wn000krwkb-python3.13-pymupdf-1.26.6.drv

I relaxed the constraint again and the only thing now failing is our nix flake workflow for macos.

We'd like to fetchpatch the commit that does this and not use pythonRelaxDeps. Could you maybe link me to this commit?

[linuxrider]

https://github.com/echemdb/svgdigitizer/commit/0189a81c1d1390dfad6671dedda0251d3028685f

[doronbehar]

Thanks. Should we wait for a patch release or fetchpatch it?

[DunklesArchipel]

Thanks for reaching out. V.0.14.1 should be available from pypi. The conda-forge release will take up to 24 h. Hope this fixes the issue.