Source: octave-instrument-control
Version: 0.10.0-2
Severity: serious
Control: close -1 0.10.1-1
Tags: sid forky
User: release.debian.org@packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: debian-s390@lists.debian.org
User: debian-s390@lists.debian.org
Usertags: s390x
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:octave-instrument-control 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: it failed
to build on s390x hence I CC-ed the s390x porters.
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=octave-instrument-control
Current text from [2]:
Migration status for octave-instrument-control (0.10.0-2 to 0.10.1-1):
BLOCKED: Maybe temporary, maybe blocked but Britney is missing
information (check below)
Issues preventing migration:
∙ ∙ Missing build on s390x
∙ ∙ Autopkgtest deferred on s390x: missing arch:s390x build
∙ ∙ Autopkgtest for octave-instrument-control/0.10.1-1: amd64: Pass,
arm64: Pass, armhf: Pass, i386: Pass, loong64: Pass, ppc64el: Pass,
riscv64: Pass
∙ ∙ Lintian check waiting for test results on s390x - info
Additional info (not blocking):
∙ ∙ Updating octave-instrument-control will fix bugs in testing: #1133584
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/o/octave-instrument-control.html
∙ ∙ Not reproduced on amd64 (not a regression): octave-instrument-control
∙ ∙ Not reproduced on arm64 (not a regression): octave-instrument-control
∙ ∙ Not reproduced on armhf (not a regression): octave-instrument-control
∙ ∙ Not reproduced on i386 (not a regression): octave-instrument-control
∙ ∙ 33 days old (needed 5 days)