• Bug#1104000: unblock: pymupdf/1.25.4+ds1-3

    From Johannes Schauer Marin Rodrigues@21:1/5 to All on Wed Apr 23 21:20:01 2025
    XPost: linux.debian.devel.release

    Package: release.debian.org
    Severity: normal
    User: release.debian.org@packages.debian.org
    Usertags: unblock
    X-Debbugs-Cc: pymupdf@packages.debian.org, bage@debian.org
    Control: affects -1 + src:pymupdf

    Please unblock package pymupdf

    [ Reason ]

    pymupdf was removed from testing because of this bug: #1100748 Together
    with the pymupdf maintainer we figured out that this was actually a
    problem that needed fixing in src:mupdf. The correct fix got uploaded
    yesterday and the fixed src:mupdf should transition to testing in 10
    days. Bastian Germann uploaded a new version of src:pymupdf yesterday as
    well which was built with the new src:mupdf and in contrast to before,
    all its autopkgtests complete now. Since pymupdf was part of oldstable
    and stable, Sebastian Ramacher told me in #debian-release that this made
    it eligible for an exception to make it still transition to testing and
    be part of Trixie as well.

    [ Impact ]

    src:pymupdf has exactly one reverse dependency in unstable: my package
    plakativ which was removed from testing as pymupdf was removed from
    testing. If the unblock request for pymupdf is not granted, then Trixie
    would also be released without plakativ (has low popcon of ~74). If the
    unblock request for pymupdf is granted, I'd need one for plakativ as
    well. :)

    [ Tests ]

    I reported the original issue in #1100748 and I debugged this problem
    together with upstream in https://github.com/pymupdf/PyMuPDF/issues/4390
    I built the fixed src:mupdf and src:pymupdf and ran its autopkgtest
    locally. The autopkgtest was failing before. Now it passes both locally
    as well as on ci.debian.net.

    [ Risks ]

    The code change happpened in src:mupdf and not in src:pymupdf. src:mupdf
    will probably transition to testing fine because it never got removed.
    The changes in src:pymupdf are only affecting test cases and the
    addition of a versioned dependency to require the fixed version of
    mupdf. The src:pymupdf package itself did not change behaviour except
    that it now does not segfault anymore thanks to patched src:mupdf. Risk
    is also low because src:pymupdf only has a single reverse dependency: my package plakativ.

    [ Checklist ]
    [*] all changes are documented in the d/changelog
    [*] I reviewed all changes and I approve them
    [ ] attach debdiff against the package in testing

    No debdiff because pymupdf got removed from testing.

    unblock pymupdf/1.25.4+ds1-3

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)