Update to 1.6.3 failing [Solved]

help
1

On updating to 1.6.1.3, getting below:

tbanerjee@tbanerjee:~/workspace/meteor/app1$ meteor update --patch
                                              
Changes to your project's package version selections from updating the release:
                                              
babel-compiler             upgraded from 7.0.8 to 7.1.1
boilerplate-generator      upgraded from 1.4.0 to 1.5.0
ddp-server                 upgraded from 2.1.2 to 2.2.0
dynamic-import             upgraded from 0.3.0 to 0.4.0
ecmascript                 upgraded from 0.10.8 to 0.11.1
ecmascript-runtime         upgraded from 0.5.0 to 0.7.0
ecmascript-runtime-client  upgraded from 0.6.2 to 0.7.1
ecmascript-runtime-server  upgraded from 0.5.0 to 0.7.0
es5-shim                   upgraded from 4.7.3 to 4.8.0
meteor                     upgraded from 1.8.6 to 1.9.0
meteor-base                upgraded from 1.3.0 to 1.4.0
modern-browsers            added, version 0.1.1
modules                    upgraded from 0.11.6 to 0.12.0
modules-runtime            upgraded from 0.9.2 to 0.10.0
mongo                      upgraded from 1.4.7 to 1.5.0
npm-mongo*                 upgraded from 2.2.34 to 3.0.7
promise                    upgraded from 0.10.2 to 0.11.1
server-render              removed from your project
shim-common                removed from your project
socket-stream-client       upgraded from 0.1.0 to 0.2.1
tracker                    upgraded from 1.1.3 to 1.2.0
webapp                     upgraded from 1.5.0 to 1.6.0

                                              
* These packages have been updated to new versions that are not backwards
compatible.
app1: updated to Meteor 1.6.1.3.              
                                              
-- Notice --                                  
                                              
1.7: The underscore package has been removed as a dependency of all packages in
     meteor-base. Since some apps may have been using underscore through this
     dependency without having it listed in their .meteor/packages files, it
     has been added automatically. If your app is not using underscore, then
     you can safely remove it using 'meteor remove underscore'.

This looks fine, but then it dies horribly.

tbanerjee@tbanerjee:~/workspace/meteor/app1$ meteor npm start

> q6a@1.0.0 start /home/tbanerjee/workspace/meteor/app1
> meteor --settings settings-development.json

[[[[[ ~/workspace/meteor/app1 ]]]]]           

=> Started proxy.                             
=> Meteor 1.7.0.3 is available. Update this project with 'meteor update'.
=> Errors prevented startup:                  
   
   While selecting package versions:
   error: Potentially incompatible change required to top-level dependency:
   mongo 1.4.7, was 1.5.0.
   Constraints on package "mongo":
   * mongo@1.4.2 <- top level
   * mongo@~1.4.2 <- top level
   * mongo@1.4.2 <- autoupdate 1.4.0 <- cultofcoders:mocha 2.4.6
   * mongo@1.3.0 <- reactive-dict 1.2.0 <- session 1.1.7
   * mongo@1.3.0 <- accounts-base 1.4.2
   * mongo@1.1.14 <- service-configuration 1.0.11
   * mongo@1.1.2 <- alanning:roles 1.2.16
   * mongo@1.1.5 <- xolvio:cleaner 0.3.3
   * mongo@1.1.5 <- cultofcoders:mocha 2.4.6
   * mongo@1.0.4 <- aldeed:collection2 3.0.0
   * mongo@1.1.5 <- johanbrook:publication-collector 1.1.0
   
   Potentially incompatible change required to top-level dependency: es5-shim
   4.7.3, was 4.8.0.
   Constraints on package "es5-shim":
   * es5-shim@4.7.0 <- top level
   * es5-shim@~4.7.0 <- top level
   * es5-shim@4.7.0 <- meteor-base 1.3.0
   
   Potentially incompatible change required to top-level dependency: ecmascript
   0.10.9, was 0.11.1.
   Constraints on package "ecmascript":
   * ecmascript@0.10.6 <- top level
   * ecmascript@~0.10.6 <- top level
   * ecmascript@0.10.0 <- webapp 1.5.0 <- autoupdate 1.4.0 <-
   cultofcoders:mocha 2.4.6
   * ecmascript@0.10.0 <- webapp 1.5.0 <- meteor-base 1.3.0
   * ecmascript@0.10.0 <- logging 1.1.20 <- webapp 1.5.0 <- autoupdate 1.4.0 <-
   cultofcoders:mocha 2.4.6
   * ecmascript@0.10.0 <- logging 1.1.20 <- webapp 1.5.0 <- meteor-base 1.3.0
   * ecmascript@0.9.0 <- ejson 1.1.0 <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- base64 1.0.11 <- ejson 1.1.0 <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- routepolicy 1.0.13 <- ddp-server 2.1.2 <- ddp 1.4.0
   <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- routepolicy 1.0.13 <- webapp 1.5.0 <- meteor-base
   1.3.0
   * ecmascript@0.10.0 <- boilerplate-generator 1.4.0 <- webapp 1.5.0 <-
   autoupdate 1.4.0 <- cultofcoders:mocha 2.4.6
   * ecmascript@0.10.0 <- boilerplate-generator 1.4.0 <- webapp 1.5.0 <-
   meteor-base 1.3.0
   * ecmascript@0.4.3 <- webapp-hashing 1.0.9 <- webapp 1.5.0 <- autoupdate
   1.4.0 <- cultofcoders:mocha 2.4.6
   * ecmascript@0.4.3 <- webapp-hashing 1.0.9 <- webapp 1.5.0 <- meteor-base
   1.3.0
   * ecmascript@0.10.0 <- ddp-client 2.3.2 <- ddp 1.4.0 <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- check 1.3.1
   * ecmascript@0.10.0 <- random 1.1.0 <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- retry 1.1.0 <- autoupdate 1.4.0 <- cultofcoders:mocha
   2.4.6
   * ecmascript@0.10.0 <- id-map 1.1.0 <- binary-heap 1.0.10 <- mongo 1.4.7
   * ecmascript@0.10.0 <- callback-hook 1.1.0 <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- ddp-common 1.4.0 <- ddp-client 2.3.2 <- ddp 1.4.0 <-
   accounts-base 1.4.2
   * ecmascript@0.10.0 <- reload 1.2.0 <- cultofcoders:mocha 2.4.6
   * ecmascript@0.10.0 <- socket-stream-client 0.1.0 <- ddp-client 2.3.2 <- ddp
   1.4.0 <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- diff-sequence 1.1.0 <- ddp-client 2.3.2 <- ddp 1.4.0
   <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- diff-sequence 1.1.0 <- minimongo 1.4.4 <-
   aldeed:collection2 3.0.0
   * ecmascript@0.10.0 <- diff-sequence 1.1.0 <- mongo 1.4.7
   * ecmascript@0.10.0 <- mongo-id 1.0.7 <- ddp-client 2.3.2 <- ddp 1.4.0 <-
   accounts-base 1.4.2
   * ecmascript@0.10.0 <- mongo-id 1.0.7 <- minimongo 1.4.4 <-
   aldeed:collection2 3.0.0
   * ecmascript@0.10.0 <- mongo-id 1.0.7 <- mongo 1.4.7
   * ecmascript@0.10.0 <- ddp-server 2.1.2 <- ddp 1.4.0 <- accounts-base 1.4.2
   * ecmascript@0.9.0 <- minimongo 1.4.4 <- aldeed:collection2 3.0.0
   * ecmascript@0.10.0 <- ordered-dict 1.1.0 <- blaze 2.3.2 <- accounts-base
   1.4.2
   * ecmascript@0.10.0 <- server-render 0.3.1 <- es5-shim 4.7.3
   * ecmascript@0.10.0 <- shim-common 0.1.0 <- es5-shim 4.7.3
   * ecmascript@0.10.0 <- autoupdate 1.4.0 <- cultofcoders:mocha 2.4.6
   * ecmascript@0.10.0 <- mongo 1.4.7
   * ecmascript@0.9.0 <- allow-deny 1.1.0
   * ecmascript@0.9.0 <- reactive-dict 1.2.0 <- session 1.1.7
   * ecmascript@0.10.0 <- minifier-css 1.3.1 <- standard-minifier-css 1.4.1
   * ecmascript@0.10.0 <- accounts-password 1.5.1
   * ecmascript@0.9.0 <- accounts-base 1.4.2
   * ecmascript@0.10.0 <- rate-limit 1.0.9 <- ddp-rate-limiter 1.0.7
   * ecmascript@0.5.8 <- static-html 1.2.2
   * ecmascript@0.5.8 <- caching-html-compiler 1.1.2 <- static-html 1.2.2
   * ecmascript@0.9.0 <- caching-compiler 1.1.12 <- caching-html-compiler 1.1.2
   <- static-html 1.2.2
   * ecmascript@0.5.8 <- templating-tools 1.1.2 <- caching-html-compiler 1.1.2
   <- static-html 1.2.2
   * ecmascript@0.5.8 <- templating-tools 1.1.2 <- static-html 1.2.2
   * ecmascript@0.4.1 <- xolvio:cleaner 0.3.3
   * ecmascript@0.4.1 <- cultofcoders:mocha 2.4.6
   * ecmascript@0.4.0-beta.11 <- tmeasday:test-reporter-helpers 0.2.1 <-
   cultofcoders:mocha 2.4.6
   * ecmascript@0.4.3 <- coffeescript 1.0.17 <- cultofcoders:mocha 2.4.6
   * ecmascript@0.4.1 <- practicalmeteor:mocha-core 1.0.1 <- cultofcoders:mocha
   2.4.6
   * ecmascript@0.5.8 <- templating-compiler 1.3.3 <- templating 1.3.2 <-
   cultofcoders:mocha 2.4.6
   * ecmascript@0.4.1 <- xolvio:backdoor 0.2.1
   * ecmascript@0.1.3 <- mdg:validated-method 1.1.0
   * ecmascript@0.1.3 <- dburles:factory 1.1.0
   * ecmascript@0.9.0 <- shell-server 0.3.1
   * ecmascript@0.6.1 <- aldeed:collection2 3.0.0
   * ecmascript@0.4.0-beta.11 <- tmeasday:check-npm-versions 0.3.2 <-
   aldeed:collection2 3.0.0
   * ecmascript@0.4.1 <- johanbrook:publication-collector 1.1.0
   
   To allow potentially incompatible changes to top-level dependencies, you
   must pass --allow-incompatible-update on the command line.
   
=> Your application has errors. Waiting for file change.

Anyone have any ideas? I’ve still not moved to ^1.7 due to an issue around legacy decorators and mobX.

Have tried to do the --patch with the --allow-incompatible-update, but not having much luck. Assist is most appreciated.

2

Hi - I logged the same issue. Meteor 1.6.1.3 patch update - Potentially incompatible change required to top-level dependency errors?

I have logged it with Meteor github in case you want to track it too: https://github.com/meteor/meteor/issues/10008

You can workaround it like this:
meteor update --release 1.6.1.1 to downgrade back to Meteor 1.6.1.1

Then:
meteor update --release 1.6.1.3 to update JUST Meteor core.

I suspect that what’s happening is that the Meteor update tool is applying the Meteor 1.7 package updates which causes the incompatibility issues - but I am only guessing here.

Hope this helps anyway

Steve

1 Like
3

That worked really well. Thanks so much!

4

Hello @steveovens , I am on meteor 1.4.2 and trying to update to 1.6.3.1

I am seeing the same error as show in thread

MACLTUS66482:esmerlin-config m_712199$ meteor update
=> Errors while initializing project:

While selecting package versions:
error: No version of mongo satisfies all constraints: @1.5.0, @=1.1.14, @~1.5.0
Constraints on package “mongo”:

  • mongo@1.5.0 <- top level
  • mongo@=1.1.14 <- top level
  • mongo@~1.5.0 <- top level
  • mongo@1.4.2 <- autoupdate 1.4.0 <- hot-code-push 1.0.4 <- meteor-base 1.4.0
  • mongo@1.1.14 <- service-configuration 1.0.11
  • mongo@1.3.0 <- accounts-base 1.4.2
  • mongo@1.0.6 <- dburles:mongo-collection-instances 0.1.3
  • mongo@1.0.4 <- matb33:collection-hooks 0.7.5
  • mongo@1.1.12 <- poetic:apple-es-db-adapter 0.0.1

MACLTUS66482:esmerlin-config m_712199$ meteor update --all-packages --allow-incompatible-update
=> Errors while initializing project:

While selecting package versions:
error: No version of mongo satisfies all constraints: @1.5.0, @=1.1.14, @~1.5.0
Constraints on package “mongo”:

  • mongo@1.5.0 <- top level
  • mongo@=1.1.14 <- top level
  • mongo@~1.5.0 <- top level
  • mongo@1.4.2 <- autoupdate 1.4.0 <- hot-code-push 1.0.4 <- meteor-base 1.4.0
  • mongo@1.1.14 <- service-configuration 1.0.11
  • mongo@1.3.0 <- accounts-base 1.4.2
  • mongo@1.0.6 <- dburles:mongo-collection-instances 0.1.3
  • mongo@1.0.4 <- matb33:collection-hooks 0.7.5
  • mongo@1.1.12 <- poetic:apple-es-db-adapter 0.0.1

MACLTUS66482:esmerlin-config m_712199$ meteor update --release 1.6.1.1
=> Errors while initializing project:

While selecting package versions:
error: No version of mongo satisfies all constraints: @1.4.2, @=1.1.14, @~1.4.2
Constraints on package “mongo”:

  • mongo@1.4.2 <- top level
  • mongo@=1.1.14 <- top level
  • mongo@~1.4.2 <- top level
  • mongo@1.4.2 <- autoupdate 1.4.0 <- hot-code-push 1.0.4 <- meteor-base 1.3.0
  • mongo@1.1.14 <- service-configuration 1.0.11
  • mongo@1.3.0 <- accounts-base 1.4.2
  • mongo@1.0.6 <- dburles:mongo-collection-instances 0.1.3
  • mongo@1.0.4 <- matb33:collection-hooks 0.7.5
  • mongo@1.1.12 <- poetic:apple-es-db-adapter 0.0.1

MACLTUS66482:esmerlin-config m_712199$ meteor update --release 1.6.1.3
=> Errors while initializing project:

While selecting package versions:
error: No version of mongo satisfies all constraints: @1.4.2, @=1.1.14, @~1.4.2
Constraints on package “mongo”:

  • mongo@1.4.2 <- top level
  • mongo@=1.1.14 <- top level
  • mongo@~1.4.2 <- top level
  • mongo@1.4.2 <- autoupdate 1.4.0 <- hot-code-push 1.0.4 <- meteor-base 1.3.0
  • mongo@1.1.14 <- service-configuration 1.0.11
  • mongo@1.3.0 <- accounts-base 1.4.2
  • mongo@1.0.6 <- dburles:mongo-collection-instances 0.1.3
  • mongo@1.0.4 <- matb33:collection-hooks 0.7.5
  • mongo@1.1.12 <- poetic:apple-es-db-adapter 0.0.1

MACLTUS66482:esmerlin-config m_712199$ meteor update --patch
=> Errors while initializing project:

While selecting package versions:
error: No version of mongo satisfies all constraints: @1.1.24, @=1.1.14, @~1.5.0
Constraints on package “mongo”:

  • mongo@1.1.24 <- top level
  • mongo@=1.1.14 <- top level
  • mongo@~1.5.0 <- top level
  • mongo@1.4.2 <- autoupdate 1.4.0 <- hot-code-push 1.0.4 <- meteor-base 1.4.0
  • mongo@1.1.14 <- service-configuration 1.0.11
  • mongo@1.3.0 <- accounts-base 1.4.2
  • mongo@1.0.6 <- dburles:mongo-collection-instances 0.1.3
  • mongo@1.0.4 <- matb33:collection-hooks 0.7.5
  • mongo@1.1.12 <- poetic:apple-es-db-adapter 0.0.1
5

Hi @saig

Not sure if you are restoring your project back to a “clean” 1.4.x state between each of these steps? If not then the very first meteor update has likely left your packages in a messed up state that none of the subsequent updates will fix.

I would start by taking your code back to the clean, working 1.4.2 state. And then try

meteor update --release 1.6.1.3

I suspect this will do the trick.

If this does not work then it may be a different issue - you might want to raise a ticket with the Meteor dev team on github as I did.

Also worth reviewing the meteor upgrade guide as you are jumping a major release - just to be aware of other changes that may affect your project. https://guide.meteor.com/1.6-migration.html

6

I did a clean up and still i am seeing same error

MACLTUS66482:esmerlin-config m_712199$ meteor update --release 1.6.1.3
=> Errors while initializing project:

While selecting package versions:
error: No version of mongo satisfies all constraints: @1.4.2, @=1.1.14, @~1.4.2
Constraints on package “mongo”:

  • mongo@1.4.2 <- top level
  • mongo@=1.1.14 <- top level
  • mongo@~1.4.2 <- top level
  • mongo@1.4.2 <- autoupdate 1.4.0 <- hot-code-push 1.0.4 <- meteor-base 1.3.0
  • mongo@1.1.14 <- service-configuration 1.0.11
  • mongo@1.3.0 <- accounts-base 1.4.2
  • mongo@1.0.6 <- dburles:mongo-collection-instances 0.1.3
  • mongo@1.0.4 <- matb33:collection-hooks 0.7.5
  • mongo@1.1.12 <- poetic:apple-es-db-adapter 0.0.1
7

Check your .meteor/packages

Maybe paste it here in reply to get more eyes on it

I am wondering if a core package like accounts-base or service-configuration may be pinned to a specific (older) version eg @1.3.0 which is requiring the MongoDB@1.1.14 exact version which seems to be the issue

1 Like
8

If so - removing the @version constraint from the package should allow it to be ypdated to the appropriate meteor 1.6.3.1 package - which should be compatible

9

./packages

meteor-base@1.0.4 # Packages every Meteor app needs to have
mobile-experience@1.0.4 # Packages for a great mobile UX
mongo@1.1.14 # The database Meteor supports right now
reactive-var@1.0.11 # Reactive variable for tracker
jquery@1.11.10 # Helpful client-side library
tracker@1.1.1 # Meteor’s client-side reactive programming library

standard-minifier-css@1.3.2 # CSS minifier run for production mode
standard-minifier-js@1.2.1 # JS minifier run for production mode
es5-shim@4.6.15 # ECMAScript 5 compatibility for older browsers.
ecmascript@0.5.9 # Enable ECMAScript2015+ syntax in app code
shell-server@0.2.1 # Server-side component of the meteor shell command

service-configuration
accounts-base
static-html
react-meteor-data
dburles:collection-helpers
dburles:mongo-collection-instances
matb33:collection-hooks
themeteorchef:bert
poetic:apple-es-db-adapter
poetic:accounts-apple-connect
poetic:apple-es-db-logger
http
poetic:meteor-react-guard@2.2.0
ground:db@2.0.0-rc.7

./versions
accounts-base@1.2.14
allow-deny@1.0.5
autoupdate@1.2.11
babel-compiler@6.13.0
babel-runtime@0.1.12
base64@1.0.10
binary-heap@1.0.10
blaze@2.1.9
blaze-tools@1.0.10
boilerplate-generator@1.0.11
caching-compiler@1.1.8
caching-html-compiler@1.0.7
callback-hook@1.0.10
check@1.2.4
dburles:collection-helpers@1.1.0
dburles:mongo-collection-instances@0.3.5
ddp@1.2.5
ddp-client@1.2.9
ddp-common@1.2.7
ddp-rate-limiter@1.0.6
ddp-server@1.2.10
deps@1.0.12
diff-sequence@1.0.7
ecmascript@0.5.9
ecmascript-runtime@0.3.15
ejson@1.0.13
es5-shim@4.6.15
fastclick@1.0.13
fortawesome:fontawesome@4.4.0_1
fourseven:scss@3.8.1
geojson-utils@1.0.10
ground:db@2.0.0-rc.7
hot-code-push@1.0.4
html-tools@1.0.11
htmljs@1.0.11
http@1.2.9
id-map@1.0.9
jquery@1.11.10
lai:collection-extensions@0.2.1_1
launch-screen@1.0.12
livedata@1.0.18
localstorage@1.0.12
logging@1.1.16
matb33:collection-hooks@0.8.4
meteor@1.6.0
meteor-base@1.0.4
minifier-css@1.2.15
minifier-js@1.2.15
minimongo@1.0.18
mobile-experience@1.0.4
mobile-status-bar@1.0.13
modules@0.7.7
modules-runtime@0.7.7
mongo@1.1.14
mongo-id@1.0.6
npm-mongo@2.2.11_2
observe-sequence@1.0.14
ordered-dict@1.0.9
poetic:accounts-apple-connect@0.0.1
poetic:apple-es-db-adapter@0.0.1
poetic:apple-es-db-logger@0.0.1
poetic:meteor-react-guard@2.3.0
promise@0.8.8
raix:eventemitter@0.1.3
raix:eventstate@0.0.4
random@1.0.10
rate-limit@1.0.6
react-meteor-data@0.2.9
reactive-dict@1.1.8
reactive-var@1.0.11
reload@1.1.11
retry@1.0.9
routepolicy@1.0.12
service-configuration@1.0.11
session@1.1.7
shell-server@0.2.1
spacebars@1.0.13
spacebars-compiler@1.0.13
standard-minifier-css@1.3.2
standard-minifier-js@1.2.1
static-html@1.1.13
templating@1.1.14
templating-tools@1.0.5
themeteorchef:bert@2.1.1
tmeasday:check-npm-versions@0.2.0
tracker@1.1.1
ui@1.0.12
underscore@1.0.10
url@1.0.11
webapp@1.3.12
webapp-hashing@1.0.9

10

Yes, i see in packages folder inside i see a configuration

// XXX We should revisit how we factor MongoDB support into (1) the
// server-side node.js driver [which you might use independently of
// livedata, after all], (2) minimongo [ditto], and (3) Collection,
// which is the class that glues the two of them to Livedata, but also
// is generally the “public interface for newbies” to Mongo in the
// Meteor universe. We want to allow the components to be used
// independently, but we don’t want to overwhelm the user with
// minutiae.

Package.describe({
summary: “Adaptor for using MongoDB and Minimongo over DDP”,
version: ‘1.1.14’
});

Npm.depends({
“mongodb-uri”: “0.9.7”
});

Npm.strip({
mongodb: [“test/”]
});

Package.onUse(function (api) {
api.use(‘npm-mongo’, ‘server’);
api.use(‘allow-deny’);

api.use([
‘random’,
‘ejson’,
‘underscore’,
‘minimongo’,
‘ddp’,
‘tracker’,
‘diff-sequence’,
‘mongo-id’,
‘check’,
‘ecmascript’
]);

// Binary Heap data structure is used to optimize oplog observe driver
// performance.
api.use(‘binary-heap’, ‘server’);

// Allow us to detect ‘insecure’.
api.use(‘insecure’, {weak: true});

// Allow us to detect ‘autopublish’, and publish collections if it’s loaded.
api.use(‘autopublish’, ‘server’, {weak: true});

// Allow us to detect ‘disable-oplog’, which turns off oplog tailing for your
// app even if it’s configured in the environment. (This package will be
// probably be removed before 1.0.)
api.use(‘disable-oplog’, ‘server’, {weak: true});

// defaultRemoteCollectionDriver gets its deployConfig from something that is
// (for questionable reasons) initialized by the webapp package.
api.use(‘webapp’, ‘server’, {weak: true});

// If the facts package is loaded, publish some statistics.
api.use(‘facts’, ‘server’, {weak: true});

api.use(‘callback-hook’, ‘server’);

// Stuff that should be exposed via a real API, but we haven’t yet.
api.export(‘MongoInternals’, ‘server’);
// For tests only.
api.export(‘MongoTest’, ‘server’, {testOnly: true});
api.export(“Mongo”);

api.addFiles([‘mongo_driver.js’, ‘oplog_tailing.js’,
‘observe_multiplex.js’, ‘doc_fetcher.js’,
‘polling_observe_driver.js’,‘oplog_observe_driver.js’],
‘server’);
api.addFiles(‘local_collection_driver.js’, [‘client’, ‘server’]);
api.addFiles(‘remote_collection_driver.js’, ‘server’);
api.addFiles(‘collection.js’, [‘client’, ‘server’]);
api.addFiles(‘connection_options.js’, ‘server’);
});

Package.onTest(function (api) {
api.use(‘mongo’);
api.use(‘check’);
api.use([‘tinytest’, ‘underscore’, ‘test-helpers’, ‘ejson’, ‘random’,
‘ddp’, ‘base64’]);
// XXX test order dependency: the allow_tests “partial allow” test
// fails if it is run before mongo_livedata_tests.
api.addFiles(‘mongo_livedata_tests.js’, [‘client’, ‘server’]);
api.addFiles(‘upsert_compatibility_test.js’, ‘server’);
api.addFiles(‘allow_tests.js’, [‘client’, ‘server’]);
api.addFiles(‘collection_tests.js’, [‘client’, ‘server’]);
api.addFiles(‘observe_changes_tests.js’, [‘client’, ‘server’]);
api.addFiles(‘oplog_tests.js’, ‘server’);
api.addFiles(‘doc_fetcher_tests.js’, ‘server’);
});

11

Hmm

That mongodb@1.1.14 can’t be helping

I would recommend removing the package version constraints from meteor-base and mongodb and trying the update release agan

My 1.6.3.3 project has
meteor-base@1.3.0
Mobile-experience@1.0.5
Mongo@1.4.2

Some of the other packages have been updated also - like standard minifiers

Anyway let’s see if changing these gets you past the mongodb issue.

Good luck

1 Like
12

Hey thanks, @steveovens atlast i am able to upgrade to 1.6.1.3

changing the
Package.describe({
summary: “Adaptor for using MongoDB and Minimongo over DDP”,
version: ‘1.1.14’
});

this to version 1.4.2 did the trick

but is see this
MACLTUS66482:esmerlin-config m_712199$ meteor update --release 1.6.1.3
mongo: updating npm dependencies – mongodb-uri…
poetic:accounts-apple-connect: updating npm dependencies – cookie…

Changes to your project’s package version selections from updating the release:

accounts-base upgraded from 1.2.14 to 1.4.2
allow-deny upgraded from 1.0.5 to 1.1.0
autoupdate upgraded from 1.2.11 to 1.4.0
babel-compiler* upgraded from 6.13.0 to 7.0.9
babel-runtime* upgraded from 0.1.12 to 1.2.2
blaze upgraded from 2.1.9 to 2.3.2
boilerplate-generator upgraded from 1.0.11 to 1.4.0
caching-compiler upgraded from 1.1.8 to 1.1.9
callback-hook upgraded from 1.0.10 to 1.1.0
check upgraded from 1.2.4 to 1.3.0
ddp upgraded from 1.2.5 to 1.4.0
ddp-client* upgraded from 1.2.9 to 2.3.2
ddp-common upgraded from 1.2.7 to 1.4.0
ddp-rate-limiter upgraded from 1.0.6 to 1.0.7
ddp-server* upgraded from 1.2.10 to 2.1.2
diff-sequence upgraded from 1.0.7 to 1.1.0
dynamic-import added, version 0.3.0
ecmascript upgraded from 0.5.9 to 0.10.6
ecmascript-runtime upgraded from 0.3.15 to 0.5.0
ecmascript-runtime-client added, version 0.6.2
ecmascript-runtime-server added, version 0.5.0
ejson upgraded from 1.0.13 to 1.1.0
es5-shim upgraded from 4.6.15 to 4.7.0
fastclick removed from your project
http upgraded from 1.2.9 to 1.4.0
id-map upgraded from 1.0.9 to 1.1.0
launch-screen upgraded from 1.0.12 to 1.1.1
localstorage upgraded from 1.0.12 to 1.2.0
logging upgraded from 1.1.16 to 1.1.19
meteor upgraded from 1.6.0 to 1.8.2
meteor-base upgraded from 1.0.4 to 1.3.0
minifier-css upgraded from 1.2.15 to 1.3.0
minifier-js* upgraded from 1.2.15 to 2.3.5
minimongo upgraded from 1.0.18 to 1.4.3
mobile-experience upgraded from 1.0.4 to 1.0.5
mobile-status-bar upgraded from 1.0.13 to 1.0.14
modules upgraded from 0.7.7 to 0.11.3
modules-runtime upgraded from 0.7.7 to 0.9.1
mongo upgraded from 1.1.14 to 1.4.2
npm-mongo upgraded from 2.2.11_2 to 2.2.33
observe-sequence upgraded from 1.0.14 to 1.0.16
ordered-dict upgraded from 1.0.9 to 1.1.0
promise upgraded from 0.8.8 to 0.10.1
random upgraded from 1.0.10 to 1.1.0
rate-limit upgraded from 1.0.6 to 1.0.8
reactive-dict upgraded from 1.1.8 to 1.2.0
reload upgraded from 1.1.11 to 1.2.0
retry upgraded from 1.0.9 to 1.1.0
server-render added, version 0.3.1
shell-server upgraded from 0.2.1 to 0.3.1
shim-common added, version 0.1.0
socket-stream-client added, version 0.1.0
spacebars-compiler upgraded from 1.0.13 to 1.1.1
standard-minifier-css upgraded from 1.3.2 to 1.4.0
standard-minifier-js* upgraded from 1.2.1 to 2.3.3
templating upgraded from 1.1.14 to 1.2.14
templating-tools upgraded from 1.0.5 to 1.1.1
tracker upgraded from 1.1.1 to 1.1.3
ui removed from your project
url upgraded from 1.0.11 to 1.2.0
webapp upgraded from 1.3.12 to 1.5.0

  • These packages have been updated to new versions that are not backwards
    compatible.
    esmerlin-config: updated to Meteor 1.6.1.3.

– Notice –

1.4.3: The account packages for different services (e.g. facebook, twitter, google, etc.) have been split and now make it possible to avoid bundling Blaze in the client bundle for projects not using Blaze. If found in
the .meteor/packages file, these packages have been split automatically. Assuming there are no other Blaze dependencies, the “-config-ui” package can be removed if there is no need for the Blaze
configuration interface.

13

ok - I didn’t mean change the package description - I meant remove (or change) the package constraint in your .meteor/packages file

If you change the package description (which seems to be what you are saying you did) - then you are literally just re-badging mongodb version 1.1.4 and calling it 1.4.2 (without actually running the code that IS version 1.4.2).

This might get you past the version checker - but will likely introduce other issues as the code will be quite different.

So - I would do this one more time from a clean revert back to your working 1.4.2 version…

Steps:

  • Revert BACK to 1.4.2
  • Run the meteor update --release 1.6.1.3
    After getting the errors, update your .meteor/packages - you should have something like this in the top lines:
meteor-base@1.3.0             # Packages every Meteor app needs to have
mobile-experience@1.0.5       # Packages for a great mobile UX
mongo@1.4.2                   # The database Meteor supports right now

Run your project again (it will update the packages because versions have changed)

You should then have a consistent set of packages.

Hope this helps.

14

yeah got it.

meteor-base@1.3.0 # Packages every Meteor app needs to have
mobile-experience@1.0.5 # Packages for a great mobile UX
mongo@1.4.2 # The database Meteor supports right now

i ran it now all are in sync cool! thanks a lot