[Buildroot] [autobuild.buildroot.net] Build results for 2016-02-14

[Martin Bark]

Thomas,


On 15 February 2016 at 20:48, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Hello Martin,
>
> On Mon, 15 Feb 2016 15:10:44 +0000, Martin Bark wrote:
>
>> >       mipsel |              host-nodejs-5.5.0 | NOK | http://autobuild.buildroot.net/results/87e9bbbb36f7fe4868d238ef6a7b72eb8cca7052/
>> >       x86_64 |              host-nodejs-5.5.0 | NOK | http://autobuild.buildroot.net/results/f748c0956f71a7857d5cc9ae7bfe3c14357a078a/
>>
>> I was able to reproduce the error in host-nodejs and i can confirm my
>> patch to update to node 5.6.0
>> (http://patchwork.ozlabs.org/patch/581620/) fixes this.  Specifically
>> the update i made to
>> 0003-Use-a-python-variable-instead-of-hardcoding-Python.patch.
>
> Thanks for looking into this issue. However, at this point, we cannot
> merge a bump of nodejs to 5.6.0 to our master branch, because this
> branch is "frozen" in terms of version bumps, package additions and
> major changes.
>
> Do you think  it is possible to have instead two patches, one that adds
> the 0003-Use-a-python-variable-instead-of-hardcoding-Python.patch fix
> to NodeJS 5.5.0, so that I can apply it on master, and another patch on
> top of it that bumps NodeJS to 5.6.0, which I would apply on our next
> branch ?

I have split the update to
0003-Use-a-python-variable-instead-of-hardcoding-Python.patch into a
separate patch and sent out an update patch set. The one you want to
fix this issue is http://patchwork.ozlabs.org/patch/583333/

Thanks

Martin

>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com