Bug#1129007: src:octave-instrument-control: fails to migrate to testing for too long: FTBFS on s390x

Paul Gevers <[email protected]>
Newsgroups gmane.linux.debian.ports.s390
Message-ID <f4776257-409b-462a-a1f8-66069061065f__22864.0737988584$1772044662$gmane$org@debian.org>
Source: octave-instrument-control
Version: 0.9.5-3
Severity: serious
Control: close -1 0.10.0-1
Tags: sid forky
User: [email protected]
Usertags: out-of-sync
X-Debbugs-CC: [email protected]
User: [email protected]
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 32 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 
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=octave-instrument-control

Current text from [2]:
Migration status for octave-instrument-control (0.9.5-3 to 0.10.0-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.0-1: amd64: Pass, 
arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
∙ ∙ Lintian check waiting for test results on s390x - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/o/octave-instrument-control.html
∙ ∙ Reproducible on amd64
∙ ∙ Reproducible on arm64
∙ ∙ Reproducible on armhf
∙ ∙ Reproducible on i386
∙ ∙ Reproducible on ppc64el
∙ ∙ 31 days old (needed 5 days)
OpenPGP_signature.asc (application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE-----

wsC7BAABCABvBYJpn0EiCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmcYfktD8NuQfzZEg+qFZvjfWjbQiYecuaJLE6HN5hsx
OBYhBFi2bUhza+k7BS3mcpxcmesFvXUKAACzzwgAvQT3OV/P9rcCFr5bn2Th3THp
KPoIYkgv33UJ8kRkB8J4d5UsnR9P9qRaf1f5CRmu7QszF5QB1cQbxJbnSNRIzG+R
ik3/wkKCjt5FcTlItsvDSu3krb4f5J+o8uOmnZlgQMTksSX6m8BqqXkwnulBC+Gt
7GPG3Zrh6nIbsBQgV4vR0Bm4XFvO0ILeVfI8RYj0JlZBaN/HSI1IZulydkxy4x4T
RiYocbZTwDl2vaMqH7LKqRD7jDRU91PR1tkIaq5mZ+DTAMnIV+U3/q+psbJIi9T7
4nvMtUQyeE21+5CJOuBLc0g9RnVOyPgvpTMwuWeqVhmpU89OuYqIQjxJ0ciYAw==
=bn4z
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.