Ensure am11/pangyp not fetched via SSH

[saper]

Pin am11/pangyp to the particular commit

Should fix the problem mentioned in:
579baf3#commitcomment-11082041

[xzyfer]

Should we not just default to the https endpoint to avoid any ssh issues?

[fourseven]

I have this problem through the windows meteor build system on v3.0.0:

C:\Users\Mathew Hartley>  meteor publish-for-arch fourseven:[email protected]
compileScss: updating npm dependencies -- node-sass, lodash, autoprefixer-core...
npm WARN package.json [email protected] No description
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No README data
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\\Users\\Mathew
Hartley\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.1.3\\mt-os.windows.x86_32\\dev_bundle\\bin\\\\node.exe"
"C:\\Users\\Mathew
Hartley\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.1.3\\mt-os.windows.x86_32\\dev_bundle\\bin\\node_modules\\npm\\bin\\npm-cli.js"
"install"
npm ERR! node v0.10.36
npm ERR! npm  v2.7.3
npm ERR! code ETARGET

npm ERR! notarget No compatible version found:
pangyp@'git+ssh://[email protected]/am11/pangyp.git#f13599f5198b853948429062c2b334010a337342'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["2.0.0","2.0.1","2.0.2","2.1.0"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'node-sass'
npm ERR! notarget


=> Errors while initializing project:

While building plugin `compileScss` in package `fourseven:scss`:
error: couldn't install npm packages from npm-shrinkwrap

[saper]

That's interesting:

changing the pangyp line to "http" causes the same symptomps as reported by the original poster:

https://gist.github.com/941c4f5c16f30d88efb2

https:// seems to work better.

[xzyfer]

Unsurprising. Github is https only.
On 7 May 2015 23:44, "Marcin Cieślak" [email protected] wrote:

That's interesting:

changing the pangyp line to "http" causes the same symptomps as reported
by the original poster:

https://gist.github.com/941c4f5c16f30d88efb2

https:// seems to work better.

—
Reply to this email directly or view it on GitHub
#931 (comment).

[am11]

Thanks @saper! I would say, lets pursue this here: rvagg/archived-pangyp#5.

@rvagg, could you please publish pangyp vNext to npm after the merge? Thanks in anticipation. 🎁

[xzyfer]

CI seems pretty unhappy about this.

[xzyfer]

This doesn't appear to be a usable solution. We need to wait until it's solved upstream. Addressing this in #942 for now.