Closed ktooi closed 3 weeks ago
@ktooi Thanks for letting us know, I wasn't aware that we were available via winget
, as we do not maintain that installation path (similar to how we don't maintain our own snap
).
So this should likely be reported to the user that created this, or perhaps a change can be submitted to the repo where this exists. The solution you provided seems to be the way forward.
Closing this ticket as there isn't anything we can do from our end.
Checks before filing an issue
Mattermost Desktop Version
5.9.0
Operating System
Windows 11 x64
Mattermost Server Version
9.5.6
Steps to reproduce
Here is what Mattermost-desktop looked like before installation. It is not installed in either the user or machine scope.
Install Mattermost-desktop into the machine scope using winget.
Expected behavior
If “--scope machine” is specified, it is expected to be installed under Program Files.
Observed behavior
But in fact, it has been installed in the wrong user scope. This is a post-installation state, confirming that Mattermost-desktop was installed in the wrong user scope.
Log Output
Additional Information
I checked https://docs.mattermost.com/install/desktop-msi-installer-and-group-policy-install.html#install-for-all-users and found that “ALLUSERS=1” I checked and understood that I needed to specify “ALLUSERS=1”. So I installed with “--custom ALLUSERS=1” and confirmed that it was installed under Program Files as expected.
This led me to believe that there was a problem with the Winget manifest. https://github.com/microsoft/winget-pkgs/blob/master/manifests/m/Mattermost/MattermostDesktop/5. 9.0/Mattermost.MattermostDesktop.installer.yaml, I think you are missing the InstallerSwitches specification.
I thought about submitting a PR to the winget-pkgs repository, but then I saw the following in the manifest file, so I assumed this file was auto-generated.
I don't know if this is the right place for this bug report, but I could not find another appropriate place to report it. Please let me know if there is another correct place to report it.
Thanks.