[Pkg-crosswire-devel] SWORD 1.5.11-1 now really in Debian experimental -- time for a second Bibletime upload attempt?

[Jonathan Marsden]

Roberto C. Sánchez wrote:

>> Now that sword-1.5.11-1 seems to be fully accepted into Debian
>> experimental, could you re-try building the bibletime 2.0~alpha3 package
>> against that, and (assuming it builds fine) upload it into experimental
>> also for us?  The same goes for the xiphos 3.0.1 package that Dmitry
>> recently RFSed, of course.

> Did you want to tighten up the build-dependency on libsword-dev before I
> build and upload it?

Sure.  There's an issue preventing me from easily building on sid with
experimental in sources.list right now... apt-get install libsword7
works fine, but apt-get install libsword-dev pulls in the old
libsword-dev and so replaces libsword7 with libsword6, which is...
undesirable :)

I'm not sure why I do not get the newer (Debian experimental, 1.5.11-1)
version of libsword-dev when I have experimental in my sources.list --
any ideas?  I can manually install the newer libsword-dev, of course...
but I suspect that the fact I have to do so means an attempt at building
 bibletime on official Debian build machines will currently pull in the
"wrong" (old) libsword-dev and so fail?

Anyway, there is now a new Bibletime source package with a libsword-dev
(>= 1.5.11) Build-Depends available for you at

  http://computeroptions.net/sword/bibletime_2.0~alpha3-1.dsc

which works *if* I manually install the newer libsword-dev.

> Your uploads are only accepted if one of the following two conditions
> is met:
> 
>  1. you are a Debian Developer with a key in the Debian keyring
>  2. you are a Debian Maintainer with a key in the Debian Maintainer
>     keyring and the package has the the DM-Upload-Allowed header set to
>     yes in debian/control
> 
> Otherwise, the upload must still be sponsored (which I am happy to do).

OK, thanks for clarifying.  So we'll need to keep pestering you for
every upload!

Jonathan