Open wmmc88 opened 1 week 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.
It seems like the version of Microsoft.Winget.Client
available in this repo, is not the same as what is published to PSGallery
.
Get-WinGetPackage doesn't support an -Exact
option. Try using -MatchOption Equals
instead
~ Get-Help Get-WinGetPackage
NAME
Get-WinGetPackage
SYNTAX
Get-WinGetPackage [[-Query] <string[]>] [-Tag <string>] [-Command <string>] [-Count <uint>] [-Id <string>] [-Name <string>] [-Moniker <string>]
[-Source <string>] [-MatchOption {Equals | EqualsCaseInsensitive | StartsWithCaseInsensitive | ContainsCaseInsensitive}] [<CommonParameters>]
ALIASES
None
REMARKS
None
As pointed out by the GitHub bot, this is related to:
[comment]: <[Policy] PowerShell> [comment]: <[Policy] Issue-Docs>
It seems like the version of
Microsoft.Winget.Client
available in this repo, is not the same as what is published toPSGallery
.
Is the updated source available somewhere?
Brief description of your issue
I'm getting different behavior between
winget list -Exact
andGet-WinGetPackage -Exact
, and it looks like the-Exact
option ofGet-WinGetPackage
is bugged. When-Exact
is passed toGet-WinGetPackage
, it is always returning nothing.Steps to reproduce
Expected behavior
I expected the output of
Get-WinGetPackage -Id Microsoft.WindowsTerminal -Source winget -Exact
to matchwinget list --id Microsoft.WindowsTerminal --exact
Actual behavior
Get-WinGetPackage -Id Microsoft.WindowsTerminal -Source winget -Exact
returns nothingEnvironment
winget powershell module info: