New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure am11/pangyp not fetched via SSH #931

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
4 participants
@saper
Member

saper commented May 7, 2015

Pin am11/pangyp to the particular commit

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

saper referenced this pull request May 7, 2015

build: Adds win_delay_hook so iojs runs with alias.
Before building, first apply the following patch
to pangyp: rvagg/archived-pangyp#5 (until it is merged).

Issue URL: #870.
Show outdated Hide outdated package.json Outdated
@fourseven

This comment has been minimized.

Show comment
Hide comment
@fourseven

fourseven May 7, 2015

Contributor

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

C:\Users\Mathew Hartley>  meteor publish-for-arch fourseven:scss@3.0.0
compileScss: updating npm dependencies -- node-sass, lodash, autoprefixer-core...
npm WARN package.json packages-for-meteor-smartpackage-1qs6hw3@0.0.0 No description
npm WARN package.json packages-for-meteor-smartpackage-1qs6hw3@0.0.0 No repository field.
npm WARN package.json packages-for-meteor-smartpackage-1qs6hw3@0.0.0 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://git@github.com/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
Contributor

fourseven commented May 7, 2015

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

C:\Users\Mathew Hartley>  meteor publish-for-arch fourseven:scss@3.0.0
compileScss: updating npm dependencies -- node-sass, lodash, autoprefixer-core...
npm WARN package.json packages-for-meteor-smartpackage-1qs6hw3@0.0.0 No description
npm WARN package.json packages-for-meteor-smartpackage-1qs6hw3@0.0.0 No repository field.
npm WARN package.json packages-for-meteor-smartpackage-1qs6hw3@0.0.0 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://git@github.com/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

@fourseven fourseven referenced this pull request May 7, 2015

Closed

Windows v3.0.0 release #83

@saper

This comment has been minimized.

Show comment
Hide comment
@saper

saper May 7, 2015

Member

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.

Member

saper commented May 7, 2015

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

This comment has been minimized.

Show comment
Hide comment
@xzyfer

xzyfer May 7, 2015

Contributor

Unsurprising. Github is https only.
On 7 May 2015 23:44, "Marcin Cieślak" notifications@github.com 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).

Contributor

xzyfer commented May 7, 2015

Unsurprising. Github is https only.
On 7 May 2015 23:44, "Marcin Cieślak" notifications@github.com 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).

@saper saper referenced this pull request May 7, 2015

Closed

Installation failed #937

@am11

This comment has been minimized.

Show comment
Hide comment
@am11

am11 May 8, 2015

Member

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. 🎁

Member

am11 commented May 8, 2015

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

This comment has been minimized.

Show comment
Hide comment
@xzyfer

xzyfer May 8, 2015

Contributor

CI seems pretty unhappy about this.

Contributor

xzyfer commented May 8, 2015

CI seems pretty unhappy about this.

Ensure am11/pangyp not fetched via SSH
Pin am11/pangyp to the particular commit
@xzyfer

This comment has been minimized.

Show comment
Hide comment
@xzyfer

xzyfer May 9, 2015

Contributor

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

Contributor

xzyfer commented May 9, 2015

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

@saper saper closed this May 9, 2015

@xzyfer xzyfer referenced this pull request May 9, 2015

Merged

Load am11/pangyp from HTTPS #943

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment