[Debian-on-mobile-maintainers] Bug#1125510: src:qrtr: fails to migrate to testing for too long: dropped architectures

[Paul Gevers]

Source: qrtr
Version: 1.1-2
Severity: serious
Control: close -1 1.2-1
Tags: sid forky d-i
User: release.debian.org at packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: debian-boot at lists.debian.org

Dear maintainer(s),

I noticed that you stopped supporting ppc64el, riscv64el and s390x, but 
your package builds udebs. Are those udebs used by d-i and if so, was 
the reduction of architectures discussed and agreed with the d-i team? 
There is no mention of this in the changelog.

[The rest of this message is generated from a template]

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:qrtr has been trying to migrate for 31 
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=qrtr

Current text from [2]:
Migration status for qrtr (1.1-2 to 1.2-1): BLOCKED: Maybe temporary, 
maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on i386
∙ ∙ Missing build on ppc64el
∙ ∙ Missing build on riscv64
∙ ∙ Missing build on s390x
∙ ∙ Autopkgtest deferred on i386: missing arch:i386 build
∙ ∙ Autopkgtest deferred on ppc64el: missing arch:ppc64el build
∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
∙ ∙ Autopkgtest deferred on s390x: missing arch:s390x build
∙ ∙ Lintian check waiting for test results on riscv64, i386, ppc64el, 
s390x - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qrtr.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ 
∙ 31 days old (needed 5 days)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 585 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/debian-on-mobile-maintainers/attachments/20260115/a806af79/attachment-0001.sig>