-
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
upgrade --all installs packages that are already up to date #1075
Comments
I did see this issue looks to be related: #1009 And saw he ran
I am guessing thats the reason. |
It was previously discussed that the version displayed and the version number are not the same. There are even times when the commercial version number is different from the actual version number in the program itself. I cooperate with the AIMP player team and at the moment I was only able to make a limitation so that it would not be possible to downgrade the version number when updating. When a forced downgrade occurs, the player stops working with newer databases. |
Something similar happened to me. #1009 I did a first upgrade --all this 2 apps where updated, after that version becomes unknown and it tries to update every time although it is already updated. |
PS C:\Users\NLxDoDge> winget upgrade
Name Id Version Available Source
----------------------------------------------------------------------------------------------
AIMP AIMP.AIMP v4.70.2251, 23.05.2021 4.70.2251 winget
Battle.Net Blizzard.BattleNet Unknown 1.22.0.12040 winget
Bulk Rename Utility TGRMNSoftware.BulkRenameUtility Unknown 3.4.3.0 winget
Discord Discord.Discord 1.0.9000 1.0.9002 winget
MEGASync Mega.MEGASync Unknown 4.5.1.0 winget
Mozilla Thunderbird Mozilla.Thunderbird 78.10.2 78.11.0 winget
GOG Galaxy GOG.Galaxy Unknown 2.0.37.384 winget
Windscribe Windscribe.Windscribe 2.2 Build 10 latest winget These are all packages that have issues on my personal system. Each of these is the latest version, but tries to update. Windows Package Manager v1.0.11451 |
I just experienced this issue. |
Found another package that updates infinitely:
|
I have the same problem with Windscribe.
|
I also have this problem and I have it with Display Fusion installed from steam because in program and features there are two entries of display fusion one is for steam and the other one is for display fusion when installed normally. "DisplayFusion 9.8" is the entry which is also created by standard installer when installing display fusion from official website but that entry called just "DisplayFusion" without any numbers is created by steam but winget falsely detects the steam entry instead of standard entry. Here is screenshot of winget upgrade In some cases Unknown version is created by laziness of app developer to add proper version number to application. |
|
I believe we can address this with the v1.1 schema with multiple ARP entry support. The version in the manifest will be able to report a "marketing" version, but the ARP entry section can match what is actually installed. |
This is similar to this issue: #1105 |
Version being reported as Unknown - This generally happens when a package does not provide a version in the Apps & Features entries that Windows Package Manager looks at. We are trying to improve this experience by providing an option to the publishers to add Apps & Features entries in the package manifest. Packages with version as Latest - Some packages have version as "Latest" instead of specific version numbers like "1.2.3" in their manifests in winget-pkgs GitHub repo and are frequently updated. Thus Windows Package Manager attempts to update such packages whenever it sees a package with "Latest" version. Packages that upgrade themselves - Some packages do upgrade themselves and might not want Windows Package Manager to upgrade or show them in the list. We are trying to improve this by providing an option to publishers to specify if a package upgrades itself in the package manifest. Side by side installs - There is another open issue for those packages that allow multiple versions of the same package to be installed side by side and need not be upgraded when a latest version already exists on the machine. |
I believe this has been addressed with Windows Package Manager 1.3. Unknown versions are excluded from Manifests can also now have AppsAndFeatures entries to allow a "marketing" version displayed for the user, but the upgrade comparison will be performed against the registry value for the software. If this is not the case, then feel free to re-open the Issue and provide feedback. |
Hi @denelon, There is still an issue with repeated installation.
|
Brief description of your issue
When I run the
winget upgrade --all
winget tries to upgrade software that are already the latest.In this example, it tried to update 2 software.
I should mention that I had these apps installed form their respected websites before I had winget installed.
Steps to reproduce
I opened the term application as admin, and executed
![winget upgrade](https://user-images.githubusercontent.com/25173863/120485642-979b5080-c3b4-11eb-9d79-c8c573b52ba8.jpg)
winget upgrade --all
In the attached screenshot, you will see I have discord, and AIMP open with their versions before I ran the update.
Discord's installed version is
1.0.9002
AIMP's installed version is
4.70.2251
Initially I thought it might be related to this issue: #696 (comment)
But when I checked the versions for both apps, I saw that winget lists the same versions that was installed.
To see the discord version, I ran:
winget search discord
To see the AIMP version, I ran:
winget search aimp
Expected behavior
I expected that when the upgrade command is executed, that software that are up to date doesn't try to download and install the same version.
Actual behavior
Up to date software gets re-downloaded and installed (in the example, Discord and AIMP).
Environment
The text was updated successfully, but these errors were encountered: