Your message dated Fri, 18 Feb 2022 21:05:46 +0000
with message-id <[email protected]>
and subject line Bug#1005766: fixed in pikepdf 5.0.0+dfsg-1
has caused the Debian Bug report #1005766,
regarding alert to upstream bug report on pikepdf test failures
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.)


-- 
1005766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005766
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pikepdf
Version: 4.2.0+dfsg-1
X-Debbugs-CC: [email protected]

The current version of pikepdf has some failed tests that are preventing qpdf 
10.6.1 from transitioning. I just wanted to make you aware of this upstream bug 
report: https://github.com/pikepdf/pikepdf/issues/303

Short version: qpdf 10.6 fixed a character encoding bug for a few obscure 
characters. This changed qpdf's response to some calls that were being made in 
pikepdf's tests. A fix to pikepdf is forthcoming that will adjust the error 
handling behavior based on a runtime check, but in the meantime, the failures 
are not actually a regression but are instead tests that are failing because 
they were relying on incorrect qpdf behavior.

I'm hoping a new pikepdf version will come out with this fix soon so just 
uploading a new pikepdf will unblock the qpdf transition. Since debian 
maintenance of pikepdf has generally been very responsive, I won't plan on 
creating another issue about it unless you would like to say something when 
pikepdf is updated. Thanks!

--- End Message ---
--- Begin Message ---
Source: pikepdf
Source-Version: 5.0.0+dfsg-1
Done: Sean Whitton <[email protected]>

We believe that the bug you reported is fixed in the latest version of
pikepdf, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton <[email protected]> (supplier of updated pikepdf 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 [email protected])


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

Format: 1.8
Date: Fri, 18 Feb 2022 13:13:43 -0700
Source: pikepdf
Architecture: source
Version: 5.0.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Sean Whitton <[email protected]>
Closes: 1005766
Changes:
 pikepdf (5.0.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1005766).
   * Refresh patches.
   * Add build-deps qpdf 10.6.2, python3-sphinx-panels, python3-packaging.
Checksums-Sha1:
 ac375b11750d7aa546826f99e248f6d371f855e1 2660 pikepdf_5.0.0+dfsg-1.dsc
 cc69e698d9b1fed2412989fa02b4244ca1b470da 2146304 pikepdf_5.0.0+dfsg.orig.tar.xz
 209202cb81d05f7ab3b04ca73db10591658c7fe0 1926592 
pikepdf_5.0.0+dfsg-1.debian.tar.xz
Checksums-Sha256:
 2ca6ac55eb0c234289fc2c4d4194d92a594b05962812a0ea4e52a296cf9d02fb 2660 
pikepdf_5.0.0+dfsg-1.dsc
 7296068e41ae558636ea9e01ad41823d2c9046f4cabadd29c70ea6a4f99e65c4 2146304 
pikepdf_5.0.0+dfsg.orig.tar.xz
 24cfa6a798d5939ef29dbf08a393f3b8d0c23bccad676913b4f620119684e4b8 1926592 
pikepdf_5.0.0+dfsg-1.debian.tar.xz
Files:
 4956084b34a3df3f4f26c6e4082e75f4 2660 python optional pikepdf_5.0.0+dfsg-1.dsc
 07cbc06e051e987b64eb1c3ffcb10a10 2146304 python optional 
pikepdf_5.0.0+dfsg.orig.tar.xz
 428844bff6ba6213636b0ce73bf8b595 1926592 python optional 
pikepdf_5.0.0+dfsg-1.debian.tar.xz

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

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmIP/hIACgkQaVt65L8G
YkCLDQ/7BaB5C8XVP6pFsMG7Cshs0r482CDNugFX5T4pFeYoM3c2O/XBsto4dssu
Q3AITQd5/QRMVdTiKoS8gU7Gk5t6Glb9njLnItg2PruSsIG00mb+1TMcAGQZThSm
/0D99b47UFosYXpgXVJoZK0cT3bfvN2oPU0k/L/wROcNnk0gYe8Ulmltki3at8Ra
rCxHSkNcFla2CQQWzGmZ7019X2YdCtrb5RvxNwAFFmvENAK+mJ1j9y80Tez4/7n4
NXXhj6etxsvUd62bnV+0BP2s0DkkDjAedJ18N9B45WiO0w4qZ76DbiYqYc8jVWQY
O2DfLabWsy3djnko7W6Q73S+xSviZ/9PQn9Umx8daCv4Q7uHlh8JYD4PQeYLCMad
CZpNFaywggibGbqkzv+9vHe4Q66f6kAhbniv9mxnZNZOfDsCQN3EnDPPX9nZnkFb
pQgfAGtoyJfxDFHEYYwbgO0otWnCcVB6xLVX3iTfwwc1zX2tkphg6ftiFQ3mMKM4
HsrycFGX1DiNvK4+Ba+z32/VvEEzItJ5UQm4tjQFgAz0snAfj7CdZLI7bFKEt57O
0UIwEef3ydrqvlclBjaOp0tYVkfN570GLBPhPmyxbsKcqa+Ae6YGS4LzHqzh1nHL
Y1q3BSF0XJPSkqSeEOfwGQOzgTi6bWa+2vg44Zcfmdmsk5o3YhE=
=qnVT
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to