Your message dated Wed, 17 Jun 2026 08:34:33 +0000
with message-id <[email protected]>
and subject line Bug#1140172: fixed in python-reportlab 4.5.1-2
has caused the Debian Bug report #1140172,
regarding src:python-reportlab: fails to migrate to testing for too long
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.)
--
1140172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140172
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-reportlab
Version: 4.4.10-1
Severity: serious
Control: close -1 4.5.1-1
Tags: sid forky
User: [email protected]
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing and
unstable for more than 30 days as having a Release Critical bug in testing [1].
Your package src:python-reportlab has been trying to migrate for 31 days [2],
hence this bug report. The current output of the migration software for this
package is copied to the bottom of this report and should list the reason why
the package is blocked.
If a package is out of sync between unstable and testing for a longer period,
this usually means that bugs in the package in testing cannot be fixed via
unstable. Blocked packages can have impact on other packages, which makes
preparing for the release more difficult. The situation that caused this bug
report might even be the result of such an issue. We expect maintainers to fix
issues that hamper the migration of their package in a timely manner. If your
package in this situation due to another package, consider helping out.
This bug will trigger auto-removal when appropriate. As with all new bugs,
there will be at least 30 days before the package is auto-removed.
This bug submission immediately closes the bug with the version in unstable, so
if that version or a later version migrates, this bug will no longer affect
testing. This bug is also tagged to only affect sid and forky, so it doesn't
affect (old-)stable.
If you believe your package is unable to migrate to testing due to issues
beyond your control, don't hesitate to contact the Release Team.
This bug report has been automatically generated. If you have any comments with
regards to the content or the process, please reach out to me.
Paul
[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=python-reportlab
Current text from [2]:
Migration status for python-reportlab (4.4.10-1 to 4.5.1-1): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Autopkgtest for python-reportlab/4.5.1-1: amd64: Pass, arm64: Pass, i386:
Pass, loong64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression ♻
(reference ♻)
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/p/python-reportlab.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 30 days old (needed 5 days)
--- End Message ---
--- Begin Message ---
Source: python-reportlab
Source-Version: 4.5.1-2
Done: Georges Khaznadar <[email protected]>
We believe that the bug you reported is fixed in the latest version of
python-reportlab, 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.
Georges Khaznadar <[email protected]> (supplier of updated python-reportlab
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: Wed, 17 Jun 2026 10:02:23 +0200
Source: python-reportlab
Architecture: source
Version: 4.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar <[email protected]>
Changed-By: Georges Khaznadar <[email protected]>
Closes: 1140172
Changes:
python-reportlab (4.5.1-2) unstable; urgency=medium
.
* modified the patch d/patches/don-t-use-Microsoft-fonts.patch in order
to skip out one test on s390x platforms where it fails with
Symbol font. Closes: #1140172
Checksums-Sha1:
645ff43f3f71adac32e32c59735b4ca0ccbbcfc1 2240 python-reportlab_4.5.1-2.dsc
847729bcff605ff092f542f32ae88c4c8d29953e 24440
python-reportlab_4.5.1-2.debian.tar.xz
9a5b82b8ca11b4c2347a9c696f2225ee21b64957 8988
python-reportlab_4.5.1-2_source.buildinfo
Checksums-Sha256:
d5c3377de0ae7a1172ad592f4d7ef1562fc31b82d802f8a61570148ed9251771 2240
python-reportlab_4.5.1-2.dsc
35202ad181ae95d7a9ef261199942d749bb0d46a2d20ede55769398ab53addb7 24440
python-reportlab_4.5.1-2.debian.tar.xz
c07727d74298565248b247f068af1b3e529f9a2980c3e8d588c78e3c13433fd1 8988
python-reportlab_4.5.1-2_source.buildinfo
Files:
3e8566c92bf91b17bc77c5c124b80121 2240 python optional
python-reportlab_4.5.1-2.dsc
346a46169f72f76824e568076d6c6558 24440 python optional
python-reportlab_4.5.1-2.debian.tar.xz
c9e102390acdd061c33b9cf8ab4e304a 8988 python optional
python-reportlab_4.5.1-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmoyVpIUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmbeBAAqAsNP3A2lXbyU8U0ms+cfjH0sfMl
IrEwgj5aBTOSvlC/J0XL1suVXMthSRbo4Or18OPOi9wlv1gH07hF4H88MOd1s+Vl
BRiMtPkl/OGy+xdmntjXkdxpIWE4LqpyRR2Am0359kDOW2ASlhGxrMaAEDGzz3Vx
fYP11HoxXLP+bJ2ZjGIL9HX27ba5Z5DJNVOGhMOR3PXcplUcD21mmjL+ymkH2FlF
WtLNOI1hmBZFpp/ZM9xolxpJ6tdLkuGgorUGwxl3i8n+qHXpUaHhazaDkODiTso1
aNv6Y2F/VgTkGwovrQgJ8ZBMH7FbCje1GuaUmsrMwNCIxZaZrKte8OdrgFLgkTfe
5PfTT63FXdcUpqUB6MKEUhGBNoQV/p8rGYFJ3c8ryQHEUhyM5EdiSgGNNHOkVVUS
JIq/9yCLbIscTcX2LekFKc/065sNYkBZtJ+Jqh8/3ZG0dPu0xvAoGRpBwRHPUbVn
aAR0qwLj0pYQNE2u+Nzg9wcadW3zCxDOHdvsTmBjmCt90X5Fc8przMXTA7523rLr
LZNg8EhbnK1ARcmcq79pOAM2rbIC96pzsMKD27x9fXwV63V1uUKFvXyDe5ELJAVD
p61K4VBWIazlUcpDmW4tyJrGvUpM9B1XA6rfWTZBwOiiMaESJdyJFf3TwZHC2OZ3
xD7MWx7WEZ2W4BQ=
=4RbW
-----END PGP SIGNATURE-----
pgpeTP318ltTY.pgp
Description: PGP signature
--- End Message ---
