Your message dated Tue, 02 Jun 2026 18:33:45 +0000
with message-id <[email protected]>
and subject line Bug#1138651: fixed in pyshark 0.6-2
has caused the Debian Bug report #1138651,
regarding src:python-roborock: 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.)
--
1138651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1138651
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-roborock
Version: 4.17.2-1
Severity: serious
Control: close -1 5.14.0-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-roborock 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-roborock
Current text from [2]:
Migration status for python-roborock (4.17.2-1 to 5.14.0-1): BLOCKED: Cannot
migrate due to another item, which is blocked (please check which dependencies
are stuck)
Issues preventing migration:
∙ ∙ Depends: python-roborock pyshark (not considered)
∙ ∙ Invalidated by dependency
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/p/python-roborock.html
∙ ∙ Autopkgtest for python-roborock/5.14.0-1: amd64: Pass, arm64: Pass, i386:
Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ Required age reduced by 3 days because of autopkgtest
∙ ∙ 4 days old (needed 2 days)
--- End Message ---
--- Begin Message ---
Source: pyshark
Source-Version: 0.6-2
Done: Edward Betts <[email protected]>
We believe that the bug you reported is fixed in the latest version of
pyshark, 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.
Edward Betts <[email protected]> (supplier of updated pyshark 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: Tue, 02 Jun 2026 19:07:31 +0100
Source: pyshark
Architecture: source
Version: 0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Home Assistant Team <[email protected]>
Changed-By: Edward Betts <[email protected]>
Closes: 1138651
Changes:
pyshark (0.6-2) unstable; urgency=medium
.
* Skip test_iterate_empty_psml_capture during riscv64 autopkgtest.
The 2s multiprocessing timeout is too tight. (Closes: #1138651)
Checksums-Sha1:
12ed868d9a2e46324e58062347c8bbaacdc94b60 2508 pyshark_0.6-2.dsc
a8daf909e8616d1ae95f5ae5587d5c4fa181da99 5772 pyshark_0.6-2.debian.tar.xz
d6bc5e03d1409f6b71b1ef734710e7ff6cee0bfe 96876 pyshark_0.6-2.git.tar.xz
6acb81b5bcf8da4c8013b67dd72e9a44205f7926 17477 pyshark_0.6-2_source.buildinfo
Checksums-Sha256:
ae917391134b3f3d031db50fae7825e3670b6647a26a973d5b3b32e1cf5558cb 2508
pyshark_0.6-2.dsc
a42efa570f790c902347b4b5ae18294018730caa9d1290b7c3b5f66688646761 5772
pyshark_0.6-2.debian.tar.xz
aa4a8f29477e5430b8d68f1f2c67c7edcae4c4815deb424036d145fcaeecd920 96876
pyshark_0.6-2.git.tar.xz
d3e2ca8dfaffdc94c6d41f7f700558fa23d87141e4faca988dc6b9e50f8f0931 17477
pyshark_0.6-2_source.buildinfo
Files:
8dc3bf840a42cbd2834104f96bc92699 2508 python optional pyshark_0.6-2.dsc
0851f6c1416b8237374006ac463ead17 5772 python optional
pyshark_0.6-2.debian.tar.xz
e23dd93344bb4a3134233ba6596b25c5 96876 python None pyshark_0.6-2.git.tar.xz
25874699d75fe8542899ac51b60e2387 17477 python optional
pyshark_0.6-2_source.buildinfo
Git-Tag-Info: tag=9430196342ae7340e0f8d90376f00d44c2ef6eeb
fp=fb8acfa78c726089c38ad0269605a1098c63b92a
Git-Tag-Tagger: Edward Betts <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmofHdMACgkQYG0ITkaD
wHlpJxAAxzQQ6bE2u0uLYJtoqE8xojMrYj0hiTS1Npss0tsxuyJDye1Yudei8CR0
VRmCOs27Gj0WzhOOwi1ihbuy9QZ5RpPz9xIUkE6nE2UkSnXYMt1NMENVOYOrzGlW
hgmJCSWtWt+J1LLn3D+IK1ejrwoo3zM4coK6tvXswPgEbL/WkGtYV6rWGma7XZXe
ODSKZD5tMr1yWvljjtFhSBYOWD2jW99zcie+q8yEcLUCu2tbPtd79r6LjLU6hdw2
xlTOXDjZXPzuuP/bHYY0tBekNDm3Xw4xbLG0CBgEKUtUmcJZPxp1PgzIJoyPhMc/
xRWirRXqRc/f4At085qKiF57ko+YyJYQxZn07JMdNJf0SjmQNujF/3YZq0ckSqAO
pfqC3CghmVKfqacKjIm/rOUPzafGZami7gqtuojrIeYXFtLYu7ty+4kmDkwSBjcx
yPd26Ds3enAjMBlQXoA8JCC/MTZYhJI+FiXCgp9AqFnoN6vZLdVRwMzsXN0D46r2
ubfsA5SdB/f1FNpVgbYdGsKZtVZiPWcnG88DKFj0KukI/2TA8RmdGIxP3npt5j1S
q+ln44MohhYy1C4196UPy6m7Eqna30MwsksfU7mWirTP9h4cGm08a3o87ZBy+Zs/
VCm+v+Otsbw78gKlvw3xtgrpuL90c09TbrE1o5EqM5ysdBSEz9c=
=/BDQ
-----END PGP SIGNATURE-----
pgp1FxJbemdtt.pgp
Description: PGP signature
--- End Message ---
