Different Binary Name in 12.04 and 12.10 (name conflict with "node" package)

Bug #1069903 reported by Ma Hsiao-chun
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Node JS
New
Undecided
Unassigned
node (Ubuntu)
Invalid
Undecided
Unassigned
nodejs (Debian)
Fix Released
Unknown
nodejs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nodejs (Ubuntu):
status: New → Confirmed
Revision history for this message
László Monda (mondalaci) wrote :

I think this is a huge mess with a long history - see http://lists.debian.org/debian-devel-announce/2012/07/msg00002.html

The nodejs package should definitely contain the node binary because node libraries depend on it. Does anyone argue that?

Why has this change happened?

Revision history for this message
Ben Kuhn (ben-s-kuhn) wrote :

Workaround:

sudo apt-get install nodejs-legacy

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

This seems to be fixed in Ubuntu according to the referred resolution above.

Changed in nodejs (Ubuntu):
status: Confirmed → Fix Released
summary: - Different Binary Name in 12.04 and 12.10
+ Different Binary Name in 12.04 and 12.10 (name conflict with "node"
+ package)
Changed in node (Ubuntu):
status: New → Confirmed
Changed in nodejs (Debian):
status: Unknown → Fix Released
Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

I opened an upstream ticket for supporting "nodejs" binary: https://github.com/joyent/node/issues/4772

Changed in node (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.