Your message dated Tue, 01 Jul 2025 13:50:15 +0000
with message-id <e1uwbnh-008n7v...@fasolo.debian.org>
and subject line Bug#1107448: fixed in zigpy 0.80.1-2
has caused the Debian Bug report #1107448,
regarding src:zigpy: 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 ow...@bugs.debian.org
immediately.)
--
1107448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zigpy
Version: 0.78.0-1
Severity: serious
Control: close -1 0.80.1-1
Tags: sid trixie
User: release.debian....@packages.debian.org
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:zigpy has been trying to migrate for 33
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. 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
trixie, 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=zigpy
Current text from [2]:
Migration status for zigpy (0.78.0-1 to 0.80.1-1): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ autopkgtest for zigpy-deconz/0.24.1-1: amd64: Regression or new test
♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel:
Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻
(reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el:
Regression or new test ♻ (reference ♻), riscv64: Regression or new test
♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
∙ ∙ blocked by freeze: does not have autopkgtest (Follow the freeze
policy when applying for an unblock)
∙ ∙ Too young, only 7 of 20 days old
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zigpy.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙
∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Waiting
for reproducibility test results on i386 - info ♻
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: zigpy
Source-Version: 0.80.1-2
Done: Edward Betts <edw...@4angle.com>
We believe that the bug you reported is fixed in the latest version of
zigpy, 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 1107...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Edward Betts <edw...@4angle.com> (supplier of updated zigpy 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 01 Jul 2025 11:02:12 +0100
Source: zigpy
Architecture: source
Version: 0.80.1-2
Distribution: unstable
Urgency: medium
Maintainer: Home Assistant Team <team+homeassist...@tracker.debian.org>
Changed-By: Edward Betts <edw...@4angle.com>
Closes: 1107448 1108525
Changes:
zigpy (0.80.1-2) unstable; urgency=medium
.
* Add Breaks: python3-zigpy-deconz (<< 0.25.0-1~)
(Closes: #1107448, #1108525)
Checksums-Sha1:
22a9d7526acec57f77b51f18eb9063632b3aee6c 2298 zigpy_0.80.1-2.dsc
89ffd7016a4c72a6c144c008499b6362d6eb83d4 3060 zigpy_0.80.1-2.debian.tar.xz
0c2ed172245c8581400f9b78dfe932b254be7a97 7414 zigpy_0.80.1-2_source.buildinfo
Checksums-Sha256:
3a1985b16df3f73936bb81560435bc3dc21e710e4eaaf90213faab49c2428ae9 2298
zigpy_0.80.1-2.dsc
a98f5b6d669bc5b28f7a9a322a1a8a0b29f963eec72f9762753da1335aa58760 3060
zigpy_0.80.1-2.debian.tar.xz
a177864396a2411acb7e8d962dc9fbb9c1e96abb7b618b20f62fe57fb11a93a8 7414
zigpy_0.80.1-2_source.buildinfo
Files:
3c6a63703c9e4baea214f880cf63825b 2298 python optional zigpy_0.80.1-2.dsc
23a4f67fe4b7f5de34b549572c70888c 3060 python optional
zigpy_0.80.1-2.debian.tar.xz
0f343a1f122f6cfb031cf5371600c2a3 7414 python optional
zigpy_0.80.1-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+4rPp4xyYInDitAmlgWhCYxjuSoFAmhjvZEACgkQlgWhCYxj
uSrc4g//Z1MLSQG2JS3o1ZW6ZU9JrLhQSAlMIa8272XFxiv+XLNpxE/tThvaLpYC
mJfiYfb+hBhcGKDgaCZPOAaKodppf9to398DHWhAAiFaclSM+OMzJtYXBusKxuew
13KbqD/SCLs/NgIJVlgrQ9lbD6E4XZ6qPUdLOE3sW1LycZbEUnlsSTDH/oXRSQ5U
C+IpXHR7FHlPr8jcMk+zhn4LViiWGCC5g+GzrRcpGdUTD3Xy6gX+QlhCHNwN35xl
KxpzjOXGnr7wltq0tEY8yneG7LzqiKaEqneemXgjtn4NWkxWBZY8V9P96q8w7B4j
0949hG5SSBoDMTRbW3WN5pfJWgaVEbwrQNj7DRzreG6iAvXTU6mWAqDYd7FqXs7w
PjI1DPdRALcoOWnYIocsaS9OGJPMl9qLusGm85aG9X4Ye6In3V66kZDzQZKwybZu
8ZmTJBLcCrb+c2TULEeslbIJ4tM5KBLpOGPB0FA9cUD6Ptu3OY82ZuRJ9kb8CcAD
0eT7AoUfG7w/7TkaJllo00oIlBvOxDXr0o0/mY9yR7qtyIEt1u+ripQgC2yN+uzu
TBfaVwYt5aI1SsDgz+gaGW5ejVqHlHL5PpaEw/r0CJPXJ1EskqEzpuVRXIL8aaYy
W4vVMf+LC8OER09HOcMIxwo2YOTvOef4GdKootPjaw/tvbJKd/I=
=t+dk
-----END PGP SIGNATURE-----
pgpXXsKhDhgeO.pgp
Description: PGP signature
--- End Message ---
