Bug 10691 - [Update request] - nodejs from very old stable to latest stable available for Mageia 2
Summary: [Update request] - nodejs from very old stable to latest stable available for...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: has_procedure MGA2-32-ok MGA2-64-ok
Keywords: validated_update
Depends on:
Blocks: 8567
  Show dependency treegraph
 
Reported: 2013-07-04 18:55 CEST by Damien Lallement
Modified: 2013-07-09 21:51 CEST (History)
3 users (show)

See Also:
Source RPM: nodejs-0.8.25-1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Damien Lallement 2013-07-04 18:55:15 CEST
Advisory
====================
This update of nodejs is to provide a better release as the one in core/release if very outdated. Moreover, this package now use bundled v8 as requested to avoid using buggy v8 package (mga#8567) and now, we are not using bundled deps (only v8) as before.

Packages
====================
nodejs-0.8.25-1.mga2.src.rpm

Steps to Reproduce
====================
- Install Mageia 3
- Install nodejs (v0.4.12, from 2011.09.15) from "core/release"
- Use it if you know how it works! [1]
- Install nodejs (v0.8.25) from "core/updates_testing"
- Use it and check it still/better works! [2]

[1]
Example on "how to check if installation went well":
$ node -e "console.log(process.versions)"
$ node -e "console.log('Hello World')"

[2]
Example on "how to check with 0.8.x:
first
# npm install azure-cli -g
then
$ azure --help

Reproducible: 

Steps to Reproduce:
Damien Lallement 2013-07-04 18:56:24 CEST

Blocks: (none) => 8567

Comment 1 claire robinson 2013-07-04 19:45:33 CEST
Could you list rpms again too please Damien, is it just nodejs rpm?
Comment 2 martyn vidler 2013-07-07 13:43:44 CEST
MGA2 32 Testing

To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Release")
  nodejs                         0.4.12       1.mga2        i586    
  v8                             3.3.10       1.mga2        i586    
5.8MB of additional disk space will be used.
1.5MB of packages will be retrieved.
Proceed with the installation of the 2 packages? (Y/n) y


    $MIRRORLIST: media/core/release/v8-3.3.10-1.mga2.i586.rpm
    $MIRRORLIST: media/core/release/nodejs-0.4.12-1.mga2.i586.rpm                                                           
installing v8-3.3.10-1.mga2.i586.rpm nodejs-0.4.12-1.mga2.i586.rpm from /var/cache/urpmi/rpms                               
Preparing...                     ##########################################################################################
      1/2: v8                    ##########################################################################################
      2/2: nodejs

created hello world
Created local web server

Although being copy/paste from a web page, to try, I,m not a programmer..

removed nodejs-0.4.12-1

installed nodejs-0.8.25-1.mga2

created same programs as above all ran the same

Ran 
npm install azure-cli -g

azure --help
 Produced help files.

CC: (none) => martynvidler
Whiteboard: (none) => MGA2-32-ok

Comment 3 martyn vidler 2013-07-07 14:55:05 CEST
MGA2 64

Tested the same as comment 2

All ran exactly the same 

Validate Advisory

Whiteboard: MGA2-32-ok => MGA2-32-ok MGA2-64-ok

Comment 4 claire robinson 2013-07-07 15:04:35 CEST
Advisory uploaded.

Whiteboard: MGA2-32-ok MGA2-64-ok => has_procedure MGA2-32-ok MGA2-64-ok

Comment 5 claire robinson 2013-07-08 10:46:45 CEST
Confirmed martyn's testing.

Removed azure-cli with..
# npm uninstall azure-cli

Validating

Could sysadmin please push from 2 core/updates_testing to core/updates

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 6 Thomas Backlund 2013-07-09 21:51:22 CEST
Update pushed:
nodejs-0.8.25-1.mga2

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED


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