Open 8549 opened 3 weeks ago
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Hi @8549,
The package manager matches data from the Registry with data from manifests. And it appears that we do have Firefox 126.0 described in a manifest. So the package manager should be matching the linked manifest with the data in the computer's Registry.
I'm guessing that the version of Firefox 126 on your computer is somehow different than the version of Firefox 126 described in the manifest in our repo, and this is causing the package manager to generate the error we see. The UpgradeBehavior
is to install
the newest version, but when the package manager tries to do this, it finds that certain bits aren't in the right buckets and this process becomes blocked.
Install method can be important, and installing with one kind of installer, then upgrading with another kind, is not recommended. Usually, the package manager gives an error, but maybe this is an unusual situation.
[!Note] While researching this, I came across a version of
Mozilla Firefox
(ID9NZVDKPMR9RD
) available through themsstore
source. This application has numerous installation paths.
Thank you for the information. Firefox was indeed installed with winget right after setting up the computer.
winget list -q firefox
Nome Id Versione Disponibile Origine
-------------------------------------------------------------
Mozilla Firefox Mozilla.Firefox 126.0.1.0 129.0.2 winget
I could try to go through the uninstall and reinstall ordeal, but I'd consider that a workaround rather than a "solution" -- considering the issue has been caused by the package manager itself. Do you have any other suggestion before I try to do that?
In this case, I'm not sure of the best route forward.
Brief description of your issue
When trying to upgrade Mozilla Firefox I receive this error message about a missing dependency:
I expected that winget is able to resolve any dependency tree issues. However, digging in the logs for the command execution, I find these interesting lines:
Which roughly translate to: "Impossible to install Mozilla Firefox 129 package. There's a different Mozilla Firefox 126 package with the same name. Before installing, remove Mozilla Firefox 126" which seems absurd to me because I'm asking winget to upgrade the package.
Steps to reproduce
winget upgrade -e Mozilla.Firefox
Expected behavior
winget is able to upgrade Mozilla Firefox just fine as it does for other packages
Actual behavior
winget is unable to upgrade Mozilla Firefox because another version of the package is already installed
Environment