[lxc-devel] [lxc/lxc] ddaa52: commands_utils.c: fix wrong licensing

Mon Mar 4 18:13:27 UTC 2019

  Branch: refs/heads/master
  Home:   https://github.com/lxc/lxc
  Commit: ddaa52263abd45e14020bf445c3231087ece8d41
      https://github.com/lxc/lxc/commit/ddaa52263abd45e14020bf445c3231087ece8d41
  Author: Christian Brauner <christian.brauner at ubuntu.com>
  Date:   2019-03-03 (Sun, 03 Mar 2019)

  Changed paths:
    M src/lxc/commands_utils.c

  Log Message:
  -----------
  commands_utils.c: fix wrong licensing

liblxc has always been meant to be LGPLv2.1+ as reflected by the many
downstreams projects and bindings which are themselves under LGPLv2.1+ or other
licenses which would be incompatible with linking against a GPLv2+ library.

It's pretty normal for a library to be LGPL while binaries are GPL as a GPL
library would only ever be usable by other GPL-only projects, which isn't the
case for very many of the liblxc downstreams.

The issue here is really carelessness. None of those GPL headers were put there
intentionally, instead being wrongly copy/pasted from other parts of the
codebase which is indeed intended to be GPLv2+. This is also made clear in our
CONTRIBUTING file in this repository:

Licensing for new files:
------------------------

LXC is made of files shipped under a few different licenses.

Anything that ends up being part of the LXC library needs to be released
under LGPLv2.1+ or a license compatible with it (though the latter will
only be accepted for cases where the code originated elsewhere and was
imported into LXC).

Language bindings for the libraries need to be released under LGPLv2.1+.

Anything else (non-libraries) needs to be Free Software and needs to be
allowed to link with LGPLv2.1+ code (if needed). LXC upstream prefers
LGPLv2.1+ or GPLv2 for those.

When introducing a new file into the project, please make sure it has a
copyright header making clear under which license it's being released
and if it doesn't match the criteria described above, please explain
your decision on the lxc-devel mailing-list when submitting your patch.

This is intended to switch over files to LGPLv2.1+ to which end we have
collected ACKs from relevant people.
/* Affected People */
Christian Brauner <christian.brauner at ubuntu.com>
Donghwa Jeong <dh48.jeong at samsung.com>

Signed-off-by: Christian Brauner <christian.brauner at ubuntu.com>
Acked-by: Donghwa Jeong <dh48.jeong at samsung.com>

  Commit: 0fb44ac949d3cd2ddf0e7e4d5f7c16bf710fcd5f
      https://github.com/lxc/lxc/commit/0fb44ac949d3cd2ddf0e7e4d5f7c16bf710fcd5f
  Author: Christian Brauner <christian.brauner at ubuntu.com>
  Date:   2019-03-03 (Sun, 03 Mar 2019)

  Changed paths:
    M src/lxc/commands_utils.h

  Log Message:
  -----------
  commands_utils.h: fix wrong licensing

liblxc has always been meant to be LGPLv2.1+ as reflected by the many
downstreams projects and bindings which are themselves under LGPLv2.1+ or other
licenses which would be incompatible with linking against a GPLv2+ library.

It's pretty normal for a library to be LGPL while binaries are GPL as a GPL
library would only ever be usable by other GPL-only projects, which isn't the
case for very many of the liblxc downstreams.

The issue here is really carelessness. None of those GPL headers were put there
intentionally, instead being wrongly copy/pasted from other parts of the
codebase which is indeed intended to be GPLv2+. This is also made clear in our
CONTRIBUTING file in this repository:

Licensing for new files:
------------------------

LXC is made of files shipped under a few different licenses.

Anything that ends up being part of the LXC library needs to be released
under LGPLv2.1+ or a license compatible with it (though the latter will
only be accepted for cases where the code originated elsewhere and was
imported into LXC).

Language bindings for the libraries need to be released under LGPLv2.1+.

Anything else (non-libraries) needs to be Free Software and needs to be
allowed to link with LGPLv2.1+ code (if needed). LXC upstream prefers
LGPLv2.1+ or GPLv2 for those.

When introducing a new file into the project, please make sure it has a
copyright header making clear under which license it's being released
and if it doesn't match the criteria described above, please explain
your decision on the lxc-devel mailing-list when submitting your patch.

This is intended to switch over files to LGPLv2.1+ to which end we have
collected ACKs from relevant people.
/* Affected People */
Christian Brauner <christian.brauner at ubuntu.com>
Donghwa Jeong <dh48.jeong at samsung.com>

Signed-off-by: Christian Brauner <christian.brauner at ubuntu.com>
Acked-by: Donghwa Jeong <dh48.jeong at samsung.com>

  Commit: 8d01f531c22f71f62dc1c53e18ed4a6703324e1c
      https://github.com/lxc/lxc/commit/8d01f531c22f71f62dc1c53e18ed4a6703324e1c
  Author: Christian Brauner <christian.brauner at ubuntu.com>
  Date:   2019-03-03 (Sun, 03 Mar 2019)

  Changed paths:
    M src/lxc/file_utils.c

  Log Message:
  -----------
  file_utils.c: fix wrong licensing

liblxc has always been meant to be LGPLv2.1+ as reflected by the many
downstreams projects and bindings which are themselves under LGPLv2.1+ or other
licenses which would be incompatible with linking against a GPLv2+ library.

It's pretty normal for a library to be LGPL while binaries are GPL as a GPL
library would only ever be usable by other GPL-only projects, which isn't the
case for very many of the liblxc downstreams.

The issue here is really carelessness. None of those GPL headers were put there
intentionally, instead being wrongly copy/pasted from other parts of the
codebase which is indeed intended to be GPLv2+. This is also made clear in our
CONTRIBUTING file in this repository:

Licensing for new files:
------------------------

LXC is made of files shipped under a few different licenses.

Anything that ends up being part of the LXC library needs to be released
under LGPLv2.1+ or a license compatible with it (though the latter will
only be accepted for cases where the code originated elsewhere and was
imported into LXC).

Language bindings for the libraries need to be released under LGPLv2.1+.

Anything else (non-libraries) needs to be Free Software and needs to be
allowed to link with LGPLv2.1+ code (if needed). LXC upstream prefers
LGPLv2.1+ or GPLv2 for those.

When introducing a new file into the project, please make sure it has a
copyright header making clear under which license it's being released
and if it doesn't match the criteria described above, please explain
your decision on the lxc-devel mailing-list when submitting your patch.

This is intended to switch over files to LGPLv2.1+ to which end we have
collected ACKs from relevant people.
/* Affected People */
Christian Brauner <christian.brauner at ubuntu.com>
Donghwa Jeong <dh48.jeong at samsung.com>

Signed-off-by: Christian Brauner <christian.brauner at ubuntu.com>
Acked-by: Donghwa Jeong <dh48.jeong at samsung.com>

  Commit: 601b35e7ac0b19adc870cab79e01d3905ef9a0b7
      https://github.com/lxc/lxc/commit/601b35e7ac0b19adc870cab79e01d3905ef9a0b7
  Author: Christian Brauner <christian.brauner at ubuntu.com>
  Date:   2019-03-03 (Sun, 03 Mar 2019)

  Changed paths:
    M src/lxc/string_utils.c

  Log Message:
  -----------
  string_utils.c: fix wrong licensing

liblxc has always been meant to be LGPLv2.1+ as reflected by the many
downstreams projects and bindings which are themselves under LGPLv2.1+ or other
licenses which would be incompatible with linking against a GPLv2+ library.

It's pretty normal for a library to be LGPL while binaries are GPL as a GPL
library would only ever be usable by other GPL-only projects, which isn't the
case for very many of the liblxc downstreams.

The issue here is really carelessness. None of those GPL headers were put there
intentionally, instead being wrongly copy/pasted from other parts of the
codebase which is indeed intended to be GPLv2+. This is also made clear in our
CONTRIBUTING file in this repository:

Licensing for new files:
------------------------

LXC is made of files shipped under a few different licenses.

Anything that ends up being part of the LXC library needs to be released
under LGPLv2.1+ or a license compatible with it (though the latter will
only be accepted for cases where the code originated elsewhere and was
imported into LXC).

Language bindings for the libraries need to be released under LGPLv2.1+.

Anything else (non-libraries) needs to be Free Software and needs to be
allowed to link with LGPLv2.1+ code (if needed). LXC upstream prefers
LGPLv2.1+ or GPLv2 for those.

When introducing a new file into the project, please make sure it has a
copyright header making clear under which license it's being released
and if it doesn't match the criteria described above, please explain
your decision on the lxc-devel mailing-list when submitting your patch.

This is intended to switch over files to LGPLv2.1+ to which end we have
collected ACKs from relevant people.
/* Affected People */
Christian Brauner <christian.brauner at ubuntu.com>
Donghwa Jeong <dh48.jeong at samsung.com>

Signed-off-by: Christian Brauner <christian.brauner at ubuntu.com>
Acked-by: Donghwa Jeong <dh48.jeong at samsung.com>

  Commit: 8690bff178f451f058ae86dc2c0722cf8b8138da
      https://github.com/lxc/lxc/commit/8690bff178f451f058ae86dc2c0722cf8b8138da
  Author: Stéphane Graber <stgraber at stgraber.org>
  Date:   2019-03-04 (Mon, 04 Mar 2019)

  Changed paths:
    M src/lxc/commands_utils.c
    M src/lxc/commands_utils.h
    M src/lxc/file_utils.c
    M src/lxc/string_utils.c

  Log Message:
  -----------
  Merge pull request #2891 from brauner/2019-03-03/update_license_headers

tree-wide: fix wrong licensing

Compare: https://github.com/lxc/lxc/compare/fff69e468f32...8690bff178f4