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

[Daniel Glassey]

On Wed, Jan 28, 2009 at 9:25 AM, Jonathan Marsden <jmarsden at fastmail.fm> wrote:
> 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? :)

If it's ok by Teus I think a new release of bibledit would be best. It
doesn't have to be a full release but
I don't think we should go through the pain of making a dfsg tarball
if we can avoid it. A tagged repo and tarball produced from it would
be great.

Regards,
Daniel

P.S. I'm going (mostly) offline for a few days tomorrow so I'll not be
able to do the upload til next week.