-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Packages that do not upgrade o report incorrect package version #1192
Comments
TLDR; This is a winget CLI issue, the package versions are correct
Geekbench is not reporting its version so that is a Geekbench issue.
|
Might be related to this #1191 (comment) |
@KaranKad That does indeed seem to fix the Mozilla and WhatsApp issues. Hopefully when those packages get an update, I won't have the same problem. |
So geekbench doesn't report the correct version, it seems like it would make sense for winget-cli to then fallback gracefuly to the verison recorded in the Manifest? That should be doable if winget records the installed version for packages through winget-pkgs. |
We've started recording the packages installed by Windows Package Manager. The challenge is we're not informed when a user performs an upgrade outside of the package manager, and if they don't report the version information in Windows Apps & Features. We have no way of knowing which version is currently installed. We could still inadvertently downgrade a user. |
I think we've captured the scenarios here in Windows Package Manager 1.3 Release Candidate. The exclusion of "Unknown" packages by default in Can you confirm? |
@musm this issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
The following packages
Prepetually state that they are upgradable, despite upgrading them multiple times. I suspect there is an issue somewhere with the packages reporitng their version numbers.
The text was updated successfully, but these errors were encountered: