Source0 for nodejs modules
by Piotr Popieluch
The the Node.js guidelines say about Source0 [1]:
"The canonical method for shipping most node modules is tarballs from
the npm registry"
and
"This method [PP: tarbals from npm] should be preferred to using
checkouts from git or automatically generated tarballs from GitHub."
But I think that in following cases it would be better to use sources
from the upstream project:
1) When the license is not included in NPM but is in upstream project.
o Because we are not supposed to ship the license separate from the
sources.
2) When the tests are not included.
o In this case we need to download the sources from NPM and from
upstream project, which seems redundant and a waste of work.
3) When NPM content is generated and source files are not in NPM.
o This would mean to download sources from NPM and upstream project,
delete the NPM sources in prep and generate the files again.
Are there good reason to enforce the use of NPM sources which I am
missing? What is your opinion?
I would like to suggest to ad those three exceptions to the guidelines.
Piotr
[1]:
https://fedoraproject.org/wiki/Packaging:Node.js?rd=Node.js/Packagers#Usi...
4 years, 10 months
native modules in epel7 ftbfs
by Piotr Popieluch
Last week the %{nodejs_arches} macro got updated in epel7 to add aarch64
architecture.
I've decided to rebuild node and the native modules so we can start using
the new arch. While at it I updated node from 6.9.4 to 6.9.5.
Now I cannot get any of the native modules built. It seems they haven't
been rebuild in years and are broken from at least the last update to 6.x.
I tried to get them built again but there seem to be some issues with
outdated versions of nan and node-gyp..
Is it forgotten to check/rebuild the native modules while updating to 6.x ?
Does someone remember what was done in Fedora to get them working again?
6 years, 7 months
Updating nodejs-bytes
by Ben Rosser
Hello nodejs@,
I'm currently, slowly, working on packaging quassel-webserver [1], a
nodejs web application. It has a number of node dependencies that need
to be gotten in Fedora (hence the "slowly").
I've currently hit a roadblock: nodejs-body-parser is needed by
nodejs-libquassel (one of the dependencies). body-parser depends on
nodejs-bytes version 2.4.0 [2]. We presently ship version *0.3.0*,
which dates back to March 2014. Tests suggest that there's actual API
changes between 0.3.0 and 2.4.0; attempting to %nodejs_fixdep the
problem away caused body-parser's unit tests to fail.
There is an open bug against our nodejs-bytes package to update it to
a newer version that was filed by release-monitoring (back in 2014)
[3], but the only action on the ticket has been additional bumps from
release-monitoring as newer and newer versions have been released.
Since the nodejs-sig group has commit rights on the package, I figured
I'd first contact this list before doing anything else. Is there a
reason we're shipping such an old version? Would it be possible for
someone to look into updating it? Should I request commit rights
myself?
dnf repoquery --whatrequires "npm(bytes)" suggests its dependencies in
Fedora are:
> nodejs-compression-0:1.0.1-5.fc24.noarch
> nodejs-connect-0:2.14.5-7.fc24.noarch
> nodejs-morgan-0:1.0.0-5.fc24.noarch
> nodejs-raw-body-0:1.1.4-4.fc24.noarch
Thanks in advance!
Ben Rosser
[1] https://github.com/magne4000/quassel-webserver
[2] https://github.com/expressjs/body-parser/blob/master/package.json
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1094697
6 years, 7 months
Node.js doesn't build with GCC 7
by Stephen Gallagher
Right now, we have a pretty serious problem with Node.js. It failed to rebuild
during the mass-rebuild for Fedora 26 due to
https://github.com/nodejs/node/issues/10388
I'm trying to work with Node.js upstream to see if we can get it resolved
quickly, but for the time being, Node doesn't build in Fedora 26.
I'll keep the list updated on the situation.
6 years, 7 months
Node.js 6.9.5
by Stephen Gallagher
Zuzana, I noticed you built Node.js 6.9.5 for Fedora 25 but not for EPEL 7. I'm
not bothering with EPEL 7 because there were no changes to Node itself in this
release, only to the bundled copy of OpenSSL which we sanitize from the tarball.
So, I don't think it's worth the effort of going through two weeks in Bodhi for
a release that has no changes. Agree?
6 years, 7 months