That page says that there is no bibletime build for armel, mips, mips64el, ppc64el, and s390x. The reason there is no build on those architectures is because one of the build dependencies (qtwebengine5-dev) cannot be installed on those archictures.
Looking at the debian/control file for qtwebengine-opensource-src (the source package), this is how qtwebengine5-dev is declared: Package: qtwebengine5-dev Architecture: amd64 arm64 armhf i386 mipsel So, the solution would be to update bibletime so that instead of "Architecture: any", it matches the architecture list of qtwebengine5-dev. That said, bibletime-data is "Architecture: all" and I am not sure if changing the list of valid architectures for bibletime should result in a change to bibletime-data. Otherwise you might end up with bibletime-data on architectures for which bibletime itself is not available. That is, unless the archive software does not include "Architecture: all" packages in architectures for which no binary packages are produced from a given source package. That is probably something to ask on debian-devel before moving forward. Regards, -Roberto On Fri, Mar 16, 2018 at 01:49:49PM +0000, Teus Benschop wrote: > The package "bibletime" is not moving from sid to testing. > It has excuses for not moving there. > [1]https://qa.debian.org/excuses.php?package=bibletime > I am not sure about how to go about this? What is the best approach to fix > the excuses, or to work around the excuses? The goal is to move the > "bibletime" package to testing. > > References > > Visible links > 1. https://qa.debian.org/excuses.php?package=bibletime > _______________________________________________ > Pkg-crosswire-devel mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel -- Roberto C. Sánchez _______________________________________________ Pkg-crosswire-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
