All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Markus Volk <f_l_k@t-online.de>,
	openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] vte: upgrade 2.72.2 -> 2.74.0
Date: Tue, 19 Sep 2023 19:57:22 +0200	[thread overview]
Message-ID: <20230919175722c6907581@mail.local> (raw)
In-Reply-To: <CANNYZj-g6JvuMm3pRHJLHxhkVn_gw__E29iLksd8RWGSvdywew@mail.gmail.com>

On 19/09/2023 18:30:23+0200, Alexander Kanavin wrote:
> On Tue, 19 Sept 2023 at 17:59, Alexandre Belloni
> <alexandre.belloni@bootlin.com> wrote:
> > > Having gpl3-only recipes in core is not a problem. Ability to build
> > > basic images without gpl3 items is tested, since that kind of thing is
> >
> > I don't think we test this anymore.
> 
> We do:
> https://git.yoctoproject.org/poky/tree/meta/lib/oeqa/selftest/cases/incompatible_lic.py?h=master-next#n135
> (the test in NoGPL3InImagesTests class)
> 
> You were probably thinking of meta-gplv2 tests.

Yeah, I thought we dropped both at the same time.


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


      reply	other threads:[~2023-09-19 17:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 11:49 [oe-core][PATCH] vte: upgrade 2.72.2 -> 2.74.0 Markus Volk
2023-09-19 12:02 ` Alexander Kanavin
2023-09-19 12:12   ` Markus Volk
     [not found]   ` <17864BB006CFEE21.29111@lists.openembedded.org>
2023-09-19 12:17     ` Markus Volk
2023-09-19 12:34   ` Markus Volk
2023-09-19 13:06   ` Markus Volk
2023-09-19 13:20     ` Alexander Kanavin
2023-09-19 13:23       ` Markus Volk
2023-09-19 13:24         ` Alexander Kanavin
2023-09-19 15:59       ` Alexandre Belloni
2023-09-19 16:30         ` Alexander Kanavin
2023-09-19 17:57           ` Alexandre Belloni [this message]

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=20230919175722c6907581@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=alex.kanavin@gmail.com \
    --cc=f_l_k@t-online.de \
    --cc=openembedded-core@lists.openembedded.org \
    /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.