[Pkg-crosswire-devel] sword-comm-mhc_1.6-1_amd64.changes REJECTED

[Roberto C. Sánchez]

Hi Thorsten,

On Thu, Feb 15, 2018 at 08:26:28PM +0100, Thorsten Alteholz wrote:
> Hi Roberto,
> 
> sorry, for waiting so long with the answer.
> 
No problem. Thanks for getting back to me. I know you have been
extremely busy, so your response is much appreciated.

> If I understand correctly now, the CCEL text files are in the public domain.
> As they already have a special format, they don't need to have additional
> markup stuff but can be immediately processed by the CW tools to create
> Sword Modules.
> 
> You just put the compressed modules into the package.
> 
> It doesn't matter how the Sword project would like to distribute their
> modules. The preferred form is the form which the user of the texts actually
> prefer to make modifications. I don't think this is the case for the
> compressed modules but only for the text files. So in order to fulfill the
> DFSG requirements, you need to put the original text files as well into the
> source tarball (or in debian/missing-sources).
> Ideally you would create the compressed modules during package build. If
> this is for whatever reason problematic, you need to explain why and
> document the process for module creation. Everybody else should be able to
> create their own modules on demand. If some of the needed tools are not yet
> within Debian main, you need to upload them first[1]. If those tools are not
> suitable for main, the Sword modules must move to non-free.
> 
Thanks for the detailed explanation and the clean guidance.

> Please also update the other sword packages if needed.
> 
The team is preparing to make the move from Alioth to Salsa and so we
are also preparing to do some overdue project housekeeping. I will make
sure that we look at this and take care of packages currently in Debian
before resubmitting sword-comm-mhc for NEW processing.

Regards,

-Roberto

-- 
Roberto C. Sánchez