Kaleb Luedtke
Kaleb Luedtke
@wingetbot run
@wingetbot run
@wingetbot run
@denelon - Can we maybe think about pulling this into 1.4? Based on @lechacon's comment above, it seems like it wouldn't be too difficult, and this bug is causing several...
I would suggest `--include-unsupported` instead of `--show-unsupported-packages`, to better align with `--include-unknown` and to make it more command agnostic
Thinking about this further - Is this something that can be applied only to specific manifest versions? E.g - Can 1.0.0 to 1.2.0 be validated as string, and 1.4.0 be...
> I don't know of a clean way of implementing it into the Schema I've thought a little on this - ```yaml ElevationRequirement: Silent: SilentWithProgress: Interactive: ``` To avoid this...
This is very much related to #2453 and my subsequent [response](https://github.com/microsoft/winget-cli/issues/2453#issuecomment-1218262365) regarding what the NASM installer actually does. Because winget doesn't explicitly control the default install location, and the fact...
@denelon - Beat me by seconds again!!
This is actually an issue with NASM itself. When the publishers created the installer for NASM, they are not setting any Registry Entries in the Add & Remove Programs table....