I just realize that I forgot the "Control:" header in my previous
message.
At any rate, after verifying that the package builds correctly in a armhf
chroot on abel.debian.org, I gave back the build on the armhf
autobuilders and the package did not FTBFS this time.
Best,
Rafael Laboissière
* Rafael Laboissière <raf...@debian.org> [2024-05-15 06:48]:
reopen -1 found -1 6.4.12+dfsg-3
I partially fixed Bug#1070994 in version 6.4.12+dfsg-3. Indeed, this
version correctly builds on arm64, armel, ppc64el, and riscv64.
However, build on armhf fails for an unrelated reason. I am currently
investigating this. I am hereby reopen the bug report.
Best,
Rafael
* Paul Gevers <elb...@debian.org> [2024-05-12 18:51]:
Source: praat
Version: 6.4.05+dfsg-1
Severity: serious
Tags: sid trixie ftbfs
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:praat has been trying
to migrate for 74 days [2]. Hence, I am filing this bug. The version
in unstabled failed to build on most architectures where it build
before.
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.
I have immediately closed this bug with the version in unstable, so
if that version or a later version migrates, this bug will no longer
affect testing. I have also tagged this bug 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.
Paul
[1]
https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=praat
