Your message dated Mon, 05 Jan 2026 15:30:48 +0000
with message-id <[email protected]>
and subject line Bug#1121752: fixed in lumpy-sv 0.3.1+dfsg-8.1
has caused the Debian Bug report #1121752,
regarding src:lumpy-sv: 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.)
--
1121752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121752
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lumpy-sv
Version: 0.3.1+dfsg-7
Severity: serious
Control: close -1 0.3.1+dfsg-8
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:lumpy-sv 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.
Because I was surprised by the excuses, I dived a bit into it. The build
on s390x was prevented in the past by build-depending on python3-pysam,
but that B-D was dropped in the latest upload. So now there is an s390x
binary again, but it can't be installed. See bug #972935.
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. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or its
(reverse-)dependencies. We expect maintainers to fix issues that hamper
the migration of their package in a timely manner.
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 and has only been sent
manually. 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=lumpy-sv
Current text from [2]:
Migration status for lumpy-sv (0.3.1+dfsg-7 to 0.3.1+dfsg-8): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ lumpy-sv/s390x has unsatisfiable dependency
∙ ∙ Autopkgtest for lumpy-sv/0.3.1+dfsg-8: amd64: Pass, arm64: Pass,
i386: Pass, ppc64el: Pass, riscv64: Pass
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/l/lumpy-sv.html
∙ ∙ Autopkgtest skipped on s390x: not installable
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙
∙ 31 days old (needed 5 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: lumpy-sv
Source-Version: 0.3.1+dfsg-8.1
Done: Sudip Mukherjee <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lumpy-sv, 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.
Sudip Mukherjee <[email protected]> (supplier of updated lumpy-sv
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: Mon, 29 Dec 2025 14:15:32 +0000
Source: lumpy-sv
Architecture: source
Version: 0.3.1+dfsg-8.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
<[email protected]>
Changed-By: Sudip Mukherjee <[email protected]>
Closes: 1121752
Changes:
lumpy-sv (0.3.1+dfsg-8.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add B-D on python3-pysam (Closes: #1121752)
- lumpy-sv is uninstallable in s390x as python3-pysam is not available in
s390x. Add it back as B-D so that lumpy-sv is not built in s390x till
python3-pysam is fixed in s390x.
Checksums-Sha1:
3583415db75660ec4f322b22bb3f89e16b619bbe 2198 lumpy-sv_0.3.1+dfsg-8.1.dsc
05871e37ab7ec17de2e3d1fe5709abb380f1a050 39266984
lumpy-sv_0.3.1+dfsg-8.1.debian.tar.xz
9b241f2c79506657824b81b7922f6c36cd9cfe43 9169
lumpy-sv_0.3.1+dfsg-8.1_amd64.buildinfo
Checksums-Sha256:
c93817f65a87321ea6da888b6aa6d1d78aaa74df51e583fda558a6c2f463e71b 2198
lumpy-sv_0.3.1+dfsg-8.1.dsc
4d302e20a023158ea46bd565f6300c7dd096d2baa63f03207ad19d4d4d4beee5 39266984
lumpy-sv_0.3.1+dfsg-8.1.debian.tar.xz
63b2b679eb389f30dd71354b8925fa9f957140ebbae813f1ef176fea3ed77e46 9169
lumpy-sv_0.3.1+dfsg-8.1_amd64.buildinfo
Files:
16b2a01a34a498e90d4ce84fd4c66eb3 2198 science optional
lumpy-sv_0.3.1+dfsg-8.1.dsc
e145e2d486180bfc920c6c2235590b78 39266984 science optional
lumpy-sv_0.3.1+dfsg-8.1.debian.tar.xz
eb7fd7f3641605110b2cdd336d5df1c8 9169 science optional
lumpy-sv_0.3.1+dfsg-8.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAmlSkZUACgkQR5mjUUbR
KzXs4w/+JENejJQHqmNYZcZcmHYPFfvopoa9VvWG+XFboB/uRgEoZN/7GkTITcVm
9ire54PMwpUIgPg1eq5mRshLkU8qPGIu5+GQ3pes4tjqALOgtQ0nat08qnykq0r5
0Z2yqda6d0S98ooErZgVAH7xwbCqAYh42IwduNIT1jYkV95I1VzAgibu98ne9CLU
dn0ib2FjGT8od2R/0ipnXVizXfPlxiyVUK8Yug1GTIwHRhFme0n/a3c2ijWWaC3b
O719VNNPX2WulePGGcxtUKAl6VB+DGrHq0WgH63L+rIcVR9QTgIuM/AqRh3f2uld
bZYUyd9aIuNq/eZSKtR+6OMF38Mbs83XVmZQ2iYEqC0fq6ngSaDtC0Ei9Xd9zxUw
TtgXAhrmyjNowVWdMqoYUfSuuqonyRrl3QqGSURsbx9oxJY+swVox5KdgwjjKcCd
fgsXS8sy9EWmP4gc18TNrkils9eh9+IkxpCfbaoEllZfWSuYN3zcYDuzcBOOiqRE
o63n3KshD9lig8Toih6uUaxRDllnUWwKIae+U3KEUIyw9Ip948HOVeUHsLN9YJ9G
PLRR8eIe7SXjZOcX4XOcEdS6knGt1M/bFg1QzMD7Sb2HdVMNMk5WgLOxMfPC3YMy
dQFc2PHbsOZ+XtIf+pF7lSPLtpVNeuX/C6gnuNkSi/FDhjvXSAc=
=FmL1
-----END PGP SIGNATURE-----
pgpJ40kxqvATG.pgp
Description: PGP signature
--- End Message ---
