Hello Roberto, I have updated the list of packages in debian/control, to match the list you had given.
The updated code has been pushed to scm.alioth.debian.org/git/pkg-crosswire/bibletime.git. It was not yet tagged. With regard to what you said: "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. ... That is probably something to ask on debian-devel before moving forward." What I did was the following: 1. Thinking about what to ask on debian-devel. 2. Expecting them to say "Google first, before asking us" :) 3. Googling on the matter. 4. Looking at https://sources.debian.org/src/qtwebengine-opensource-src/5.9.2+dfsg-3/debian/control/ 5. Copying the way they did it there: Package: libqt5webengine-data Architecture: all Multi-Arch: foreign 6. Considering that if this is good for the qtwebengine data, it will also be good for the BibleTime data. May I ask for a review of the package and a sponsored upload. May you also grant me the privileges to upload the bibletime package myself. Thanks! Teus. On Sun, 18 Mar 2018 at 08:36 Teus Benschop <[email protected]> wrote: > Thank you for the information, Roberto, that is something I will try. > 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. > > On Fri, 16 Mar 2018 at 15:22 Roberto C. Sánchez <[email protected]> > wrote: > >> 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 >> >
_______________________________________________ Pkg-crosswire-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
