Hi Paul, On Thu, Mar 31, 2022 at 10:06:24AM +0200, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 60 days as having a Release Critical bug in testing > [1]. Your package src:yosys has been trying to migrate for 61 days [2]. > Hence, I am filing this bug. Your latest upload failed to build from source > on mips64el and s390x where it built successfully in the past. The latest > upload also caused autopgktest regression on all architectures.
Getting myself a porterbox guest account just took ages, I'm on it now :)
> If you believe your package is unable to migrate to testing due to issues
> beyond your control, don't hesitate to contact the Release Team.
It seems to me berkeley-abc is to blame for most yosys test suite failures
and particularly the s390x one that's blocking migration. Apparently it has
major problems on big-endian architectures that aren't easily fixed:
https://github.com/YosysHQ/yosys/issues/2645
How would I go about documenting and excluding s390x from building yosys
and is there anything I need to do about the non-offical Debian ports
architectures or can I just let those builds fail without it affecting
yosys' migration?
Thanks,
--Daniel
signature.asc
Description: PGP signature
