djhi / heroku-buildpack-meteorite

MIT License
11 stars 16 forks source link

Downgraded packages during deploy #3

Open todda00 opened 10 years ago

todda00 commented 10 years ago

This buildpack works for me to deploy to Heroku, but for some reason it downgrades some packages during the deploy. These packages are not downgraded when using meteor deploy to *.meteor.com sites, or running on localhost, but they are downgraded during the deploy to Heroku.

downgraded splendido:accounts-templates-unstyled from version 0.9.11 to version 0.9.7 downgraded aldeed:autoform from version 3.2.0 to version 3.1.0 downgraded splendido:accounts-templates-core from version 0.9.11 to version 0.9.7

Here is my log:

Fetching repository, done.
Counting objects: 7, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 1.03 KiB | 0 bytes/s, done.
Total 7 (delta 5), reused 0 (delta 0)

-----> Removing .DS_Store files
-----> Fetching custom git buildpack... done
-----> Meteor app app detected
-----> Resolving engine versions

       No version of Node.js specified in nodeversion, using '0.10.29'

       Using Node.js version: 0.10.29
-----> Fetching Node.js binaries
        - downloading and extracting node from http://s3pository.heroku.com/node/v0.10.29/node-v0.10.29-linux-x64.tar.gz
-----> Installing meteorite with npm

       > fibers@1.0.2 install /tmp/node-modules-1nrX/lib/node_modules/fibers
       > node ./build.js

       `linux-x64-v8-3.14` exists; testing
       Binary is fine; exiting
       /tmp/node-modules-1nrX/bin/mrt -> /tmp/node-modules-1nrX/lib/node_modules/meteorite/bin/mrt.js

       > meteorite@0.9.2 postinstall /tmp/node-modules-1nrX/lib/node_modules/meteorite
       > sh ./completions/postinstall.sh

       fibers@1.0.2 /tmp/node-modules-1nrX/lib/node_modules/fibers

       meteorite@0.9.2 /tmp/node-modules-1nrX/lib/node_modules/meteorite
       ├── rolling_timeout_exec@0.0.1
       ├── colors@0.6.0-1
       ├── wrench@1.3.9
       ├── async@0.2.9
       ├── optimist@0.6.1 (wordwrap@0.0.2, minimist@0.0.10)
       ├── underscore@1.3.3
       ├── fstream@1.0.2 (inherits@2.0.1, rimraf@2.2.8, graceful-fs@3.0.3, mkdirp@0.5.0)
       ├── ddp@0.4.6 (faye-websocket@0.7.3, meteor-ejson@0.6.3, node-srp@0.0.1)
       └── prompt@0.2.11 (read@1.0.5, pkginfo@0.3.0, revalidator@0.1.8, winston@0.6.2, utile@0.2.1)
       Meteorite installed
       Installing meteor
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4506    0  4506    0     0  14220      0 --:--:-- --:--:-- --:--:-- 15645
Downloading Meteor distribution
######################################################################## 100.0%

Meteor 0.9.3.1 has been installed in your home directory (~/.meteor).

Now you need to do one of the following:

  (1) Add "$HOME/.meteor" to your path, or
  (2) Run this command as root:
        cp "/tmp/node-meteor-6u3J/.meteor/packages/meteor-tool/1.0.33/meteor-tool-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor

Then to get started, take a look at 'meteor --help' or see the docs at
docs.meteor.com.
       Meteor installed
       Installing packages

       Done installing smart packages
       Building meteor bundle
       WARNING: 'bundle' has been deprecated. Use 'build' instead.

       Figuring out the best package versions to use. This may take a moment.
         downgraded splendido:accounts-templates-unstyled from version 0.9.11 to version 0.9.7
         downgraded aldeed:autoform from version 3.2.0 to version 3.1.0
         downgraded splendido:accounts-templates-core from version 0.9.11 to version 0.9.7
-----> Vendoring node into slug
-----> Move to app directory: /programs/server
-----> Run npm install
npm WARN package.json meteor-dev-bundle@0.0.0 No description
npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
npm WARN package.json meteor-dev-bundle@0.0.0 No README data

> fibers@1.0.1 install /tmp/build_00facb4b-09a2-4456-be86-ab7ccc143994/.meteor/heroku_build/app/programs/server/node_modules/fibers
> node ./build.js

`linux-x64-v8-3.14` exists; testing
Binary is fine; exiting
underscore@1.5.2 node_modules/underscore

semver@2.2.1 node_modules/semver

source-map-support@0.2.5 node_modules/source-map-support
└── source-map@0.1.29 (amdefine@0.1.0)

fibers@1.0.1 node_modules/fibers
-----> Copy over environment profile.d scripts
-----> Discovering process types
       Procfile declares types      -> (none)
       Default types for Meteor app -> web

-----> Compressing... done, 17.6MB
-----> Launching... done, v29
       http://rampdash-prod.herokuapp.com/ deployed to Heroku

To git@heroku.com:rampdash-prod.git
   e3993ba..d4ec0ef  master -> master
djhi commented 10 years ago

Hi,

Yes I've seen this too. Can't figure out why it's happening. My only guess is that some dependencies are not playing well together. I'll look into this and keep you informed

krstffr commented 9 years ago

The same issue is described here: https://github.com/AdmitHub/meteor-buildpack-horse/issues/17