Your message dated Wed, 11 Jun 2025 12:33:58 +0000
with message-id <e1upkeu-001wjb...@fasolo.debian.org>
and subject line Bug#1107431: fixed in bluetooth-sensor-state-data 1.9.0-2
has caused the Debian Bug report #1107431,
regarding src:bluetooth-sensor-state-data: 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.)
--
1107431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bluetooth-sensor-state-data
Version: 1.7.5-1
Severity: serious
Control: close -1 1.9.0-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:bluetooth-sensor-state-data has been
trying to migrate for 34 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=bluetooth-sensor-state-data
Current text from [2]:
Migration status for bluetooth-sensor-state-data (1.7.5-1 to 1.9.0-1):
BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ autopkgtest for bluemaestro-ble/0.2.3-2: 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 ♻)
∙ ∙ autopkgtest for bluetooth-sensor-state-data/1.9.0-1: amd64: Pass,
arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass,
riscv64: Pass, s390x: Pass
∙ ∙ autopkgtest for bthome-ble/3.12.5-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 ♻)
∙ ∙ autopkgtest for sensorpro-ble/0.5.3-2: 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 ♻)
∙ ∙ autopkgtest for sensorpush-ble/1.7.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 ♻)
Additional info:
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/b/bluetooth-sensor-state-data.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙
∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙
Reproducible on i386 - info ♻ ∙ ∙ 24 days old (needed 20 days)
∙ ∙ not blocked: has successful autopkgtest
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: bluetooth-sensor-state-data
Source-Version: 1.9.0-2
Done: Edward Betts <edw...@4angle.com>
We believe that the bug you reported is fixed in the latest version of
bluetooth-sensor-state-data, 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
bluetooth-sensor-state-data 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: Wed, 11 Jun 2025 13:17:21 +0100
Source: bluetooth-sensor-state-data
Architecture: source
Version: 1.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Edward Betts <edw...@4angle.com>
Closes: 1107431
Changes:
bluetooth-sensor-state-data (1.9.0-2) unstable; urgency=medium
.
* This latest release breaks existing Python bluetooth libraries in testing.
* The appropriate libraries have been added to the Breaks field, to allow
this package to migrate to testing. (Closes: #1107431)
Checksums-Sha1:
87d778028155e88a890df8525947fd1d18674c0c 2594
bluetooth-sensor-state-data_1.9.0-2.dsc
04ef883ca9a56250bbd8e09b085d9287ea846856 4076
bluetooth-sensor-state-data_1.9.0-2.debian.tar.xz
58d45a8d19c9c2e22fcc0d956f019171b1635825 7323
bluetooth-sensor-state-data_1.9.0-2_source.buildinfo
Checksums-Sha256:
ed0a1fd795a152a8ef656c359d02f1968376c34513b02538e61a03660018c7b1 2594
bluetooth-sensor-state-data_1.9.0-2.dsc
c1e9bf7f79df4edb44558ef9ef64569df45f71ab90253d07622f5e9b36ecabc5 4076
bluetooth-sensor-state-data_1.9.0-2.debian.tar.xz
be4a463d20fe4803cd52095ccfc9ec176b0440b1d3e76abf3d3024bc23206a8f 7323
bluetooth-sensor-state-data_1.9.0-2_source.buildinfo
Files:
5d580a02b7da48dcdb7afb3770a9d7a9 2594 python optional
bluetooth-sensor-state-data_1.9.0-2.dsc
bbad90eda0a3fc80f9522c811693781a 4076 python optional
bluetooth-sensor-state-data_1.9.0-2.debian.tar.xz
0ec9d3c5082f1dcad94ca2bb8c355f2c 7323 python optional
bluetooth-sensor-state-data_1.9.0-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+4rPp4xyYInDitAmlgWhCYxjuSoFAmhJdK8ACgkQlgWhCYxj
uSq/WQ/+Iv92p+UQrCGhUdoSMsEv8tvB1pJY+Cbvx6P1opyijKZOqRagHPSmVBwd
cMBnbsypG2HTDxmVwZzhV/sLdcHIMJ16qM0fMKwY1nJ+zG4mADeI05kbuuodpHeP
4+rP+xBKfhhyi0U68MNBqnYgmLHQF9ao5kSvAwQkXsNzLMsLOiq42h8Lvni8H0F6
z9gP5LNO6nDR4L8lE8FskXCTj18JOdXv5+xe4Wc5vE41uGIi2aRbwvLZgWd26RMS
RSRVIV1Hs6qs0xB6er8JP5gsLJUkIuBkh9B7tmsiycyGECm+2v96kLzciHaBMHUx
v/xertCtdNKEe+rtaCJSmKA6XUh0PlrhNzE9H7yKtu192wuZpyhOZMkdc0cBJusk
nz9QBynKm0Pmwzq5AG1F9MX/FjK66nkbAwMoPf+fuxgL8wuZqNT1iygU9L6DkgCB
uLc17LJUsrDb01hCww8Ko0XWbyR2Yeh7ewv0DmNdVlTWPlOL6o/Jf2D+trc/VgsX
ntKUZhUAnSrgpkbHxATlkSgyxHQWquSRtXm/48zUmTI6OtHq8bdpH0y2V9mVxAPZ
6tCgnquRO+yJ3FOhNkQD1o7gtTQfeZRDauBLV2pSfaKAWd9GxBxaFLOBK1irMIIu
sIDxYW2Ryk1Qv9xBkqvaFzc+aadK1HY62XNqXW7AbnIq/WnUG6Y=
=TS+4
-----END PGP SIGNATURE-----
pgpJ3J4OL9Ikn.pgp
Description: PGP signature
--- End Message ---
