[Pkg-crosswire-devel] Uploading to Debian experimental -- possible?

[Jonathan Marsden]

Dmitrijs Ledkovs wrote:

>     One question: splitting the data out like this creates a new binary
>     package.  Does that mean that when uploaded to Debian experimental, it
>     is going to languish in the "NEW" queue?  Or will it still go straight
>     in because the source package (bibletime) is already in Debian?
> 
> NEW queue is by source package only =D

Cool, thanks for the info.  That's good news.

In alphabetical order, we have:

bibledit:

No dependency on libsword7, exists in Debian already => Use experimental

biblememorizer:

No dependency on libsword7, exists in Debian already => Use experimental

bibletime:

Depends on libsword7, exists in Debian already => Waits for sword

gnomesword:

Depends on libsword7, exists in Debian already => Waits for sword

sword:

Exists in Debian already => Can use experimental (when ready!)

This suggests to me that we can perhaps "go for it" fairly soon, at
least with bibledit and biblememorizer, which do not depend on
libsword7.  I doubt we can get bibletime or gnomesword in until we get
sword in, because of their direct dependency on libsword7 and build-dep
on libsword7-dev.

Is there anyone here with the privs and time/energy to look over
bibledit and biblememorizer (as they are not sword-dependent) right
away, and do whatever it takes to get them into Debian experimental?  We
may want a needs-packaging bug for each of them in the Debian BTS?  Once
they are in, I can file sync request bugs for each on LaunchPad, and
then we'll ask the MOTUs to approve them.

BTW, I just set up a Debian Lenny RC2 virtual machine here last night,
so I can now start to test packages under Debian (i386) as well as under
Ubuntu.

Jonathan