Bug#1018871: ibus-tests:armel: depends on gnome-shell:armel which is likely to be removed

[Simon McVittie <smcv@debian.org>]

On Thu, 01 Sep 2022 at 14:25:29 +0200, Gunnar Hjalmarsson wrote:
> given the
> current ibus packaging, maybe these lines in debian/rules would be more
> suitable:
> 
> ifeq ($(DEB_HOST_ARCH), armel)
>    skip_packages = -Nibus-tests
> endif

That assumes that all other architectures that we care about have a
working mozjs/gjs, which is broadly true if you are not interested
in retrocomputing, but is an assumption that might need more future
maintenance, for example if it regresses on s390x or mips64el. It's up
to you whether you prefer to assume that unknown architectures do or
don't have a working mozjs/gjs.

To avoid this change's migration being blocked, you'll also need to set
Architecture: !armel in debian/tests/control. Otherwise, ci.debian.net
will interpret "the test needs ibus-tests, but I can't install that"
as a test failure on armel.

The reason I suggested assuming that unknown architectures don't have
mozjs/gjs is that mozjs usually requires per-architecture code to be
written (it's a complicated JIT implementation). It looks like bookworm
is likely to have a working gjs on

    amd64 arm64 armhf i386 mips64el ppc64el s390x
    (riscv64)

but not on

    armel
    (alpha arc hppa hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k powerpc ppc64 sh4 sparc64 x32)

where the architectures in parentheses are currently -ports architectures,
and the others are currently release candidates.

    smcv