<div dir="ltr">Thank you for the information, Roberto, that is something I will try.<div>It does not give me a happy feeling to reduce the number of architectures that BibleTime runs on. But I realize, now, that this is something beyond our control. It's upstream's choice to use a dependency not available on all architectures.</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, 16 Mar 2018 at 15:22 Roberto C. Sánchez <<a href="mailto:roberto@debian.org">roberto@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That page says that there is no bibletime build for armel, mips,<br>
mips64el, ppc64el, and s390x. The reason there is no build on those<br>
architectures is because one of the build dependencies<br>
(qtwebengine5-dev) cannot be installed on those archictures.<br>
<br>
Looking at the debian/control file for qtwebengine-opensource-src (the<br>
source package), this is how qtwebengine5-dev is declared:<br>
<br>
Package: qtwebengine5-dev<br>
Architecture: amd64 arm64 armhf i386 mipsel<br>
<br>
So, the solution would be to update bibletime so that instead of<br>
"Architecture: any", it matches the architecture list of<br>
qtwebengine5-dev.<br>
<br>
That said, bibletime-data is "Architecture: all" and I am not sure if<br>
changing the list of valid architectures for bibletime should result in<br>
a change to bibletime-data. Otherwise you might end up with<br>
bibletime-data on architectures for which bibletime itself is not<br>
available.  That is, unless the archive software does not include<br>
"Architecture: all" packages in architectures for which no binary<br>
packages are produced from a given source package.<br>
<br>
That is probably something to ask on debian-devel before moving forward.<br>
<br>
Regards,<br>
<br>
-Roberto<br>
<br>
On Fri, Mar 16, 2018 at 01:49:49PM +0000, Teus Benschop wrote:<br>
>    The package "bibletime" is not moving from sid to testing.<br>
>    It has excuses for not moving there.<br>
>    [1]<a href="https://qa.debian.org/excuses.php?package=bibletime" rel="noreferrer" target="_blank">https://qa.debian.org/excuses.php?package=bibletime</a><br>
>    I am not sure about how to go about this? What is the best approach to fix<br>
>    the excuses, or to work around the excuses? The goal is to move the<br>
>    "bibletime" package to testing.<br>
><br>
> References<br>
><br>
>    Visible links<br>
>    1. <a href="https://qa.debian.org/excuses.php?package=bibletime" rel="noreferrer" target="_blank">https://qa.debian.org/excuses.php?package=bibletime</a><br>
<br>
> _______________________________________________<br>
> Pkg-crosswire-devel mailing list<br>
> <a href="mailto:Pkg-crosswire-devel@lists.alioth.debian.org" target="_blank">Pkg-crosswire-devel@lists.alioth.debian.org</a><br>
> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel</a><br>
<br>
<br>
--<br>
Roberto C. Sánchez<br>
<br>
_______________________________________________<br>
Pkg-crosswire-devel mailing list<br>
<a href="mailto:Pkg-crosswire-devel@lists.alioth.debian.org" target="_blank">Pkg-crosswire-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel</a><br>
</blockquote></div>