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

`meteor update --all-packages` is not documented in help.txt #8154

Closed
glasser opened this issue Dec 14, 2016 · 5 comments
Closed

`meteor update --all-packages` is not documented in help.txt #8154

glasser opened this issue Dec 14, 2016 · 5 comments
Assignees

Comments

@glasser
Copy link
Member

@glasser glasser commented Dec 14, 2016

The flag meteor update --all-packages added in #7653 is not mentioned in meteor help update.

@deadjdona
Copy link

@deadjdona deadjdona commented Jan 6, 2017

And it do not work properly ^_^

$ meteor update --all-packages
This project is already at Meteor 1.4.2.3, the latest release.
Your top-level dependencies are at their latest compatible versions.

Newer versions of the following indirect dependencies are available:

  • aldeed:collection2-core 1.2.0 (2.0.0 is available)
  • aldeed:schema-deny 1.1.0 (2.0.0 is available)
  • aldeed:schema-index 1.1.1 (2.0.0 is available)
  • coffeescript 1.11.1_4 (1.12.0_1 is available)
    To update one or more of these packages, pass their names to meteor update, or just run meteor update --all-packages.
@abernix
Copy link
Member

@abernix abernix commented Jan 16, 2017

@deadjdona meteor update --all-packages actually does work in the sense that it updates all possible packages to the latest versions possible based on the other package constraints in your project, but the message it provides is a bit confusing, I agree. The problem you're encountering is that there are some impossible constraints that are preventing you from upgrading to those higher versions of those four packages (e.g. aldeed:*, coffeescript). You can get more information about exactly which package is preventing the upgrade by running (for example):

meteor add aldeed:collection2-core@2.0.0

(Just replace the package name and version with the package listed in the "Newer versions" message)

I'm going to try to improve this message soon to make it more clear what the problem is.

@hwillson
Copy link
Member

@hwillson hwillson commented Feb 27, 2017

Hi @abernix - I just submitted PR #8431 to help address the issue of the missing help text. Since that should hopefully help address the original issue here, what do you think we should do with the issue of the unhelpful version solver messages (#8154 (comment))? Issue #5270 exists to track this already, so maybe that's enough? Thanks!

@abernix
Copy link
Member

@abernix abernix commented Mar 3, 2017

@hwillson #5270 is sufficient to track the rest of this problem (which is actually the output from the command versus the help itself), but your PR will fix this. Thanks for opening #8431!

@abernix abernix added this to the Release 1.4.3.x milestone Mar 9, 2017
@abernix
Copy link
Member

@abernix abernix commented Mar 9, 2017

Thanks for reporting, @glasser. This should be released with Meteor 1.4.3.2.

meteor update --release 1.4.3.2-beta.0
@abernix abernix closed this Mar 9, 2017
@abernix abernix modified the milestones: Release 1.4.3.x, Release 1.4.3.2 Mar 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.