Your message dated Sun, 01 Jun 2025 17:58:22 +0000
with message-id <[email protected]>
and subject line Bug#1106720: Removed package(s) from unstable
has caused the Debian Bug report #1029732,
regarding pypdf2 is deprecated, please move from python3-pypdf2 to python3-pypdf
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 [email protected]
immediately.)
--
1029732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029732
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:pypdf2
Severity: wishlist
Control: affects -1 src:pypdf
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11
Control: reassign -2 bookletimposer
Control: reassign -3 kraft
Control: reassign -4 krop
Control: reassign -5 odoo-14
Control: reassign -6 orangeassassin
Control: reassign -7 pdfposter
Control: reassign -8 python3-xhtml2pdf
Control: reassign -9 tryton-modules-stock-package-shipping-dpd
Control: reassign -10 diffoscope
Control: reassign -11 diffoscope-minimal
Control: block -1 by -2 -3 -4 -5 -6 -7 -8 -9 -10 -11
As noted in https://bugs.debian.org/1028559, upstream for the PyPDF2
Python module has moved to the "pypdf" namespace.
Correspondingly, there is a new python3-pypdf package in debian
unstable.
The packages listed above all currently depend on (or recommend) PyPDF2,
but probably should move to the updated version. When all these bug
reports are closed, we can consider removing the pypdf2 source package
and python3-pypdf2 from debian.
The migration should be relatively straightforward; much of the API
remains the same, just under the "pypdf" module name instead of the
"PyPDF2" module name. Where the API differs, the version of PyPDF2
currently in debian testing/unstable (2.12.1-3) emits a
PendingDeprecationWarning wherever a piece of the API will break.
For example:
foo.py:76: PendingDeprecationWarning: getObject is deprecated and will be
removed in PyPDF2 3.0.0. Use get_object instead.
(PyPDF2 version 3.x is basically a terminal version of PyPDF2, and pypdf
takes over from 3.1.x onward; PyPDF2 version 3.x will not enter debian,
as it is an API break from 2.x, and pypdf 3.x supercedes it)
To transition a given package:
- run tests with as complete coverage as possible and note the
PendingDeprecation warnings
- for each warning, patch the upstream line as recommended
- ensure that the tests pass without PendingDeprecationWarnings
- convert from "PyPDF2" to "pypdf" on any import or scoped reference in
python
- update dependency indicators in upstream metadata annotations
(e.g. pyproject.toml, setup.cfg, etc)
- update dependency indicators in debian packaging (from python3-pypdf2
to python3-pypdf).
- run the tests again
Please send any upstream fixes back upstream as well, of course!
Regards,
--dkg
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2.12.1-4+rm
Dear submitter,
as the package pypdf2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1106720
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
