Bug#742077: RFS: vcmi/0.95-1 [ITP]
Hi,
Quoting Paul Wise (2014-08-29 17:47:10)
> On Fri, Aug 29, 2014 at 8:16 AM, Johannes Schauer wrote:
> > Would this solve the license incompatibility between fuzzylite (apache 2.0)
> > and vcmi (gpl2+)?
>
> Yes because the latest version (5.0) of fuzzylite (LGPLv3) is
> compatible with vmci (GPLv2+).
I'm confused. I asked whether removing fuzzylite from vcmi and making it a
shared library instead would solve the license incompatibility. I am aware that
using fuzzylite 5.0 will solve the issue but not using the embedded copy is a
different issue than upgrading the code to be compatible with version 5.0.
So the answer is: "No, but switching to 5.0 will"?
> > I asked upstream whether they can remove the embedded copy and depend on
> > the system version instead: http://bugs.vcmi.eu/view.php?id=1886
> ...
> > A problem might be that vcmi as the only user of that library uses the old 4.0
> > version while upstream just released 5.0. Vcmi upstream expressed that
> > migration to fuzzylite 5.0 would be very troublesome here:
> > http://bugs.vcmi.eu/view.php?id=1884#c4932
> >
> > Would it be okay to package fuzzylite 4.0 even though upstream is at 5.0?
>
> Since it is not GPLv2+ compatible, that wouldn't solve the problem.
Okay. Thank you for clarifying this.
> Perhaps fuzzylite upstream would be willing to apply the license change to
> 4.0 too?
I sent off an email to ask about that.
> The code copy should be removed in any case, if that proves impossible
> (perhaps it is patched), please contact the security team to report the
> issue.
It turns out that their embedded code copy is patched but I am in the process
of clarifying with upstream which parts they patched. Maybe no patching is
necessary anymore with fuzzylite 5.0 or maybe upstream can integrate their
patches into the 4.0 branch.
Thanks!
cheers, josch
Reply to: