From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/lxc: fix license
Date: Wed, 15 Jul 2020 21:38:48 +0200 [thread overview]
Message-ID: <CAPi7W83p-63jxoYFpda1szKQWTr3XFgXecS9QGLZ92MxnMb5_w@mail.gmail.com> (raw)
In-Reply-To: <20200715213055.407fac8d@windsurf.home>
Hi Thomas,
Le mer. 15 juil. 2020 ? 21:30, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> a ?crit :
>
> On Wed, 15 Jul 2020 21:04:38 +0200
> Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
>
> > Commit 5a393677314dfdaa6a4bd6a847b642ae54517538 forgot to update
> > license which has been changed from COPYING to LICENSE.GPL2 and
> > LICENSE.LGPL2.1 since version 4.0.0 and
> > https://github.com/lxc/lxc/commit/cc73685dd09315b292968ee91a08a8f295376b35
> >
> > It should be noted that COPYING describes GPLv3 for an unknown reason
>
> Has this been reported upstream ?
I created an issue here: https://github.com/lxc/lxc/issues/3484.
>
> > LXC_VERSION = 4.0.3
> > LXC_SITE = https://linuxcontainers.org/downloads/lxc
> > -LXC_LICENSE = LGPL-2.1+
> > -LXC_LICENSE_FILES = COPYING
> > +LXC_LICENSE = GPL-2.0, LGPL-2.1+
>
> Do we have some details about what is under GPL, what is under LGPL ?
Yes, each file has a SPDX header since
https://github.com/lxc/lxc/commit/cc73685dd09315b292968ee91a08a8f295376b35.
Most of them are LGPL but some source files under tools directory are
GPL-2.0-only.
>
> Is it GPL-2.0, or GPL-2.0+ ?
It is GPL-2.0.
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
Best Regards,
Fabrice
next prev parent reply other threads:[~2020-07-15 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 19:04 [Buildroot] [PATCH 1/1] package/lxc: fix license Fabrice Fontaine
2020-07-15 19:30 ` Thomas Petazzoni
2020-07-15 19:38 ` Fabrice Fontaine [this message]
2020-07-15 20:26 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPi7W83p-63jxoYFpda1szKQWTr3XFgXecS9QGLZ92MxnMb5_w@mail.gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.