Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
http://qa-logs.debian.net/2020/12/05/spring_104.0+dfsg-7_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Hi,

This package builds Arch:all binary packages, but they cannot be built
on arm64. I don't think we have a good way to indicate that.

The Architecture: field already restricts the arch-specific binary
packages to something that does not include arm64.

For reference, here are some other packages I ran into in the same case:

bolt-lmm_2.3.4+dfsg-2_unstable.log:Architecture: amd64 i386 ppc64el all
gkl_0.8.6+dfsg-2_unstable.log:Architecture: all amd64
libosl_0.8.0-3_unstable.log:Architecture: i386 amd64 all
rapmap_0.15.0+dfsg-1_unstable.log:Architecture: amd64 all
reprozip_1.0.16-1_unstable.log:Architecture: all amd64 i386 x32
spring_104.0+dfsg-7_unstable.log:Architecture: amd64 i386 all

Lucas