Bug#1061265: rst2pdf: Uses deprecated/to be removed pypdf2
On January 22, 2024 10:11:50 AM UTC, Rob Allen wrote: >Hi, > >I’m the one of the leads on rst2pdf itself. > >Is there anything you want me to do related to this? > >Regards, > >Rob Thank you for being interested in its status in Debian. No. My understanding is that all this needs is for the maintainer in Debian to update the package to the most current release. The next Debian release is likely at least a year and a half from now, so there's plenty of time. Scott K
Bug#1061265: rst2pdf: Uses deprecated/to be removed pypdf2
Hi, I’m the one of the leads on rst2pdf itself. Is there anything you want me to do related to this? Regards, Rob > On 21 Jan 2024, at 18:19, Scott Kitterman wrote: > > Source: rst2pdf > Version: 0.99-1 > Severity: wishlist > > rst2pdf declares a requirement for python3-pypdf2 in > Build-Depends-Indep. > > 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. > > It looks like the current upstream release has already been ported to > use python3-pypdf (which is really pypdf3). Please update your package. > > Scott K >
Bug#1061265: rst2pdf: Uses deprecated/to be removed pypdf2
Source: rst2pdf Version: 0.99-1 Severity: wishlist rst2pdf declares a requirement for python3-pypdf2 in Build-Depends-Indep. 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. It looks like the current upstream release has already been ported to use python3-pypdf (which is really pypdf3). Please update your package. Scott K