On Fri, Jun 19, 2020 at 02:45:37PM -0300, Joao Eriberto Mota Filho wrote: > Package: nmapsi4 > Version: 0.5~alpha2-1 > Severity: serious > Tags: ftbfs patch > Justification: fails to build from source (but built successfully in the past) > > Dear Maintainer, > > nmapsi4 fails to build from source in several architectures since 0.5~alpha2-1 > revision. > > nmapsi4 build depends of qtwebengine5-dev. Since 5.9.1+dfsg-5 revision, > released > in 30 Sep 2017, qtwebengine5-dev is only available for amd64, arm64, armhf, > i386 > and mipsel. Consequently, now nmapsi4 FTBFS in armel, mips64el, ppc64el, > s390x, > alpha, hppa, hurd-i386, ia64, m68k, powerpc, ppc64, riscv64, sh4, sparc64 and > x32.
There is no FTBFS: https://buildd.debian.org/status/package.php?p=nmapsi4 There are plenty of packages in the archive whose build dependencies cannot be fulfilled on all release architectures. This is not a problem. >... > -Architecture: any > +Architecture: amd64 arm64 armhf i386 mipsel >... This would actually make things worse, since manual maintainance of such architecture lists is extra effort. Imagine qtwebengine5-dev gains support for a new architecture like riscv64. With "Architecture: any" all packages that directly or indirectly build depend on qtwebengine5-dev will automatically be built as soon as qtwebengine5-dev is available on this architecture. With an explicit architecture list bugs would have to be filed and manual uploads made for every single of these packages. > Regards, > > Eriberto cu Adrian
