Skip to content
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

Build failing for Meteor 1.6.1.3 #111

Open
jrtilson opened this issue Jul 12, 2018 · 3 comments
Open

Build failing for Meteor 1.6.1.3 #111

jrtilson opened this issue Jul 12, 2018 · 3 comments

Comments

@jrtilson
Copy link

Trying to build using Meteor version 1.6.1.3 results in:

* Connection #0 to host install.meteor.com left intact
[-] Installing Meteor 1.6.1.3...
Downloading Meteor distribution
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
The command '/bin/sh -c cd $APP_SOURCE_DIR && $BUILD_SCRIPTS_DIR/install-deps.sh && $BUILD_SCRIPTS_DIR/install-node.sh && $BUILD_SCRIPTS_DIR/install-phantom.sh && $BUILD_SCRIPTS_DIR/install-graphicsmagick.sh && $BUILD_SCRIPTS_DIR/install-mongo.sh && $BUILD_SCRIPTS_DIR/install-meteor.sh && $BUILD_SCRIPTS_DIR/build-meteor.sh && $BUILD_SCRIPTS_DIR/post-build-cleanup.sh' returned a non-zero code: 1
build hook failed! (1)
ERROR: Build failed: build hook failed! (1)
ERROR: Build failed with exit code 2
ERROR: Build in 'master' (91d9a8f2) failed in 0:08:22�

This in on Docker Cloud, and worked Previously with Meteor 1.6.1.1

Any ideas?

@jrtilson
Copy link
Author

Testing this on MacOS I believe I found the issue, the TARBALL_URL for 1.6.1.3 returns a 403:

https://static-meteor.netdna-ssl.com/packages-bootstrap/1.6.1.3/meteor-bootstrap-os.osx.x86_64.tar.gz

@jrtilson
Copy link
Author

There's also an issue open on the meteor repo:

meteor/meteor#10038

@gustawdaniel
Copy link
Contributor

I suggest to close because of it is not problem of this repo and this version is outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants