LogoopenSUSE Build Service > Projects > devel:languages:nodejs > nodejs
Sign Up | Log In

Node JS

Evented I/O for V8 JavaScript

http://nodejs.org

Source Files (show merged sources derived from linked package)

Filename Size Changed Actions
node-gyp-addon-gypi.patch 3.03 KB 9 months ago Download File
node-v5.9.1.tar.xz 12.6 MB 2 months ago
nodejs-libpath.patch 2.18 KB 3 months ago Download File
nodejs-sle11-python26-check_output.patch 1.29 KB 5 months ago Download File
nodejs.changes 41 KB 2 months ago Download File
nodejs.spec 7.48 KB 2 months ago Download File
support-arm64-build.patch 777 Bytes 3 months ago Download File

Latest Revision

buildservice-autocommit accepted request 380445 2 months ago (revision 105)
baserev update by copy to link target

Comments for devel:languages:nodejs (21)

Brenton Horne fusion809 wrote 3 months ago

This package is out of date. Version 5.6.0 is out.

Marguerite Su MargueriteSu wrote 3 months ago

@fusion809, thanks, update is on the way

Andrei Dziahel develop7 wrote 3 months ago

it seems updated nodejs is broken for me:

$ npm module.js:462 if fs.exists('/usr/lib64', fs.F_OK, function(err) { ^^

SyntaxError: Unexpected identifier at runInThisContext (node.js:904:18) at NativeModule.compile (node.js:988:14) at Function.NativeModule.require (node.js:937:18) at startup (node.js:99:35) at node.js:1001:3

Please consider updating to v5.7.0

Andrei Dziahel develop7 wrote 3 months ago
$  npm 
module.js:462
  if fs.exists('/usr/lib64', fs.F_OK, function(err) {
     ^^

SyntaxError: Unexpected identifier
    at runInThisContext (node.js:904:18)
    at NativeModule.compile (node.js:988:14)
    at Function.NativeModule.require (node.js:937:18)
    at startup (node.js:99:35)
    at node.js:1001:3
Andrei Dziahel develop7 wrote 3 months ago

@MargueriteSu oh, the error above doesn't have to do with update, it's caused by syntax error in nodejs-libpath.patch.

Brenton Horne fusion809 wrote 3 months ago

Ah, well I can confirm I am getting the same error.

Andrei Dziahel develop7 wrote 3 months ago

I've submitted https://build.opensuse.org/request/show/361056 that enables build-time tests which will prevent such issues in the future. I didn't fix the patch, because it has syntax error in module.js-related hunk.

Brenton Horne fusion809 wrote 3 months ago

I've made the bump to 5.7.0 successfully in my own branch of this repo https://build.opensuse.org/package/show/home:fusion809:branches:devel:languages:nodejs/nodejs. The only problem that I don't know how to fix is the arm patch.

Martin Fischer gabel wrote 3 months ago

Any news for an update to 5.7.0 to fix the issues below?

Julian Bäume j_ohny_b wrote 3 months ago

an update to 5.7 will not fix this issue. This issue is because of a broken patch. I'm currently testing a fix, SR should follow in a few minutes

Martin Fischer gabel wrote 3 months ago

OK, I thought the broken patch would be reverted by upgrading to 5.7.0 from the original sources.

Julian Bäume j_ohny_b wrote 3 months ago

nope, you need synchronous code, in this case, or path will be defined to late. In your case, also, the path variable will not be available in the correct scope and can therefore not be used later. I opened https://build.opensuse.org/request/show/361114 - at least it works fine on my machine, now.

Marguerite Su MargueriteSu wrote 3 months ago

ok. I merged your patch to my 5.7.0 branch. thanks.

Kristoffer Gronlund KGronlund wrote 3 months ago

Why revoke the submission that fixes the problem in 5.6.0? Right now hawk is broken since the nodejs which is in Factory is broken.

Julian Bäume j_ohny_b wrote 3 months ago

You are right. I opened a new SR, since the 5.7.0 update might still take a while.

Julian Bäume j_ohny_b wrote 3 months ago

FYI, i brought up this issue on the osf ML, yesterday, because the broken state got merged into factory despite my warning, that it's broken. No answer on this subject, yet.

Kristoffer Gronlund KGronlund wrote 3 months ago

Thank you.

Marguerite Su MargueriteSu wrote 3 months ago

5.7.0 is ready, with a failing test:

=== release test-tls-server-verify ===
[  284s] Path: parallel/test-tls-server-verify
[  284s] 0 0   connecting with agent1
[  284s] 0 1   connecting with agent2
[  284s] 0 2   connecting with agent3
[  284s] 0 3   connecting with nocert
[  284s] 1 0   connecting with agent1
[  284s] 1 1   connecting with agent2
[  284s] 1 2   connecting with agent3
[  284s] 1 3   connecting with nocert
[  284s] 2 0   connecting with agent1
[  284s] 0 Running 'Do not request certs. Everyone is unauthorized.'
[  284s] 1 Running 'Allow both authed and unauthed connections with CA1'
[  284s] 0 - unauthed connection: null
[  284s] 0 - unauthed connection: null
[  284s] 0 - unauthed connection: null
[  284s] 0 - unauthed connection: null
[  284s] 1 - unauthed connection: UNABLE_TO_GET_ISSUER_CERT
[  284s] 0 0   * unauthed
[  284s] 1 - unauthed connection: UNABLE_TO_GET_ISSUER_CERT
[  284s] 0 1   * unauthed
[  284s] 1 - unauthed connection: UNABLE_TO_GET_ISSUER_CERT
[  284s] 0 2   * unauthed
[  284s] 0 3   * unauthed
[  284s] 2 Running 'Do not request certs at connection. Do that later'
[  284s] 1 2   * unauthed
[  284s] 1 1   * unauthed
[  284s] 1 0   * unauthed
[  284s] 1 - unauthed connection: UNABLE_TO_GET_ISSUER_CERT
[  284s] 
[  284s] assert.js:89
[  284s]   throw new assert.AssertionError({
[  284s]   ^
[  284s] AssertionError: 1 0 agent1 authed is false but should have been true
[  284s]     at ChildProcess.

any one can resolve this?

Julian Bäume j_ohny_b wrote 3 months ago

Yes, that is, why tests were disabled in the first place. The tests need a network connection to run, but there is none available during build time on OBS. The best case would be to just deactivate the tests needing a network connection. A kind of working solution (but quite fragile, as we just saw) is to just not run them on OBS, at all.

Marguerite Su MargueriteSu wrote 3 months ago

yep...I'll strip that test