Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] util-linux: Set the license for util-linux-fcntl-lock to MIT
Date: Thu, 4 Apr 2024 20:02:31 +0200	[thread overview]
Message-ID: <202404041802317f92a6a4@mail.local> (raw)
In-Reply-To: <DB5PR02MB10213CCA7CB746291E72C4A07EF3C2@DB5PR02MB10213.eurprd02.prod.outlook.com>

On 04/04/2024 17:25:52+0000, Peter Kjellerstedt wrote:
> > -----Original Message-----
> > From: Alexandre Belloni <alexandre.belloni@bootlin.com>
> > Sent: den 4 april 2024 01:45
> > To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH] util-linux: Set the license for util-linux-fcntl-lock to MIT
> > 
> > Hello,
> > 
> > This caused:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4604/steps/12/logs/stdio
> > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20240403-u_hyp_wv/packages/diff-html/
> 
> Doesn't this type of breakage happen all the time for pure recipe 
> changes that affect the output if the PR server is not enabled?
> 
> > 
> > I guess we need to bump PR?
> 
> Given that RP removed all PR variables from the recipes in OE-Core (see 
> commit d4c346e8ab8f3cae25d1b01c7331ed9f6d4f96ef), I would expect that he 
> is not too keen to see them coming back...
> 

The plan is to take your patch as-is in master and if this causes reop
failures bump PR

> //Peter
> 
> > 
> > On 02/04/2024 06:56:54+0200, Peter Kjellerstedt wrote:
> > > This avoids problems if BSD-4-Clause is in INCOMPATIBLE_LICENSE since
> > > util-linux-fcntl-lock is now a dependency of run-postinsts.
> > >
> > > Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > > ---
> > >  meta/recipes-core/util-linux/util-linux.inc | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/meta/recipes-core/util-linux/util-linux.inc b/meta/recipes-core/util-linux/util-linux.inc
> > > index f4b547215e..d506783f9a 100644
> > > --- a/meta/recipes-core/util-linux/util-linux.inc
> > > +++ b/meta/recipes-core/util-linux/util-linux.inc
> > > @@ -7,6 +7,7 @@ disk partitioning, kernel message management, filesystem creation, and system lo
> > >  SECTION = "base"
> > >
> > >  LICENSE = "GPL-1.0-or-later & GPL-2.0-or-later & LGPL-2.1-or-later & BSD-2-Clause & BSD-3-Clause & BSD-4-Clause & MIT"
> > > +LICENSE:${PN}-fcntl-lock = "MIT"
> > >  LICENSE:${PN}-fdisk = "GPL-1.0-or-later"
> > >  LICENSE:${PN}-libblkid = "LGPL-2.1-or-later"
> > >  LICENSE:${PN}-libfdisk = "LGPL-2.1-or-later"
> 

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2024-04-04 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02  4:56 [PATCH] util-linux: Set the license for util-linux-fcntl-lock to MIT Peter Kjellerstedt
2024-04-03 23:44 ` [OE-core] " Alexandre Belloni
2024-04-04 17:25   ` Peter Kjellerstedt
2024-04-04 18:02     ` Alexandre Belloni [this message]
2024-04-04 20:22     ` Richard Purdie

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=202404041802317f92a6a4@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox