1756101 - Firefox Developer fails to upgrade with the command "winget upgrade --id Mozilla.Firefox.DeveloperEdition"

Status: RESOLVED INVALID

(Firefox :: Installer, defect)

Description

[alex_mayorga]

Attachment: WinGet-2022-02-18-00-00-20.293.log

Steps:
Try to upgrade Firefox Developer with this command in a cmd.exe window:

winget upgrade --id Mozilla.Firefox.DeveloperEdition

Actual result:
The upgrade fails per the log attached.

Expected result:
The upgrade succeeds.

Comment 1

[alex_mayorga]

Attachment: WinGet-2022-02-18-01-11-38.645.log

Adding the command output:

C:\Users\AlexMayorgaAdame>winget upgrade --id Mozilla.Firefox.DeveloperEdition --verbose-logs
A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.

Attaching a verbose log.

Comment 2

[Robin Steuber (she/her) [:bytesized]]

@nalexander I believe this is Windows Store related. Can you shed any light on this?

Comment 3

[Robin Steuber (she/her) [:bytesized]]

Wait, is the Windows Store related? I see that in the search results, it lists the source for "Mozilla Firefox Browser" as "msstore", but it lists the source for "Firefox Developer Edition" as "winget". I don't really know enough about winget to know what that means.

@nalexander I'm hoping that you know more about this, because I'm pretty confused about what's going on here.

Comment 4

[Robin Steuber (she/her) [:bytesized]]

Ok, I just spent a bit of time reading up on winget. I think that I basically understand well enough; it's a package manager, not unlike other package managers.

We don't maintain those package managers or their listings. It is up to their maintainers to make sure that all of that works correctly. So you will need to file a bug with them. Possibly here, but I'm not entirely sure.

If they need us to work with them in order to make Firefox compatible with their repository, we are typically willing to do that. But, since winget is not our product, we do not debug it for them.

Comment 5

[Nick Alexander :nalexander [he/him]]

(In reply to Kirk Steuber (he/him) [:bytesized] from comment #4)

Ok, I just spent a bit of time reading up on winget. I think that I basically understand well enough; it's a package manager, not unlike other package managers.

We don't maintain those package managers or their listings. It is up to their maintainers to make sure that all of that works correctly. So you will need to file a bug with them. Possibly here, but I'm not entirely sure.

If they need us to work with them in order to make Firefox compatible with their repository, we are typically willing to do that. But, since winget is not our product, we do not debug it for them.

I concur. We don't yet publish our own MSIX packages for Devedition (see https://bugzilla.mozilla.org/show_bug.cgi?id=1738303), so winget must be producing its own packages. (Or perhaps they're fetching the ones we produce from TC or archive.m.o somehow?) In any case, the configuration is not (yet) supported.

Comment 6

[Robin Steuber (she/her) [:bytesized]]

(In reply to Nick Alexander :nalexander [he/him] from comment #5)

so winget must be producing its own packages.

They are coming from here. It appears that various contributors are submitting PRs to add Firefox versions to the repo and keep them up to date. For example, this one.

Comment 7

[Nick Alexander :nalexander [he/him]]

(In reply to Kirk Steuber (he/him) [:bytesized] from comment #6)

(In reply to Nick Alexander :nalexander [he/him] from comment #5)

so winget must be producing its own packages.

They are coming from here. It appears that various contributors are submitting PRs to add Firefox versions to the repo and keep them up to date. For example, this one.

Mmm. A mix of MSI and EXE. If winget supports MSIX, they'll have a much better experience migrating to MSIX (eventually, when we publish more versions).