-
-
Notifications
You must be signed in to change notification settings - Fork 285
RFC: Warn if ] up Foo is not able to install the latest version of Foo
#1606
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
RFC: Warn if ] up Foo is not able to install the latest version of Foo
#1606
Conversation
]up Foo is not able to install the latest version of Foo]up Foo is not able to install the latest version of Foo
Codecov Report
@@ Coverage Diff @@
## master #1606 +/- ##
==========================================
- Coverage 86.57% 86.52% -0.06%
==========================================
Files 24 24
Lines 5370 5416 +46
==========================================
+ Hits 4649 4686 +37
- Misses 721 730 +9
Continue to review full report at Codecov.
|
|
Awesome! I feel like the phrasing could be a bit clearer, but it's a bit tricky. Maybe |
That looks good to me! |
]up Foo is not able to install the latest version of Foo] up Foo is not able to install the latest version of Foo
Done. |
|
How about also mentioning the command to get more information ( Also, it could be useful to explicit say that this is because of version incompatibilities between installed packages. Otherwise the user could think it's because of a network problem, a bug in Julia, etc. |
|
What about a table format? In "Packages holding it back" I'd envision listing only those packages present in the |
|
Maybe use |
|
Just pointing it out that I have a little script that lists all packages where their last version hold back any other package: https://gist.github.com/KristofferC/7c8048e2ee9aaa465966caeb98c1446a#file-script-jl with the result: https://gist.github.com/KristofferC/7c8048e2ee9aaa465966caeb98c1446a#file-packages_holding_back-md. I am not sure it makes sense to tie displaying this information to |
|
Yea, this doesn't seem specific to |
|
The thing I am normally interested in isn't if it updated to the latest release, but if it updated to the latest version permitted by my current environment's Project.toml. |
|
Yeah, makes sense. |
|
I think having a couple of specific debugging/info commands could be useful, for example I was trying to install an older version of a package but couldn't figure out what was preventing it from the error message. Being able to list all the current requirements for a package would help. |
|
Sorry, I completely forgot about this PR. It seems like the consensus is to close this PR, and maybe in the future add a dedicated function |
|
I think it makes sense for I think a separate function to show compat info for the whole project would be great too. |
I'll close this in favor of adding a dedicated function. |
Fixes #1605
Usage:
] up] up FooFoocan't be updated to latest] up Foo Bar BazFoo,Bar,Bazcan't be updated to latest] up -w] up -w -p] up -w -p] up -w -mExample output:
Click to expand