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

Multiple separate version reports upon winget upgrade #1258

Closed
cilerler opened this issue Jul 6, 2021 · 4 comments
Closed

Multiple separate version reports upon winget upgrade #1258

cilerler opened this issue Jul 6, 2021 · 4 comments
Milestone

Comments

@cilerler
Copy link

cilerler commented Jul 6, 2021

Steps to reproduce

The following command will install the package that I identified with the issue.

winget install Microsoft.dotnet;

Expected behavior

winget upgrade should not report two separate versions for the same package.

Actual behavior

It shows the same package with different versions.

image

Environment

Windows Package Manager v1.0.11692
Windows: Windows.Desktop v10.0.19043.1052
Package: Microsoft.DesktopAppInstaller v1.12.11692.0
@ghost ghost added the Needs-Triage Issue need to be triaged label Jul 6, 2021
@denelon
Copy link
Contributor

denelon commented Jul 6, 2021

The .net SDK does get treated as different "packages". They run side by side so other packages with version specific dependencies don't break. There are several other issues discussing this topic.

@cilerler
Copy link
Author

cilerler commented Jul 6, 2021

Thanks, @denelon, and that is precisely my point. It should treat them as separate packages since you may want to have 5.1.200 and 5.2.100 side by side, and that doesn't mean that it should suggest upgrading all to 5.3.0

If you don't mind, can you give me a reference issue that covers the problem here to close this one. Thank you so much for your attention and participation.

@denelon
Copy link
Contributor

denelon commented Jul 6, 2021

@cilerler, this is the latest comment:

microsoft/winget-pkgs#17985 (comment)

@cilerler
Copy link
Author

cilerler commented Jul 6, 2021

Perfect, thank you! Closing this issue since it is a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants