From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/nodejs: bump version to 5.6.0
Date: Wed, 10 Feb 2016 22:29:30 +0100 [thread overview]
Message-ID: <56BBABBA.70508@mind.be> (raw)
In-Reply-To: <1455137405-20582-1-git-send-email-martin@barkynet.com>
On 10-02-16 21:50, Martin Bark wrote:
> This is an important security release. See
> https://nodejs.org/en/blog/release/v5.6.0/ for further details
It's a security release, but it also carries a bunch of development work. So
I'm not sure if it is 2016.02 material... Still, it's early in the cycle.
>
> Patches from 5.5.0 have been copied over except for
> 0003-Use-a-python-variable-instead-of-hardcoding-Python.patch which has
> been updated to include some more python variables.
That patch looks like it should be upstreamable. Has anyone tried?
>
> Signed-off-by: Martin Bark <martin@barkynet.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
> ---
> ...01-Remove-dependency-on-Python-bz2-module.patch | 0
> .../0002-gyp-force-link-command-to-use-CXX.patch | 0
> ...hon-variable-instead-of-hardcoding-Python.patch | 65 +++++++++++++---------
> .../0004-Fix-va_list-not-declared.patch | 0
> .../0005-Fix-support-for-uClibc-ng.patch | 0
> package/nodejs/Config.in | 2 +-
> package/nodejs/nodejs.hash | 4 +-
> 7 files changed, 43 insertions(+), 28 deletions(-)
> rename package/nodejs/{5.5.0 => 5.6.0}/0001-Remove-dependency-on-Python-bz2-module.patch (100%)
> rename package/nodejs/{5.5.0 => 5.6.0}/0002-gyp-force-link-command-to-use-CXX.patch (100%)
> rename package/nodejs/{5.5.0 => 5.6.0}/0003-Use-a-python-variable-instead-of-hardcoding-Python.patch (79%)
> rename package/nodejs/{5.5.0 => 5.6.0}/0004-Fix-va_list-not-declared.patch (100%)
> rename package/nodejs/{5.5.0 => 5.6.0}/0005-Fix-support-for-uClibc-ng.patch (100%)
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2016-02-10 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 20:50 [Buildroot] [PATCH 1/1] package/nodejs: bump version to 5.6.0 Martin Bark
2016-02-10 21:29 ` Arnout Vandecappelle [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=56BBABBA.70508@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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