Your message dated Fri, 18 May 2018 15:41:21 -0700 with message-id <CAGOGP4TO1u9CmUAya9SO4ddGA84qrm+MxDA+26Akd4Z6_6s8Aw@mail.gmail.com> and subject line Re: Bug#894068: ocrmypdf: New dependency on PyMuPDF for v6.0.0 has caused the Debian Bug report #894068, regarding RFP: PyMuPDF -- python binding for mupdf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 894068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894068 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: ITP: PyMuPDF -- python binding for mupdf
- From: Mathieu Malaterre <malat@debian.org>
- Date: Thu, 20 Oct 2016 11:59:30 +0200
- Message-id: <CA+7wUsw1O3yaerxq_ct=RNaZOJCgipRyD=DYJBn-mUjaXH-Lwg@mail.gmail.com>
Package: wnpp Severity: wishlist * Package name : PyMuPDF Version : 1.9.2 Upstream Author : Ruikai Liu, Jorj X. McKie * URL : https://github.com/rk700/PyMuPDF * License : GPL Programming Lang: C Description : python binding for mupdf This is version 1.9.2 of PyMuPDF (formerly python-fitz), a Python binding which supports MuPDF 1.9a - "a lightweight PDF and XPS viewer". MuPDF can access files in PDF, XPS, OpenXPS and EPUB (e-book) formats, and it is known for its top performance and high rendering quality. With PyMuPDF you therefore can also access files with extensions *.pdf, *.xps, *.oxps or *.epub from your Python scripts. -- I'll package this under the python group.
--- End Message ---
--- Begin Message ---
- To: Sean Whitton <spwhitton@spwhitton.name>
- Cc: 894068-done@bugs.debian.org
- Subject: Re: Bug#894068: ocrmypdf: New dependency on PyMuPDF for v6.0.0
- From: James R Barlow <barlow.jim@gmail.com>
- Date: Fri, 18 May 2018 15:41:21 -0700
- Message-id: <CAGOGP4TO1u9CmUAya9SO4ddGA84qrm+MxDA+26Akd4Z6_6s8Aw@mail.gmail.com>
- In-reply-to: <874lkwi6zw.fsf@iris.silentflame.com>
- References: <152203828225.4958.13790203479010992138.reportbug@40b9c476321b> <87lgeeg2ug.fsf@iris.silentflame.com> <CAGOGP4TBF7vRX8eRhtqAqrujmWwe-pLYubJ=SHPhEuU5eh9P+A@mail.gmail.com> <87a7uufrty.fsf@iris.silentflame.com> <CAGOGP4TCOWYo_sZHwd5it4DaJgqxtjoDydyX=+tqMu0jCdfF9g@mail.gmail.com> <874lkwi6zw.fsf@iris.silentflame.com>
-JamesHi Sean,I ended up deciding to remove PyMuPDF (apart from optional tests in the test suite, anyway) from the next major release of ocrmypdf - I'll still need your support with some new dependencies, but I think I've found a solution that should more acceptable to Debian and will work better for me as well.On Sat, 31 Mar 2018 at 08:45 Sean Whitton <spwhitton@spwhitton.name> wrote:Hello,
On Sat, Mar 31 2018, James R Barlow wrote:
> Hello Sean,
>
> As promised ocrmypdf v6.1.2 makes pymupdf optional but recommended. My
> continuous integration tests check with and without pymupdf.
>
> The only major regression without pymupdf is that with all of:
> 1) an input file containing a mix of scanned and born digital files
> 2) --skip-text (not default)
> 3) --output-type pdf (not default)
> the output file can grow extremely large compared to the input. Past
> versions of ocrmypdf have had this issue for a long time, and now it will
> produce a warning.
>
> So it should be ready for Debian.
I will start working on the new packaging. Thank you for the new
release.
--
Sean Whitton
--- End Message ---