Re: [Pkg-javascript-devel] Fwd: Revive NodeJS on armel (forwardport jessie src-package)

[Jérémy Lal]

2017-03-18 8:29 GMT+01:00 Jonas Smedegaard :
> Quoting Sven Giermann (2017-03-17 22:32:54)
>> 2017-03-17 11:22 GMT+01:00 Jonas Smedegaard :
>>
>>> How about fresh install of _Debian_ wheezy (not Emdebian wheezy)?
>>>
>>
>> That's my main problem:
>> I am unable to install wheezy or jessie, passing all tests supplied
>> with the source package!
>
> My point is: How about _not_ rebuild (backport or forwardport) Nodejs
> package at all, but instead rebase system ("side-grade" - or rather
> reinstall) from unmaintained Emdebian to LTS-team-maintained Debian.
>
>
>> I was trying to stress that on my initial post, only writing the
>> initial intent for better understanding.
>
> I understand that your initial post was about forward-porting nodejs -
> i.e. rebuilding an older nodejs package on a newer Debian.
>
> I did not address your question, but side-stepped it by questioning the
> _premise_ for your question - that it is "time to change to newer
> distribution" - and consequently explore a _different_ and likely far
> less complex path not involving package recompilation.
>
> Perfectly fine if what you want to do is recompile Nodejs.  You need not
> defend your premise, I only questioned it in case your limited scope was
> unintentional.
>
> [details on rebuilding Nodejs snipped - left for others to discuss]
>
>
>>> Depending on your needs (is brand recognition a need for you?), I
>>> recommend you to consider the OSHW boards from Olimex.
>>>
>>
>> I'm fine with everything that does not cost to much and is easy to
>> purchase.
>> Is anyone able to pass all nodejs build tests on that platform?
>
> Yes: LIME2 is an armhf device, and all tests enabled in the Debian
> packaging of Nodejs passes for armhf, if that is what you mean.  Status
> for archs succeeding build (including testsuite) is here:
> https://buildd.debian.org/status/package.php?p=nodejs
>
> I believe the full _upstream_ testsuite does not succeed on _any_ Debian
> arch.  But Jéremy knows more intimately about that.

Right, a handful of upstream tests will fail - sometimes or always
depending on the test.
If you have a low number of test failures, you can assume you have a
working installation of nodejs :)

Jérémy


-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Fwd: Revive NodeJS on armel (forwardport jessie src-package)

[Jonas Smedegaard]

Quoting Sven Giermann (2017-03-17 22:32:54)
> 2017-03-17 11:22 GMT+01:00 Jonas Smedegaard :
>
>> How about fresh install of _Debian_ wheezy (not Emdebian wheezy)?
>>
> 
> That's my main problem:
> I am unable to install wheezy or jessie, passing all tests supplied 
> with the source package!

My point is: How about _not_ rebuild (backport or forwardport) Nodejs 
package at all, but instead rebase system ("side-grade" - or rather 
reinstall) from unmaintained Emdebian to LTS-team-maintained Debian.


> I was trying to stress that on my initial post, only writing the 
> initial intent for better understanding.

I understand that your initial post was about forward-porting nodejs - 
i.e. rebuilding an older nodejs package on a newer Debian.

I did not address your question, but side-stepped it by questioning the 
_premise_ for your question - that it is "time to change to newer 
distribution" - and consequently explore a _different_ and likely far 
less complex path not involving package recompilation.

Perfectly fine if what you want to do is recompile Nodejs.  You need not 
defend your premise, I only questioned it in case your limited scope was 
unintentional.

[details on rebuilding Nodejs snipped - left for others to discuss]


>> Depending on your needs (is brand recognition a need for you?), I 
>> recommend you to consider the OSHW boards from Olimex.
>>
>
> I'm fine with everything that does not cost to much and is easy to 
> purchase.
> Is anyone able to pass all nodejs build tests on that platform?

Yes: LIME2 is an armhf device, and all tests enabled in the Debian 
packaging of Nodejs passes for armhf, if that is what you mean.  Status 
for archs succeeding build (including testsuite) is here: 
https://buildd.debian.org/status/package.php?p=nodejs

I believe the full _upstream_ testsuite does not succeed on _any_ Debian 
arch.  But Jéremy knows more intimately about that.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Fwd: Revive NodeJS on armel (forwardport jessie src-package)

[Sven Giermann]

2017-03-17 11:22 GMT+01:00 Jonas Smedegaard :

> How about fresh install of _Debian_ wheezy (not Emdebian wheezy)?
>

That's my main problem:
I am unable to install wheezy or jessie, passing all tests supplied with
the source package!

I was trying to stress that on my initial post, only writing the initial
intent for better understanding.
Before I try to find the best solution for me, I'm looking for a way to
install something, that passes the build-tests on my platform.

I tried wheezy and jessie with their appropriate nodejs source, both failed
several tests.
I repeated at least the jessie test on armhf platform, which also failed.
So it would be nice to find someone that is able to pass all 'test-simple'
targets on any platform (i386, amd64, armel, armhf), to have a valid
starting point for me. (I didn't try the Intel platforms so far, but assume
they fail as well)

After finding a solid (wheezy or jessie) base, I might continue to port
that to libssl1.0.2 or to static link to libssl1.0.1 - that's why I asked
for a guide for static linking to openssl.

Would it be an option for you to backport those parts (as opposed to
> forward-port Nodejs which I fear is quite more complex)?
>

Again, for now nodejs tests seem to fail on older releases too.

Raspberry Pi is arguably _popular_ but certainly not a standard.
>

Sorry for that - I definitely meant "popular", which is a great advantage
searching for solutions...

Depending on your needs (is brand recognition a need for you?), I
> recommend you to consider the OSHW boards from Olimex.
>

I'm fine with everything that does not cost to much and is easy to purchase.
Is anyone able to pass all nodejs build tests on that platform?


Sven
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Fwd: Revive NodeJS on armel (forwardport jessie src-package)

[Sven Giermann]

Jonas,

thanks for your quick reply and the interest in my "problem". :-)

2017-03-17 9:47 GMT+01:00 Jonas Smedegaard :

> Could you please elaborate on the "time to change to newer distribution"
> part?
>
> If reason for the change is improved security support, then it seems you
> are somewhat defeating that by running (exposed to the network, I guess)
> code which no longer receives security updates.
>

Yes, I'm well aware of that. But until now, it's only exposed to my LAN.
The reason for looking at newer distributions is the need for a clean
reinstallation after trying different packages on my production system, I
don't need any more. I'd like to renew my installation from scratch, which
(of course) could still be done with emDebian wheezy, but I'm not sure how
long the mirrors will still be active. Yes, I might archive a pure base
installation - but I'd feel more comfortable with a supported distribution,
keeping only NodeJS in an unsupported state.

Apart from that, I fear that even wheezy's backport of v0.10.29 does not
pass all tests, so I started to focus on the current stable distribution
(jessie). But as this fails to build 'test-simple', I wanted to get some
support from others who know, what they are doing...

Further, there are many more components like OWFS and EBUSD running on that
system - which I'd like to keep more current.

Last but not least, the most obvious solution would be to retire my armel
device and get a standard Raspberry Pi or similiar - but I get comparable
test failures on stable (jessie) running armhf, too.
So I thought, it's time to shed some light on this...


Sven
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel