Update to Meteor 2.3.2 problems- Help

Struggling to update to Meteor 2.3.2 from 2.2 as I am not able to understand the error messages any help would be appreciated.

This is the message I get from the update (partial msg)

 Conflict: Constraint http@1.1.0 is not satisfied by http 2.0.0.
   Constraints on package "http":
   * http@2.0.0 <- top level
   * http@1.0.10 <- useraccounts:core 1.14.2 <- useraccounts:bootstrap 1.14.2
   * http@1.4.2 || 2.0.0 <- mizzao:timesync 0.5.2 <- mizzao:user-status 1.0.1
   * http@1.0.8 <- cfs:http-methods 0.0.32 <- tap:i18n 1.8.2
   * http@1.4.3 <- facebook-oauth 1.8.0 <- accounts-facebook 1.3.2
   * http@1.4.2 <- google-oauth 1.3.0 <- accounts-google 1.3.3
   * http@1.4.1 <- accounts-twitter 1.4.2
   * http@1.4.2 <- oauth1 1.3.0 <- twitter-oauth 1.2.0 <- accounts-twitter 1.4.2
   * http@1.1.0 <- lukemadera:image-picker-manual 1.0.1
   * http@1.4.2 || 2.0.0 <- quave:apple-oauth 3.0.0 <- quave:accounts-apple 3.0.0

and this message repeats for each version of http. But when I look at the code in lukemadera:image-picker-manual 1.0.1 in package.js no version on http is used.


Package.onUse(function(api) {
  api.versionsFrom('1.1.0.2');

  api.use('templating');
  api.use('blaze');
  api.use('reactive-var');
  api.use('mdg:camera');
  api.use('classcraft:imagemagick');
  api.use('http');
  

  api.addFiles([
    'lib/Jcrop/jquery.Jcrop.min.css',
    'lib/Jcrop/jquery.Jcrop.min.js',
    'image-picker.html',
    'image-picker.css',
  ], 'client');
  api.addFiles([
    'image-picker.js',
    'image-picker-imagemagick.js'
  ]);
  api.addAssets([
    'lib/Jcrop/Jcrop.gif'
  ], 'client');

  api.export('lmImagePicker');
});

Please help in understanding how the meteor update program is identifying that lukemadera:image-picker-manual 1.0.1 is using http@1.1.0.
Is it trying to take the version from api.versionsFrom(‘1.1.0.2’)?

As written in the changelog and the blog post, you need to adjust the following:

to:
api.versionsFrom(['1.1.0.2', '2.3']);

That is after you check that you are not using any of the affected APIs that are broken (which in case of http should be none, but you need to check the behavior is still as you expect, or better migrate to fetch).

Thanks …removing api.versionsFrom also seemed to have worked