Source: schism
Version: 2:20251014-1
Severity: serious
Control: close -1 2:20260524-1
Tags: sid forky ftbfs
User: release.debian.org@packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: debian-powerpc@lists.debian.org
User: debian-powerpc@lists.debian.org
Usertags: ppc64el

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:schism 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. 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=schism

Current text from [2]:
Migration status for schism (2:20251014-1 to 2:20260524-1): BLOCKED:
Maybe temporary, maybe blocked but Britney is missing information (check
below)
Issues preventing migration:
∙ ∙ Missing build on ppc64el
∙ ∙ Autopkgtest deferred on ppc64el: missing arch:ppc64el build
∙ ∙ Lintian check waiting for test results on ppc64el - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/s/schism.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 31 days old (needed 5 days)

Hey, maintainers, thanks for maintaining this package in Debian.

I think this issue might have fallen through the cracks? So far as I can
tell, clicking around Debian's package tracker, the timeline looks like
this:

2026-05-27: Debian's schism package is updated to the newest upstream
version, 20260524.

2026-05-28 (one day later): The person packaging schism for Fedora
reports the PowerPC build failure to upstream, at:
https://github.com/schismtracker/schismtracker/issues/828

2026-06-28 (a month and a day later): This bug is filed, since Debian
hit the same FTBFS-on-ppc64el problem with version 20260524 that Fedora
hit.

2026-06-28 (still a month and a day later): This bug is marked as "fixed
in versions schism/2:20260524-1" (i.e. the version where the FTBFS was
detected) and "done".

2026-07-03 (a month and a bit later): Upstream commits a change titled
"util: fix build on ppc64" targeting big-endian PowerPC, although they
hope it will fix little-endian PowerPC too:
https://github.com/schismtracker/schismtracker/commit/5509849f2b7

2026-07-27 (two months later): The schism package is removed from
testing, due to the continued failure to build on ppc64el.

schism may not be the most popular package, but I think it would be a
shame for it to fall out of Debian if cherry-picking the upstream patch
would fix it.


Timothy Allen.