[Pkg-crosswire-devel] Using an updated upstream bibleedit (copyrights fixed)

[Jonathan Marsden]

Daniel Glassey wrote:

> I didn't realise syncs could be made from experimental! Yes, I can
> upload there once the copyright/license issues are sorted.

Teus already made the relevant changes in the bibledit git repo, and
announced the result as version 3.5.45.  Of course, this includes all
other changes made in that repo since 3.5 too.  I confirmed that this
source tree is 100% OK (it is 100% GPL!) according to licencecheck.

So, we could generate a tarball from git and call that our original
source, and so package bibledit 3.5.45 -- and risk any bugs resulting
from those changes.  Or, we can generate a patch containing just the
copyright/licence changes, and package that plus the official 3.5
tarball (but then we would still be distributing a tarball that has
licence issues until the patch we provide with it is applied... is that
OK??).  Do I need to create a "dfsg" tarball??

I think I'm probably better at technical stuff than legal stuff ... does
anyone know what the officially Debian-correct and Ubuntu-correct way to
handle this would be? :)

Jonathan