Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27260 - [nodejs] Man pages missing for npm
Attached to Project:
Community Packages
Opened by Daniel Freedman (azakus) - Saturday, 26 November 2011, 05:48 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 02 December 2011, 10:14 GMT
Opened by Daniel Freedman (azakus) - Saturday, 26 November 2011, 05:48 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 02 December 2011, 10:14 GMT
|
DetailsDescription:
npm documentation was not generated The man pages are used by npm for npm's own help, so missing them means that npm errors out when run without arguments or as npm help. Additional info: * nodejs v0.6.3 Steps to reproduce: * Install nodejs v0.6.3 * run "npm" |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Friday, 02 December 2011, 10:14 GMT
Reason for closing: Fixed
Additional comments about closing: nodejs 0.6.4-1
Friday, 02 December 2011, 10:14 GMT
Reason for closing: Fixed
Additional comments about closing: nodejs 0.6.4-1
upstream knows about this bug, this is not a packaging issue.
Guess I must not have gotten all the traces of the npm v1.0.106 man pages out of there first.
Thanks for checking!