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/ufoai-maps_2.5-2_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.

Hello,

The package builds fine on amd64. I don't think it is correct to use severity
serious in this case because ufoai-maps is an arch:all package. The same is
true for Java packages. If we want to make this a release goal (making arch all
packages buildable on all supported architectures), it should have been
discussed months before the freeze. I saw that you have lowered the severity on
some packages already. Can we agree to use severity normal for build failures
on other architectures than amd64 if the package in question is arch:all?

Regards,

Markus

Hi,

I sent a message to similar failures, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976468#10
(I missed ufoai-maps because it hadn't finished building on amd64 yet
when I worked on this).

So yes, I'm fine with downgrading.

Lucas