On 2020-11-02, Adrian Bunk wrote: > Source: mes > Version: 0.22-4 > Severity: important > Tags: ftbfs > > "amd64 armel armhf i386" are the architectures supported upstream > (32bit arm needs some files that are in upsteam but missing in the > 0.22 release tarball).
There is work on adding more architectures in mes upstream (e.g. arm, arm64, FreeBSD, Hurd, riscv64)... My understanding was in Debian to not pre-emptively restrict architectures... I have gotten bugs on other packages for adding architecture restrictions before even though it FTBFS on those architecture before. Having architecture restrictions by default requires porters to get a sourceful upload to enable building that package (or maintaining a fork). I can see the logic of either approach... live well, vagrant
signature.asc
Description: PGP signature
