Last modified: 2014-08-28 13:51:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T71079, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69079 - Upgrade node and npm on Tool Labs
Upgrade node and npm on Tool Labs
Status: RESOLVED DUPLICATE of bug 70120
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Marc A. Pelletier
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-03 19:47 UTC by Dan Michael Heggø
Modified: 2014-08-28 13:51 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Dan Michael Heggø 2014-08-03 19:47:50 UTC
(partly copy-paste from http://comments.gmane.org/gmane.org.wikimedia.labs/2780)

The version of npm/node currently installed is no longer supported, and npm is not even working.

npm used to have a self-signed certificate that it verified client-side using a signature. In newer versions they now have a proper certificate and node/npm were updated to account for this. Minor releases have been made to node 0.8 and npm to support the new certificates. The old ones are no longer valid as of February 2014.

Details at
http://blog.npmjs.org/post/78165272245/more-help-with-self-signed-cert-in-chain-and-npm
Comment 1 Yuvi Panda 2014-08-03 19:50:58 UTC
Hmm, I suspect we'll have to find a newer package of nodejs for precise and get it on toollabs.

Other option is to setup a bunch of nodes that run trusty, and let tool authors specify that their tools should run there instead of the precise hosts.
Comment 2 Tim Landscheidt 2014-08-28 13:51:50 UTC

*** This bug has been marked as a duplicate of bug 70120 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links