Your message dated Fri, 13 Jul 2018 16:49:28 +0000
with message-id <e1fe1g4-000gbg...@fasolo.debian.org>
and subject line Bug#903627: fixed in ocrmypdf 6.2.2-1
has caused the Debian Bug report #903627,
regarding ocrmypdf: contains workaround for old version of python3-ruffus which 
should not be used with current python3-ruffus
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 ow...@bugs.debian.org
immediately.)


-- 
903627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ocrmypdf
Version: 6.2.0-1
Severity: serious
Tags: ftbfs
X-debbugs-cc: j...@purplerock.ca

OCRmyPDF contains a workaround for a bug in python3-ruffus <=2.6.3 that
upstream reports should not be used with python3-ruffus >=2.7 (see
changelog entry for 4.1.2-1 upload).

python3-ruffus 2.7 was just uploaded to Debian, so ocrmypdf is now
buggy, and indeed unbuildable.

The current upstream release of OCRmyPDF, 7.0.0, will not be reaching
Debian unstable for some time: a new dependency, pikepdf, will target
experimental.  So ideally we would patch the workaround out of OCRmyPDF
6.2.0.  CCing upstream to request advice on how to do this.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: ocrmypdf
Source-Version: 6.2.2-1

We believe that the bug you reported is fixed in the latest version of
ocrmypdf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton <spwhit...@spwhitton.name> (supplier of updated ocrmypdf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 13 Jul 2018 17:28:42 +0100
Source: ocrmypdf
Binary: ocrmypdf ocrmypdf-doc
Architecture: source
Version: 6.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton <spwhit...@spwhitton.name>
Changed-By: Sean Whitton <spwhit...@spwhitton.name>
Description:
 ocrmypdf   - add an OCR text layer to PDF files
 ocrmypdf-doc - add an OCR text layer to PDF files - documentation
Closes: 903627
Changes:
 ocrmypdf (6.2.2-1) unstable; urgency=medium
 .
   * New upstream release.
   * Loosen {build-,}dependency on python3-ruffus (Closes: #903627).
Checksums-Sha1:
 06fff628b52a1c909b36ce42aefea5edd58650df 2458 ocrmypdf_6.2.2-1.dsc
 2f4644363b10b2320d42457811bbb18d3fdfbd52 18189560 ocrmypdf_6.2.2.orig.tar.xz
 367345830687fce9bdd5aa2fcafb8f92fc875317 27112 ocrmypdf_6.2.2-1.debian.tar.xz
Checksums-Sha256:
 9f289dbbd95e807aad0b6d3232eb2f8b1acbaea244329539d19c692a683d0907 2458 
ocrmypdf_6.2.2-1.dsc
 69ce28efc8f4b85eebb36155fb4ca575502eebb59c49609ac23917d8c81584a2 18189560 
ocrmypdf_6.2.2.orig.tar.xz
 35fdf4f01ffff16d05cac8474158eae665c70ed244c789804bc17ae2733a9685 27112 
ocrmypdf_6.2.2-1.debian.tar.xz
Files:
 8fa93167a75c6facefb6c8300fe89a37 2458 graphics optional ocrmypdf_6.2.2-1.dsc
 03f39c672f1f5f8f575456bc71751e3c 18189560 graphics optional 
ocrmypdf_6.2.2.orig.tar.xz
 ae5afd471b0baa470c7fe6c3de193b2b 27112 graphics optional 
ocrmypdf_6.2.2-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAltI014ACgkQaVt65L8G
YkC+QBAAt2UAr/Kcmtdm+jqSGUnZpV6Jy5XtKxBM22TG6iz5OMc268Z1EqMgUmi4
TVqXw8BykiaBz6rExoBpsl5DPkDJj3u11FkiZR+4WlxJXfoOD063RNPs7xLfdo40
q2Dib+tcogltfiGSjEaJHTu1V38mxF4Tdj1yfjN0mef+G4FBgJebWBJvzNhufxgD
Owp/qC7H/lt30uhpNHoTrix+qZvPKoS/PvnI/aTz+g7vHYrjH26JjWV9q2MD7Ii/
2LkQZPeVZ927EDCBFfSg6KJFjJdfKbjUmheVg8fYiK1qM2IkqLpV2J4BxOFH/ZtU
QZ8RADHqVhA+4vgKsc4Td/QDlFY5lz26NYdaGFFLDs+LSJoYUShCkzb+zY1uByGN
vPmMpxRCSqMQtETfsyitpwdHXmy0k+Rz2bBxOwmKFACrAYTbCo88GYYAQsWBSCey
Dtl/eR3sPB/kftc3AEojT2jioDqNxlwQBWMasbPI41YSNL0sGFfsdb0kkShtpCWK
FD2rjOJmW5MoQ3KhKsuqQs7XJ8sNGyf/Zab35YWUqapZyNhv4QagGXJtCsfhBSO3
llTp98kjkm+OaiZa/0cKERCF6dryG/FPIukWK2K/+tvQmFs3WyAC/nf5tz3SGPQg
q1XZVKmFZ9iUkKTNy4slQ+Go+7yCGHZhpN7bGOT4ABXoMoIEuhM=
=9WFA
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to