[pkg-crosswire-devel] Fwd: sword-comm-mhc_2.0-1_amd64.changes REJECTED
Bastian Germann
bastiangermann at fishpost.de
Sat Aug 28 14:36:51 BST 2021
Am 28.08.21 um 15:10 schrieb Roberto C. Sánchez:
> On Sat, Aug 28, 2021 at 02:07:18PM +0200, Teus Benschop wrote:
>> Hi all,
>>
>> The package was rejected. It was because the copyright didn't match with
>> the DFSG.
>>
>> On thinking about this, I think that it does not in any way impact users
>> who want to use the commentary that was to be included in the package.
>> Everyone can install it from the online Crosswire repositories.
>>
>> Taking it one step further, my question is what the additional value of
>> this package would have been in the first place?
>>
>> Was it to assist people who don't have any internet connection, or who for
>> certain reasons don't want to use that?
>>
> Several years ago I took it upon myself to package some of what I
> thought would be the most common and useful modules. It feels "better"
> to me to be able to install components via apt rather than downloading
> modules, for example here with Sword modules, CPAN modules, Python
> modules, etc. It simplifies deploying across multiple machines, where I
> can deploy a meta-package that pulls in the necessary package as a
> dependency, rather than having to script the installation of an external
> component. Just a preference on my part.
The downside of packaging the CrossWire modules is that they are not
very good at keeping their source updated to the same version that is
published as binaries on their FTP server. Also, the copyright
information is sometimes inaccurate, which is the case with the MHC
module. Lafricain has improved the situation a lot compared to what it was.
I think, the baseline for our modules should be to meet Debian Policy.
Two of them will be autoremoved if the source does not appear in the
next two weeks, and I think that is okay.
For the other modules, there are still #985655 and #985656, which are
actually also Policy violations and could have a higher priority. I do
not have experience of converting USFX/USFM to OSIS/Sword and there are
several programs out there that do that. The affected modules' source
eBible uses Haiola, but I think having that in Debian just for this
reason will be too much work. So, alternatively we could package
usfm2osis (which version?) or u2o. Any thoughts on this?
More information about the pkg-crosswire-devel
mailing list