Update: Add Machine Scope DuongDieuPhap.ImageGlass.installer.yaml

[PckgrBot]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[PckgrBot]

#133123

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -1978334972

(Automated response - build 530.)

[PckgrBot]

@stephengillie any advice on how I get solve this?

[stephengillie]

Manual Validation ended with:

[stephengillie]

This needs to be added at line 61. GitHub doesn't make it easy to suggest this.

  - PackageIdentifier: Microsoft.DotNet.DesktopRuntime.8

[PckgrBot]

This needs to be added at line 61. GitHub doesn't make it easy to suggest this.

  - PackageIdentifier: Microsoft.DotNet.DesktopRuntime.8

Unless I'm missing something this is already in the manifest at line 61?

[stephengillie]

Unless I'm missing something this is already in the manifest at line 61?

Yes, it is. Somehow it was missing from the version I was working with yesterday.

[stephengillie]

Unless I'm missing something this is already in the manifest at line 61?

Yes, it is. Somehow it was missing from the version I was working with yesterday.

I see why now - I launched this validation with Get-ManifestFile which leverages Get-SecondMatch to perform the Get-Clipboard operation, then finds any 2 lines that have the same data before the colon, and clobbers the first. Because usually it's an old and new SHA256 key or other duplicated value. This is the first instance of an intentionally duplicated value, effectively.

[PckgrBot]

Unless I'm missing something this is already in the manifest at line 61?

Yes, it is. Somehow it was missing from the version I was working with yesterday.

I see why now - I launched this validation with Get-ManifestFile which leverages Get-SecondMatch to perform the Get-Clipboard operation, then finds any 2 lines that have the same data before the colon, and clobbers the first. Because usually it's an old and new SHA256 key or other duplicated value. This is the first instance of an intentionally duplicated value, effectively.

OK all good! Let me know if you think there is anything else I can change.

[stephengillie]

@wingetbot waivers Add Validation-Installation-Error

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.