-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
--include-unknown
not functioning as expected
#1939
Comments
Per discussion in the gitter channel, it seems like winget is not checking to see if there is a version of the app in the repository before putting it into the count of unknown packages. So if there isn't something in the repo to "update" to, then it shouldn't add it to the count. Shouldn't be that hard to fix, I'll try to write one if nobody else does. WinDirStat is a package where this is true, as winget can't find a eligible package during upgrade due to another upgrade bug. |
Another case that this happens is Edit: Seems like there is also a second portion to this bug that even if |
Not always, GOG shows up as available for upgrade with |
I see you guys talking about BlueScreenView and WinDirStat, the reason these are getting picked up is because it doesn't match the metadata because the Publisher is blank and its missing the ProductCode 🙃 |
I'm having a similar issue. `> winget upgrade --all No installed package found matching input criteria. 2 packages have version numbers that cannot be determined. Use "--include-unknown" to see all results. No applicable update found. 2 packages have version numbers that cannot be determined. Use "--include-unknown" to see all results.` `> winget upgrade No installed package found matching input criteria. `> winget upgrade --include-unknown No installed package found matching input criteria.` Something is broken here. |
Run "winget upgrade --include-unknown and show the results. If you don't have any that can be upgraded currently, adding include-unknown isn't going to change anything |
But is there any way to remove the line and get it to stop checking the package? |
There are several edge cases confounding the upgrade logic in WinGet. They range from inconsistent versioning behavior to no version being reported. We also have packages that do a better job of upgrading themselves due to services running or other packages using their libraries. In order to have the best possible experience with In some cases, running There are also cases where the scope or architecture doesn't match. These can be compounded by user preferences or requirements in settings. We're working to improve the messaging displayed to users to help with some of the confusion. We're also working on package pinning to help prevent unwanted upgrades. |
I agree that the message is quite misleading. It stated "Use |
I wrote that, I agree it is somewhat confusing. Maybe since we have the package index by time we do the "lets filter out all the unknown versions" part, we could just only show the "use --include-unknown" part if any of the unknown version packages actually exist in the repo. |
Brief description of your issue
When running
winget upgrade
it tells me a package has unknown version. When using--include-unknown
the package with unknown version is not listed and the upgrade list does not changeSteps to reproduce
Have a package with unknown version, run
winget upgrade --include-unknown
Expected behavior
A list of all upgradeable packages to be shown
Actual behavior
The list of packages does not change between
winget upgrade
andwinget upgrade --unknown
Logs attached for reference.
WinGet-2022-02-14-19-58-27.679_upgrade.log
WinGet-2022-02-14-19-58-35.901_IncludeUnknown.log
Environment
The text was updated successfully, but these errors were encountered: