Spec URL: http://www.metal3d.org/rpms/node.js.spec SRPM URL: http://www.metal3d.org/rpms/node.js-0.2.6-1.fc14.src.rpm Description: Node.js use V8 javascript Engine (used in Webkit). It's an engine to develop server side net application (http, socket...) It has severals modules to help to develop multi-clients applications, HTTP servers... etc... Koji said me that's ok, but some "warnings" appears with rpmlint node.js.x86_64: W: non-standard-group Development node.js.x86_64: W: only-non-binary-in-usr-lib node.js.x86_64: E: script-without-shebang /usr/lib64/node/wafadmin/Tools/node_addon.py node.js.x86_64: E: script-without-shebang /usr/lib64/node/wafadmin/pproc.py node.js.x86_64: E: script-without-shebang /usr/lib64/node/wafadmin/ansiterm.py node.js.x86_64: W: no-manual-page-for-binary node-waf node.js.x86_64: W: no-manual-page-for-binary node-repl node.js-debuginfo.x86_64: W: spelling-error Summary(en_US) js -> dis, ks, ja node.js-debuginfo.x86_64: W: spelling-error %description -l en_US js -> dis, ks, ja node.js-devel.x86_64: W: spelling-error Summary(en_US) Developpement -> Developmental, Development, Developer node.js-devel.x86_64: W: spelling-error Summary(en_US) js -> dis, ks, ja node.js-devel.x86_64: W: spelling-error %description -l en_US javascript -> java script, java-script, JavaScript node.js-devel.x86_64: W: spelling-error %description -l en_US developpement -> developmental, development, developer node.js-devel.x86_64: W: non-standard-group Developpement node.js-devel.x86_64: W: no-documentation 3 packages and 0 specfiles checked; 3 errors, 12 warnings. I will correct errors and "Developpement" groupe name... but can you take a look on LICENSE text because it uses lot of licenses and one of them is "apache like"... Thanks
Isn't this the same package as https://bugzilla.redhat.com/show_bug.cgi?id=634911 which is under review now? At least a quick look tells me so.
Patrice, this is being worked on; you're more than welcome to join forces. I keep a sort of a status dashboard here: https://fedoraproject.org/wiki/User:Lkundrak/NodeJS
*** This bug has been marked as a duplicate of bug 634911 ***