Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

npm install orm --save fails on Windows - git error #5702

Open
pwl86 opened this Issue · 5 comments

4 participants

@pwl86

Hello,

I am new here I please forgive me any mistakes :-)

I am getting error while running command: npm install orm --save
However I am able to install older version orm@2.1.3 without any errors or warnings.

Here is the error from console:

npm ERR! Failed resolving git HEAD (https://github.com/dresende/node-sql-ddl-sync.git) fatal: ambiguous argument 'v0.3.8': unknown revision or path not in the w orking tree.
npm ERR! Failed resolving git HEAD (https://github.com/dresende/node-sql-ddl-sync.git) Use '--' to separate paths from revisions, like this:
npm ERR! Failed resolving git HEAD (https://github.com/dresende/node-sql-ddl-sync.git) 'git <command> [<revision>...] -- [<file>...]'
npm ERR! Failed resolving git HEAD (https://github.com/dresende/node-sql-ddl-sync.git)
npm ERR! Failed resolving git HEAD (https://github.com/dresende/node-sql-query.git) fatal: ambiguous argument 'v0.1.21': unknown revision or path not in the working tree.
npm ERR! Failed resolving git HEAD (https://github.com/dresende/node-sql-query.git) Use '--' to separate paths from revisions, like this:
npm ERR! Failed resolving git HEAD (https://github.com/dresende/node-sql-query.git) 'git <command> [<revision>...] -- [<file>...]'
npm ERR! Failed resolving git HEAD (https://github.com/dresende/node-sql-query.git)
npm ERR! Error: Command failed: fatal: ambiguous argument 'v0.3.8': unknown revision or path not in the working tree.
npm ERR! Use '--' to separate paths from revisions, like this:
npm ERR! 'git <command> [<revision>...] -- [<file>...]'
npm ERR!
npm ERR!     at ChildProcess.exithandler (child_process.js:647:15)
npm ERR!     at ChildProcess.emit (events.js:98:17)
npm ERR!     at maybeClose (child_process.js:755:16)
npm ERR!     at Socket.<anonymous> (child_process.js:968:11)
npm ERR!     at Socket.emit (events.js:95:17)
npm ERR!     at Pipe.close (net.js:465:12)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\\Program Files (x86)\\nodejs\\node.exe" "c:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "orm" "--save"
npm ERR! cwd c:\Users\praczynx\workspace\CustomerPortal
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! code 128
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     c:\Users\praczynx\workspace\CustomerPortal\npm-debug.log
npm ERR! not ok code 0

Git version:

$ git --version
git version 1.9.4.msysgit.0
@othiym23 othiym23 added the support label
@kawas44

+1

To me it seems that this issue keep popping and people get around it but not solution has been found. I assume it is Windows only.

TLDR
In my team we get around it adding a slash before version tag
so git+ssh://git@git.devhost.dn:foo/bar.git#v0.2.0
became git+ssh://git@git.devhost.dn:foo/bar.git/#v0.2.0

What's strange with this bug is that some in the team (other Windows users) does not need an extra slash to make it work. We have checked npm, node and git versions still no correlation

As of today I still have this bug and add my extra slash to my own repo without pushing it to others.

node -v v0.10.32
npm -v 1.4.28
git version 1.9.4.msysgit.2

Good luck

@othiym23
Owner

@kawas44 What that means is that some of you have it cached correctly, and some of you don't. npm cache clean will put everybody on the same page, but that's just a workaround, because the real issue is on us, to make working with git dependencies less finicky.

@kawas44

@othiym23 many thanks

'npm cache clean' did fix our weird slash hack !

@othiym23 othiym23 added this to the cache rewrite milestone
@othiym23
Owner

I've stuck this on the cache rewrite milestone to remind me to come back and let you know when the relevant work has been done around git dependency caching so you two can test it for me and make sure I didn't break anything. Expect a ping before the end of the year. ;)

@smikes

/cc @othiym23 should be tagged 'bug'

@othiym23 othiym23 added bug windows and removed support labels
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.