Jonas,

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

2017-03-17 9:47 GMT+01:00 Jonas Smedegaard <jo...@jones.dk>:

> 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

Reply via email to