Your message dated Wed, 23 Oct 2024 15:15:12 +0000
with message-id <e1t3d4q-00ep4v...@fasolo.debian.org>
and subject line Bug#1083225: fixed in odoo 17.0.0+dfsg2-1
has caused the Debian Bug report #1083225,
regarding odoo: Uses deprecated/to be removed PyPDF2
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.)


-- 
1083225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odoo
Version: 16.0.0+dfsg.2-2
Severity: wishlist

The odoo package has recently added a dependency on python3-pypdf2.  Last 
January the following bug was filed against all packages using python3-pypdf2:

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
 
I'm currently in the process of updating all these bugs with:

As we approach the first anniversary for this bug, an update:

I've recently adopted pypdf and pypdf2 into the Debian Python Team in response 
to an RFA for both packages.  As these are somewhat security sensitive packages 
(among my first acts after adopting the packages was to upload proposed updates 
for both to address minor security issues in Bookworm in the next point release 
- same bug in both), I do not think we should release pypdf2 in Trixie and have 
filed an RC bug to that effect.

If you want this package to be in Trixie, you will need to use pypdf instead of 
pypdf2.

Scott K

--- End Message ---
--- Begin Message ---
Source: odoo
Source-Version: 17.0.0+dfsg2-1
Done: Sebastien Delafond <s...@debian.org>

We believe that the bug you reported is fixed in the latest version of
odoo, 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 1083...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Delafond <s...@debian.org> (supplier of updated odoo 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: Wed, 23 Oct 2024 15:21:58 +0200
Source: odoo
Architecture: source
Version: 17.0.0+dfsg2-1
Distribution: unstable
Urgency: medium
Maintainer: Freexian Packaging Team <team+freex...@tracker.debian.org>
Changed-By: Sebastien Delafond <s...@debian.org>
Closes: 1064843 1083225
Changes:
 odoo (17.0.0+dfsg2-1) unstable; urgency=medium
 .
   [ Sébastien Delafond ]
   * Latest origin/17.0 release (Closes: #1083225)
   * README.Debian: describe `addons_path` (Closes: #1064843)
   * d/control: bump up Standards-Version
Checksums-Sha1:
 02a2330aa36de1db6586946d0b87b49c9ffcd3b6 1632 odoo_17.0.0+dfsg2-1.dsc
 2d5f428406e96dc80bfb43849a8da3e45a2ee88c 94780604 odoo_17.0.0+dfsg2.orig.tar.xz
 c3cc431e48611b555df0b6bbb75f8aa14f3bcf0e 21796 
odoo_17.0.0+dfsg2-1.debian.tar.xz
 82ec547755c53006e04321e98709a50357971309 6389 
odoo_17.0.0+dfsg2-1_source.buildinfo
Checksums-Sha256:
 c2645ee1772c25120ed9109fd0c42a4953dba4a53112ce824bcc69f9340482f0 1632 
odoo_17.0.0+dfsg2-1.dsc
 884eb4d82187a37259be451d411dd400a61a762c09cba026c648f6f6b237c617 94780604 
odoo_17.0.0+dfsg2.orig.tar.xz
 92d892b7e1c532479de5d4b6979b48fd47a4be1a7283072ad54707f713cd2fd4 21796 
odoo_17.0.0+dfsg2-1.debian.tar.xz
 88ee4779229fac970646fddc9ce937c08f87e20c27b3ab5d71302d5117f808dc 6389 
odoo_17.0.0+dfsg2-1_source.buildinfo
Files:
 534b72edb3337ab66d689f5b5f77c757 1632 net optional odoo_17.0.0+dfsg2-1.dsc
 e1c12a038d5ac30dd1938a9c76c6c1a9 94780604 net optional 
odoo_17.0.0+dfsg2.orig.tar.xz
 6f078a5598eed2ddc985658516f8eb7b 21796 net optional 
odoo_17.0.0+dfsg2-1.debian.tar.xz
 52165064172074948f5e05da358e441c 6389 net optional 
odoo_17.0.0+dfsg2-1_source.buildinfo

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

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAmcY/1MACgkQEL6Jg/PV
nWSBqgf/e59wAEYuwN1M1Qm+G1lBMCHyc0SYjKy9bJ8d9PzpXR37rEiXcaRz2IrF
LNTPxyNGJXzo7sGybzso9M75GeZG61TjiJf2vM8P8OUZe/MGgYJVBrZJm45fxrAV
7/ZswbQETsZL/brKcDSrfkeRjZsBGLl3z8noqcUeCFMXThH27tMNhbUVu9cfI0Le
dwkZhEA4SW6LX5/pnktDmIKKJ65zKYGa4ImiC6gZKBAfkjTFLsht1OrdF+e4W1XH
zeos3Z9U8jHFby4IajxBDWIyCDgZvR21l/C85sC6N58uO5HMVOCq4f4YVyjXf43c
sh/UdYGwDxq1i9mgHiWko0mSIANf6Q==
=owi7
-----END PGP SIGNATURE-----

Attachment: pgpnmyg0M2dfS.pgp
Description: PGP signature


--- End Message ---

Reply via email to