glibc: correct license

From: Peter Marko <peter.marko@siemens.com>

The license per https://www.gnu.org/software/libc/ is LGPL-2.1-or-later.
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=273a835fe7c685cc54266bb8b502787bad5e9bae
converted last LGPL-2.1-only references.

License-Update: correction

Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
 meta/recipes-core/glibc/glibc-common.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

On Sun, May 5, 2024 at 2:18 AM Peter Marko via lists.openembedded.org
<peter.marko=siemens.com@lists.openembedded.org> wrote:

> From: Peter Marko <peter.marko@siemens.com>
>
> The license per https://www.gnu.org/software/libc/ is LGPL-2.1-or-later.
>
> https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=273a835fe7c685cc54266bb8b502787bad5e9bae
> converted last LGPL-2.1-only references.
>
> License-Update: correction
>

This should reflect reason but overall the patch is ok


> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> ---
>  meta/recipes-core/glibc/glibc-common.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/glibc/glibc-common.inc
> b/meta/recipes-core/glibc/glibc-common.inc
> index b9516e77f0..91a3f5bcd5 100644
> --- a/meta/recipes-core/glibc/glibc-common.inc
> +++ b/meta/recipes-core/glibc/glibc-common.inc
> @@ -2,7 +2,7 @@ SUMMARY = "GLIBC (GNU C Library)"
>  DESCRIPTION = "The GNU C Library is used as the system C library in most
> systems with the Linux kernel."
>  HOMEPAGE = "http://www.gnu.org/software/libc/libc.html"
>  SECTION = "libs"
> -LICENSE = "GPL-2.0-only & LGPL-2.1-only"
> +LICENSE = "GPL-2.0-only & LGPL-2.1-or-later"
>
>  LIC_FILES_CHKSUM ?= "file://LICENSES;md5=f77e878d320e99e94ae9a4aea7f491d1
> \
>        file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> --
> 2.30.2
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#199017):
> https://lists.openembedded.org/g/openembedded-core/message/199017
> Mute This Topic: https://lists.openembedded.org/mt/105919323/1997914
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

From: Khem Raj <raj.khem@gmail.com> 
Sent: Sunday, May 5, 2024 21:22
To: Marko, Peter (ADV D EU SK BFS1) <Peter.Marko@siemens.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] glibc: correct license

> On Sun, May 5, 2024 at 2:18 AM Peter Marko via http://lists.openembedded.org <peter.marko=mailto:siemens.com@lists.openembedded.org> wrote:
> > From: Peter Marko <mailto:peter.marko@siemens.com>
> >
> > The license per https://www.gnu.org/software/libc/ is LGPL-2.1-or-later.
> > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=273a835fe7c685cc54266bb8b502787bad5e9bae
> > converted last LGPL-2.1-only references.
> >
> > License-Update: correction
>
> This should reflect reason but overall the patch is ok
>

Could you please be more specific what should I write?
The long reason is written above the License-Update field, I just added the field to satisfy the patch checker bot.
Putting the whole text to this field doesn't look right.

I don't know the history of glibc license to be able to assess if they migrated recently or if these were just wrongly committed licenses.
I just noticed the commit when updating glibc to the latest hash and decided to correct the recipe LICENSE field according to this hint.
So "correction" looks to me like a good short statement wrt the recipe LICENSE field.

Thanks,
  Peter

On Sun, May 5, 2024 at 1:43 PM Marko, Peter <Peter.Marko@siemens.com> wrote:
>
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Sunday, May 5, 2024 21:22
> To: Marko, Peter (ADV D EU SK BFS1) <Peter.Marko@siemens.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][PATCH] glibc: correct license
>
> > On Sun, May 5, 2024 at 2:18 AM Peter Marko via http://lists.openembedded.org <peter.marko=mailto:siemens.com@lists.openembedded.org> wrote:
> > > From: Peter Marko <mailto:peter.marko@siemens.com>
> > >
> > > The license per https://www.gnu.org/software/libc/ is LGPL-2.1-or-later.
> > > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=273a835fe7c685cc54266bb8b502787bad5e9bae
> > > converted last LGPL-2.1-only references.
> > >
> > > License-Update: correction
> >
> > This should reflect reason but overall the patch is ok
> >
>
> Could you please be more specific what should I write?

its can be changed/corrected from X to Y then point to supporting
links you have cited as links using [1] [2] etc.

> The long reason is written above the License-Update field, I just added the field to satisfy the patch checker bot.
> Putting the whole text to this field doesn't look right.
>
> I don't know the history of glibc license to be able to assess if they migrated recently or if these were just wrongly committed licenses.
> I just noticed the commit when updating glibc to the latest hash and decided to correct the recipe LICENSE field according to this hint.
> So "correction" looks to me like a good short statement wrt the recipe LICENSE field.
>
> Thanks,
>   Peter