Skip to content
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

Cannot upgrade from WinMerge 2.16.20.0 to WinMerge 2.16.22 #71609

Closed
sba923 opened this issue Aug 20, 2022 · 6 comments
Closed

Cannot upgrade from WinMerge 2.16.20.0 to WinMerge 2.16.22 #71609

sba923 opened this issue Aug 20, 2022 · 6 comments
Labels
Area-External Help-Wanted This is a good candidate work item from the community. Issue-Bug It either shouldn't be doing this or needs an investigation.
Milestone

Comments

@sba923
Copy link

sba923 commented Aug 20, 2022

Brief description of your issue

winget upgrade WinMerge.WinMerge cannot be done anymore at this point:

image

image

image

Steps to reproduce

Launch winget upgrade WinMerge.WinMerge from an elevated PowerShell prompt.

Expected behavior

WinMerge should get upgraded to version 2.16.20.0.

Or at least winget should fail without user interaction but with a clear error message.

Actual behavior

The command-line winget experience is blocked by an interactive dialog.

Environment

Windows Package Manager v1.3.2091
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22000.856
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2091.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
@ghost ghost added the Needs-Triage This work item needs to be triaged by a member of the core team. label Aug 20, 2022
@anirugu
Copy link

anirugu commented Aug 20, 2022

Edit the title to "Cannot upgrade from WinMerge 2.16.20.0 to WinMerge 2.16.22.0"

You mention 2.16.20.0 twice in your title, which make confusion.

@sba923 sba923 changed the title Cannot upgrade from WinMerge 2.16.20.0 to WinMerge 2.16.20.0 Cannot upgrade from WinMerge 2.16.20.0 to WinMerge 2.16.22 Aug 20, 2022
@sba923
Copy link
Author

sba923 commented Aug 20, 2022

Edit the title to "Cannot upgrade from WinMerge 2.16.20.0 to WinMerge 2.16.22.0"

You mention 2.16.20.0 twice in your title, which make confusion.

Oops, copy/paste glitch...

Fixed.

@denelon
Copy link
Contributor

denelon commented Aug 22, 2022

This looks like it's related to how the installer behaves. I'm wondering if there might be arguments that could be passed to the installer during upgrade that would suppress the dialog or at least return an error that could be mapped to one of the expected return codes.

@denelon denelon added Area-External Help-Wanted This is a good candidate work item from the community. Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage This work item needs to be triaged by a member of the core team. labels Aug 22, 2022
@ghost ghost added the Needs-Triage This work item needs to be triaged by a member of the core team. label Aug 22, 2022
@denelon denelon removed the Needs-Triage This work item needs to be triaged by a member of the core team. label Aug 22, 2022
@denelon denelon transferred this issue from microsoft/winget-cli Aug 22, 2022
@Trenly
Copy link
Contributor

Trenly commented Aug 22, 2022

Also somewhat related to microsoft/winget-cli#1786

Copy link
Contributor

Hello @sba923,

This issue has been identified as requiring a fix from a third party or external repository. Since there has been no recent activity on this issue, it will be automatically closed.

Template: msftbot/noRecentActivity/areaExternal

1 similar comment
Copy link
Contributor

Hello @sba923,

This issue has been identified as requiring a fix from a third party or external repository. Since there has been no recent activity on this issue, it will be automatically closed.

Template: msftbot/noRecentActivity/areaExternal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-External Help-Wanted This is a good candidate work item from the community. Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

4 participants