On Wed, 23 Sep 2026 at 09:39:44 +0200, Gregor Riepl wrote:
WebKitGTK can no longer work on big-endian architectures as a result
of an upstream move from Cairo to Skia, as announced in
<https://lists.debian.org/debian-devel/2026/09/msg00139.html> and
#1148038.
This is one of the leaf packages that will need to be removed from
s390x as a result.
Is there anything else that needs to be done for this bug?
Do we need to declare a dependency on architecture-is-little-endian?
If you need to upload slic3r-prusa in the near future for some other
reason (before webkit2gtk gets removed from s390x, which is still
blocked by some other packages right now), it could be a good idea to
add a Build-Depends on architecture-is-little-endian so that
slic3r-prusa:s390x won't be re-introduced and need removing again.
The tracking bug for removal of webkit2gtk from s390x is
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1148038>.
In the longer term, my understanding is that the maintainers of affected
packages like slic3r-prusa don't need to do anything special. After
webkit2gtk is removed from s390x, slic3r-prusa will become
BD-Uninstallable on s390x and won't be rebuilt there; but new uploads of
slic3r-prusa should still be able to migrate to testing, because there
already won't be a s390x binary available, so being unbuildable on s390x
won't be a regression.
smcv
