Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

fpm-npm fails on npm -> deb #120

Closed
jalogisch opened this Issue · 12 comments

9 participants

@jalogisch

Trying to made .deb from npm fails.

Building up the Module isn't a Problem, and it is installed into node_modules directory in the working dir. There is also a dir named npm2pkg with contains the downloaded files.

but as result there is no .deb

# fpm-npm -t deb -n forever
npm WARN watch@0.3.3 package.json: bugs['web'] should probably be bugs['url']

> daemon@0.3.2 preinstall /update/node/node_modules/forever/node_modules/daemon
> node-waf configure build

Checking for program g++ or c++          : /usr/bin/g++ 
Checking for program cpp                 : /usr/bin/cpp 
Checking for program ar                  : /usr/bin/ar 
Checking for program ranlib              : /usr/bin/ranlib 
Checking for g++                         : ok  
Checking for node path                   : not found 
Checking for node prefix                 : ok /usr 
'configure' finished successfully (0.038s)
Waf: Entering directory `/update/node/node_modules/forever/node_modules/daemon/build'
[1/2] cxx: src/daemon.cc -> build/Release/src/daemon_1.o
[2/2] cxx_link: build/Release/src/daemon_1.o -> build/Release/daemon.node
Waf: Leaving directory `/update/node/node_modules/forever/node_modules/daemon/build'
'build' finished successfully (0.286s)
npm WARN prefer global forever@0.7.2 should be installed with -g
forever@0.7.2 ./node_modules/forever 
��� colors@0.5.1
��� mkdirp@0.2.1
��� async@0.1.15
��� timespan@2.0.1
��� pkginfo@0.2.2
��� watch@0.3.3
��� minimatch@0.0.4
��� daemon@0.3.2
��� cliff@0.1.5 (eyes@0.1.6)
��� portfinder@0.2.0 (mkdirp@0.0.7)
��� nconf@0.4.4 (ini@1.0.1)
��� optimist@0.2.8 (wordwrap@0.0.2)
��� dnode@0.8.2 (lazy@1.0.7 dnode-protocol@0.0.12 traverse@0.4.6 socket.io@0.6.18)
��� ps-tree@0.0.2 (parse-table@0.0.0)
��� winston@0.5.6 (eyes@0.1.6 stack-trace@0.0.6 loggly@0.3.9)
��� clip@0.1.6

can't find any suitable logfile to attach. system is debian lenny.

@rkhatibi

same problems here. It looks like fpm-npm does the build and makes a packages.tgz, but never hands off to the deb building code

tested with node 0.6.5 w/built in NPM, Ruby 1.9.2-p290, and FPM 0.3.11. I suspect part of the cause is npm is now bundled with node.

@adamgibbins

(Bumping to watch)

@pyr

i see the same behavior

@SparkGithub

same here

@saeta

bump to watch.

@jordansissel
Owner

There's no proper npm package type implemented in fpm, perhaps it's time that happens ;)

@jordansissel
Owner

TODO: remove fpm-npm, implement lib/fpm/packages/npm.rb

@philjackson

Is fpm-npm just a wrapper for... npm?

@mcreenan

Any update on this? It would be nice to be able to produce a deb package instead of having to depend on npm in my package and then install the modules i need via post-install.

@jordansissel
Owner

I'm going to delete fpm-npm in the repo. Will save confusion, I think, the 'fpm-npm' prototype hasn't been touched in 2 years. The proper support would be to create a lib/fpm/packages/npm.rb implementation as I described.

@jordansissel
Owner

c51697e removes fpm-npm

@jordansissel
Owner

fpm 0.4.33 adds npm support: fpm -s npm -t deb express

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.