Upstream claims the code is GPL-3+, see the forwarded email I just sent
you, so it needs to be cleared.

O.


On Thu, Jun 6, 2013 at 11:29 AM, Jérémy Lal <[email protected]> wrote:

> I don't think this concerns debian-legal, so i move the discussion
> back to seafile ITP.
>
> On 06/06/2013 07:40, Ondřej Surý wrote:
> > Hi,
> >
> > I am working on packaging ccnet[1] library (requirement for seafile),
> > and the upstream code has two licenses in the base directory - MIT
> > and GPL-3+.
> > When I asked for clarification they have replied the code is GPL-3+
> > with some parts reused from some other project which was MIT
> > licensed.
>
> There is some confusion...
> Copyright [2] is BSD-2-clause and there's a GPL3 LICENCE.txt file.
> So it's the other way around.
>
> > Unfortunatelly the individual source files are not licensed, so it's
> > unclear to me what's the license of the files and the packages as
> > whole.
>
> Then you should review the whole package file by file.
> Let me help :
>
> * There is some copy/paste/rename of inet_ntop.c code [3][4],
>   ISC License, in lib/libccnet_utils.c.
> * lib/buffer.c has a BSD-3-clause license.
> * lib/net.c has an mcast_join function that seems directly taken from
>   Unix Network Programming sample code [5]. I did not find a license
>   for that file. There is a disclaimer, though.
> * net/common/getgateway.c is from libnatpmp, see [6].
>   Now BSD-3-clause.
> * net/common/list.h is a kernel header, GPL-2 license.
>
> No GPL-3 found unless i missed something.
>
> > Can you provide a guidance?
> >
> > (It would still need openssl+gpl exception to go in.)
> >
> > Ondřej Surý 1. https://github.com/haiwen/ccnet
>
> Hope that helped,
> Jérémy.
>
>
> [2]
> https://raw.github.com/haiwen/ccnet/master/COPYRIGHT
> [3]
> https://github.com/haiwen/ccnet/commit/f9a41fbc
> [4]
> https://github.com/haiwen/ccnet/commit/2de2207f
> [5]
> http://www.unpbook.com/unpv13e.tar.gz
> in lib/mcast_join.c
> [6]
> http://packages.qa.debian.org/libn/libnatpmp.html
>
>


-- 
Ondřej Surý <[email protected]>

Reply via email to