AceLine commented 11 years ago

Hi,

I tried to install Pushd on Debian Squeeze but it failed. The whole output of installation process was:

npm install

npm http GET https://registry.npmjs.org/redis npm http GET https://registry.npmjs.org/netmask npm http GET https://registry.npmjs.org/async npm http GET https://registry.npmjs.org/mocha npm http GET https://registry.npmjs.org/should npm http GET https://registry.npmjs.org/hiredis npm http GET https://registry.npmjs.org/apn/1.3.1 npm http GET https://registry.npmjs.org/c2dm/1.1.0 npm http GET https://registry.npmjs.org/express npm ERR! git clone git://github.com/rs/node-gcm.git error: unknown option mirror' npm ERR! git clone git://github.com/rs/node-gcm.git usage: git-clone [options] [--] <repo> [<dir>] npm ERR! git clone git://github.com/rs/node-gcm.git npm ERR! git clone git://github.com/rs/node-gcm.git -q, --quiet be quiet npm ERR! git clone git://github.com/rs/node-gcm.git -n, --no-checkout don't create a checkout npm ERR! git clone git://github.com/rs/node-gcm.git --bare create a bare repository npm ERR! git clone git://github.com/rs/node-gcm.git --naked create a bare repository npm ERR! git clone git://github.com/rs/node-gcm.git -l, --local to clone from a local repository npm ERR! git clone git://github.com/rs/node-gcm.git --no-hardlinks don't use local hardlinks, always copy npm ERR! git clone git://github.com/rs/node-gcm.git -s, --shared setup as shared repository npm ERR! git clone git://github.com/rs/node-gcm.git --template <path> path the template repository npm ERR! git clone git://github.com/rs/node-gcm.git --reference <repo> reference repository npm ERR! git clone git://github.com/rs/node-gcm.git -o, --origin <branch> npm ERR! git clone git://github.com/rs/node-gcm.git use <branch> instead or 'origin' to track upstream npm ERR! git clone git://github.com/rs/node-gcm.git -u, --upload-pack <path> npm ERR! git clone git://github.com/rs/node-gcm.git path to git-upload-pack on the remote npm ERR! git clone git://github.com/rs/node-gcm.git --depth <depth> create a shallow clone of that depth npm http GET https://registry.npmjs.org/coffee-script npm ERR! git clone git://github.com/rs/mpns.git error: unknown optionmirror' npm ERR! git clone git://github.com/rs/mpns.git usage: git-clone [options] [--] [

] npm ERR! git clone git://github.com/rs/mpns.git npm ERR! git clone git://github.com/rs/mpns.git -q, --quiet be quiet npm ERR! git clone git://github.com/rs/mpns.git -n, --no-checkout don't create a checkout npm ERR! git clone git://github.com/rs/mpns.git --bare create a bare repository npm ERR! git clone git://github.com/rs/mpns.git --naked create a bare repository npm ERR! git clone git://github.com/rs/mpns.git -l, --local to clone from a local repository npm ERR! git clone git://github.com/rs/mpns.git --no-hardlinks don't use local hardlinks, always copy npm ERR! git clone git://github.com/rs/mpns.git -s, --shared setup as shared repository npm ERR! git clone git://github.com/rs/mpns.git --template path the template repository npm ERR! git clone git://github.com/rs/mpns.git --reference reference repository npm ERR! git clone git://github.com/rs/mpns.git -o, --origin npm ERR! git clone git://github.com/rs/mpns.git use instead or 'origin' to track upstream npm ERR! git clone git://github.com/rs/mpns.git -u, --upload-pack npm ERR! git clone git://github.com/rs/mpns.git path to git-upload-pack on the remote npm ERR! git clone git://github.com/rs/mpns.git --depth create a shallow clone of that depth npm ERR! Error:

git "clone" "--mirror" "git://github.com/rs/node-gcm.git" "/root/.npm/_git-remotes/git-github-com-rs-node-gcm-git-3012d575"

failed with 129 npm ERR! at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/exec.js:59:20) npm ERR! at ChildProcess.EventEmitter.emit (events.js:98:17) npm ERR! at maybeClose (child_process.js:730:16) npm ERR! at Socket. (child_process.js:943:11) npm ERR! at Socket.EventEmitter.emit (events.js:95:17) npm ERR! at Pipe.close (net.js:451:12) npm ERR! If you need help, you may report this log at: npm ERR! http://github.com/isaacs/npm/issues npm ERR! or email it to: npm ERR! npm-@googlegroups.com

Hope you - ore anybody - can help me out.

Best regards,

AceLine

jvah commented 11 years ago

My guess is that the problem is your npm uses "--mirror" with git clone, but your git version is too old to support it. I think in the case of npm it would be enough to change "--mirror" to "--bare", but I haven't tested it. The "--mirror" flag is defined in "lib/cache.js" of npm, easier way would be to upgrade the git client, though...

AceLine commented 11 years ago

Hi, thnx. for your reply. I made an update to the latest git and git-core version I could get over apt-get install. The output now was bit different then before but:

hiredis@0.1.15 install /usr/local/src/pushd/node_modules/hiredis node-gyp rebuild

npm WARN package.json jade@0.26.3 No README.md file found! Traceback (most recent call last): File "/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp", line 15, in import gyp File "/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/init.py", line 8, in import gyp.input File "/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 15, in import multiprocessing ImportError: No module named multiprocessing gyp ERR! configure error gyp ERR! stack Error: gyp failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:415:16) gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17) gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:784:12) gyp ERR! System Linux 2.6.26-2-686 gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /usr/local/src/pushd/node_modules/hiredis gyp ERR! node -v v0.10.4 gyp ERR! node-gyp -v v0.9.5 gyp ERR! not ok npm ERR! hiredis@0.1.15 install: node-gyp rebuild npm ERR! sh "-c" "node-gyp rebuild" failed with 1 npm ERR! npm ERR! Failed at the hiredis@0.1.15 install script. npm ERR! This is most likely a problem with the hiredis package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-gyp rebuild npm ERR! You can get their info via: npm ERR! npm owner ls hiredis npm ERR! There is likely additional logging output above.

Please give me a detailed hint to the right direction to solve this problem... I'm very much in need of pushd.

Thnx. in advance,

AceLine

jvah commented 11 years ago

Probably an old Python version, multiprocessing module was introduced in Python 2.6. You could upgrade python as well, or alternatively try to get http://code.google.com/p/python-multiprocessing/ from somewhere.

Unfortunately Node.js doesn't mix very well with old systems. :)

AceLine commented 11 years ago

Hi again,

thnx. for reply. I updated git to 2.7 and it worked like a charm. so good. Although I have one last problem now:

coffee pushd.coffee

Registering push service: event-source Registering push service: apns Registering push service: gcm Registering push service: http Registering push service: mpns-toast Registering push service: mpns-tile Listening on tcp port 8085 Listening on udp port 8085

events.js:72 throw er; // Unhandled 'error' event ^ Error: Redis connection to 127.0.0.1:/var/run/redis/redis.sock failed - connect ENOENT at RedisClient.on_error (/usr/local/src/pushd/node_modules/redis/index.js:151:24) at Socket. (/usr/local/src/pushd/node_modules/redis/index.js:86:14) at Socket.EventEmitter.emit (events.js:95:17) at net.js:426:14 at process._tickCallback (node.js:415:13)

The only thing I changed btw. added in the settings.coffee was the google api-key....

Please tell me if you know a very detailed tutorial or how to to get to know step by step how to configure settings.coffee or at all "how to install, configure and get up and running pushd".

Thank you so much for your patience,

best regards,

AceLine

rs commented 11 years ago

Is you Redis server running?

AceLine commented 11 years ago

Yes it is running...

jvah commented 11 years ago

Try to comment out redis_socket and uncomment redis_port and redis_host.

jvah commented 11 years ago

Did the last comment fix your issue? It would be polite to close the issue if it did.

fortress-of-solitude commented 11 years ago

I was seeing the same issue as reported by AceLine - the suggestion to "comment out redis_socket and uncomment redis_port and redis_host" solved the issue for me. Thanks.

jvah commented 11 years ago

Cool, I will make a patch that changes the settings-sample.coffee to be less confusing.

rs / pushd

Installation on Debian Squeeze fail #14

npm install

coffee pushd.coffee