[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Do autopkgtest for non-listed architectures prevent migration?



On 2022-01-22 15:06 +0100, Markus Blatt wrote:
> For why 32bit architectures are not listed:
> Many tests of the buildsystem of the upstream package fail because of Y2K38 bugs.
> Upstream does not see that as a problem as running a simulation on these architectures
> or simulations of just 16 years is not a goal. Fixing this in Debian would be
> much hard work and might not be worth it. Which is why would like to prevent it.

If the package builds on the 32bit arches then I would advise that you
let it build.  We always try to build for all arches in debian and it
is very annoying if you have say an armhf machine and something is not
available just because there was some test failure so upstream simply
excluded builds completely. Packges should only be excluded on an arch
if they are known not to build or to be genuinely useless there.

If there are too many problems with the tests to fix for now then
don't run the tests on those architectures, or mark them in the
autopackage tests as expected to fail (Not sure if we support 'test X
on arch Y known to fail' markings, but if we do then such markings
would be best). As Hilmar pointed out you mark which arches to run
tests on separately from which arches to build.

If the package is available then maybe someone who cares will fix
it. If it isn't they probably won't even try. A note in the
Debian.README about this known issue would be helpful.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/

Attachment: signature.asc
Description: PGP signature


Reply to: