-
Notifications
You must be signed in to change notification settings - Fork 905
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
upgrade - prerelease with dependencies that are also prerelease fails to upgrade #1957
Comments
That's weird. I wonder if there are other things at play on this with the repository issues we've been having. Can we verify this against a source that is not https://chocolatey.org/api/v2? |
I am having the same issue with the What is interesting, is that it does detect that the package is outdated (and therefore, also understands that the installation is a prelease). I ran with
Running separate NuGet or Find-Package commands find the packages btw, although the nuget command output specifies the version differently than Find-Package (which one does choco use?)
|
How would I do that? |
Outdated and upgrade all specifically flips a switch on prereleases to do that. I would consider this an enhancement to allow upgrade do that if you have a prerelease installed. I think it would probably need to flip it on for the entire set of dependencies though. |
Maybe a bug... I went back and reread the previous issue that made it work for a package being a prerelease being upgraded - it properly handles that aspect. |
Not what I'm seeing... cup [pkg] -y
cup all -y
both appear broken w.r.t. this issue. #686 should be re-opened. |
@bc3tech I explained why the issue won't get reopened already at #686 (comment) So let's move past that and focus on this issue at hand. It looks like a bug, that prerelease dependencies are not also getting found for a prerelease. |
Put all the nupkgs in the same folder locally and use |
doesn't appear to change things
|
Good, that validates the issue is an issue. Thanks for that @bc3tech. I've marked this up as a bug and to be reviewed with the next release. This does have a workaround, but that workaround is not optimal. So hopefully this will be easy to find and fix. |
What You Are Seeing?
I cannot upgrade a prerelease package which has a prerelease dependency w/o specifying
-pre
tochoco upgrade
What is Expected?
chocolatey attempts to upgrade the package because it sees it's out of date - without
-pre
- so it should likewise update any prerelease dependenciesseealso my comment on #686
How Did You Get This To Happen? (Steps to Reproduce)
attempt
choco upgrade vivaldi
when an old prerelease package is installedOutput Log
Full Log Output
The text was updated successfully, but these errors were encountered: