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#30987 - gziping man pages breaks 'npm help <topic>'
Attached to Project:
Community Packages
Opened by J Jordan (jjrdn) - Friday, 03 August 2012, 03:07 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 04 August 2012, 07:15 GMT
Opened by J Jordan (jjrdn) - Friday, 03 August 2012, 03:07 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 04 August 2012, 07:15 GMT
|
DetailsLine 60 of the PKGBUILD, the man pages are being compressed. Unfortunately npm requires the man pages to be uncompressed for the 'npm help' command to work.
See: https://github.com/isaacs/npm/blob/master/lib/help.js#L40-41 Basically npm looks for the man file without the .gz extension, and if it does not exists, it assumes that the topic does not exist and performs a search instead. To test this, run the 'npm help install' and you will see that npm does a search for 'install' when it should open the man page. If you gunzip the install.1.gz file, this command now works. Removing line 60 of the PKGBUILD should resolve this issue. |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Saturday, 04 August 2012, 07:15 GMT
Reason for closing: Fixed
Additional comments about closing: nodejs 0.8.5-1
Saturday, 04 August 2012, 07:15 GMT
Reason for closing: Fixed
Additional comments about closing: nodejs 0.8.5-1
Comment by J Jordan (jjrdn) -
Friday, 03 August 2012, 03:15 GMT
This report is for the nodejs package and the summary should begin with [nodejs 0.8.4-1]. This has been an issue since node-0.8.0-1