Source: wireshark
Version: 4.6.6-1
Severity: serious
Control: close -1 4.6.6-2
Tags: sid forky ftbfs
User: release.debian.org@packages.debian.org
Usertags: out-of-sync
User: debian-arm@lists.debian.org
X-Debbugs-CC: debian-arm@lists.debian.org
Usertags: armhf

TL;DR: the package FTBFS on armhf and can't migrate

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:wireshark 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. Regularly, reporting
issues against reverse (build/test/regular) dependencies is what needs
to happen. If this has already been done, than this bug is just for
tracking purposes.

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=wireshark

Current text from [2]:
Migration status for wireshark (4.6.6-1 to 4.6.6-2): BLOCKED: Maybe
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on armhf
∙ ∙ Autopkgtest deferred on armhf: missing arch:armhf build
∙ ∙ Autopkgtest for termshark/2.4.0-5: amd64: Pass, arm64: Pass, i386:
Pass, ppc64el: Pass, riscv64: Pass, s390x: Test triggered
∙ ∙ Autopkgtest for wireshark/4.6.6-2: amd64: Pass, arm64: Pass, i386:
Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
∙ ∙ Lintian check waiting for test results on armhf - info
∙ ∙ Reproducibility check deferred on armhf: missing builds - info
∙ ∙ Depends: wireshark falcosecurity-libs (not considered)
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/w/wireshark.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 31 days old (needed 5 days)