Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Martin Bark <martin@barkynet.com>,
	Daniel Price <daniel.price@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/nodejs: bump to version 14.18.2
Date: Wed, 26 Jan 2022 15:40:21 +0100	[thread overview]
Message-ID: <87r18uh86i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20211231100725.3662078-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Fri, 31 Dec 2021 11:07:25 +0100")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > This bump will fix the following build failure raised since bump of
 > python3 to version 3.10.1 in commit
 > 25b1fc2898d68ddf2674b14c738045875fc5a2dc:

 > Please use python3.9 or python3.8 or python3.7 or python3.6 or python3.5 or python2.7.
 > 	/usr/bin/python3.7 ./configure
 > 	/usr/bin/python3.5 ./configure
 > 	/home/peko/autobuild/instance-1/output-1/host/bin/python2.7 ./configure
 > Node.js configure: Found Python 3.10.1...

 > https://github.com/nodejs/node/releases/tag/v14.18.2

 > Fixes:
 >  - http://autobuild.buildroot.org/results/9e2ebb9c3681ec0485eaa042fa838c8ee62f649b

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Committed to 2021.11.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-01-26 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 10:07 [Buildroot] [PATCH 1/1] package/nodejs: bump to version 14.18.2 Fabrice Fontaine
2021-12-31 23:40 ` James Hilliard
2022-01-01 10:28 ` Yann E. MORIN
2022-01-26 14:40 ` Peter Korsgaard [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=87r18uh86i.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=daniel.price@gmail.com \
    --cc=fontaine.fabrice@gmail.com \
    --cc=martin@barkynet.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