All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <yoann.congal@smile.fr>, <bitbake-devel@lists.openembedded.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Thomas Perrot" <thomas.perrot@bootlin.com>,
	"Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>,
	"Richard Purdie" <richard.purdie@linuxfoundation.org>
Subject: Re: [bitbake-devel] [2.18][PATCH 0/2] fetch/{npm,npmsw}: fix security issue and re-enable fetchers
Date: Tue, 25 Aug 2026 15:17:13 +0200	[thread overview]
Message-ID: <DKY1XVP2EL02.RX322WV88ALR@bootlin.com> (raw)
In-Reply-To: <DKY1SVKSA25G.1G4STPIKU99KZ@smile.fr>

Hi Yoann,

On Tue Aug 25, 2026 at 3:10 PM CEST, Yoann Congal via lists.openembedded.org wrote:
> Hello,
>
> On Tue Aug 25, 2026 at 3:02 PM CEST, Antonin Godard via lists.openembedded.org wrote:
>> This is a proposal to backport patches re-enabling the npm and npmsw
>> fetcher on 2.18 (Wrynose). The two patches from this series are simple
>> cherry-picks, and had no conflicts applying.
>>
>> Applying these two patches locally is also fine to me, but as this seems
>> to be working as-is I figured this might be helpful to others - up to the
>> maintainer(s) to decide.
>
> I understand this is tempting but that'd be a feature addition from
> wrynose point of view and so, unacceptable per stable policy.
>
> Without exception to the rules, we'll have to live with wrynose not
> having a NPM fetcher.

Understood, and fine by me. You'll have a link to share to others wondering
about it now. :)

Thanks for the swift answer!
Antonin


      reply	other threads:[~2026-08-25 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 13:02 [2.18][PATCH 0/2] fetch/{npm,npmsw}: fix security issue and re-enable fetchers Antonin Godard
2026-08-25 13:02 ` [2.18][PATCH 1/2] fetch/{npm,npmsw}: re-enable fetchers now that checksums come from SRC_URI Antonin Godard
2026-08-25 13:02 ` [2.18][PATCH 2/2] tests/fetch: restore and extend npm/npmsw test coverage Antonin Godard
2026-08-25 13:10 ` [bitbake-devel] [2.18][PATCH 0/2] fetch/{npm,npmsw}: fix security issue and re-enable fetchers Yoann Congal
2026-08-25 13:17   ` Antonin Godard [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=DKY1XVP2EL02.RX322WV88ALR@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=thomas.perrot@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yoann.congal@smile.fr \
    /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.