Nirsoft.Advancedrun version 1.51

[neomax7]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• 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.2 schema?

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

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[neomax7]

manifest v1.4 with zip

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @neomax7,

The package manager bot determined there was an issue with the pull request. Make sure the manifest files are under the manifests\partition\publisher\appname\version directory and only one package version is being modified in your PR. The partition of the path must be the first letter of the publisher in lower-case.

Example:
Path: manifests / m / Microsoft / WindowsTerminal / 1.6.10571.0 / WindowsTerminal.yaml

For details on the error, see the details link below in the build pipeline.

You may also try the Windows Package Manager Manifest Creator

Template: msftbot/validationError/pullRequest

[neomax7]

manifest version is 1.4 with zipped portable executable

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @neomax7,

The package manager bot determined there was an issue with the pull request. Make sure the manifest files are under the manifests\partition\publisher\appname\version directory and only one package version is being modified in your PR. The partition of the path must be the first letter of the publisher in lower-case.

Example:
Path: manifests / m / Microsoft / WindowsTerminal / 1.6.10571.0 / WindowsTerminal.yaml

For details on the error, see the details link below in the build pipeline.

You may also try the Windows Package Manager Manifest Creator

Template: msftbot/validationError/pullRequest

[neomax7]

the manifest version is 1.4 with zipped portable executable.

I have tested manifest locally with winget version v1.5.101-preview and it worked without any error.

I have forked the repository and tried to merge and it worked without any conflict.

could you please let me know if there is anything I can do to fix the pulling issue?

[ghost]

Hello @neomax7,

This package appears to reference a compressed .zip archive rather than an installer.

This PR is blocked until support for .zip is implemented in:

• Support installing .zip files winget-cli#140

Template: msftbot/blockingIssue/zipInstaller

[stephengillie]

the manifest version is 1.4 with zipped portable executable.

Each of these is somewhat of a blocker currently.

I have tested manifest locally with winget version v1.5.101-preview and it worked without any error.

I have forked the repository and tried to merge and it worked without any conflict.

could you please let me know if there is anything I can do to fix the pulling issue?

The successful install is encouraging. We're monitoring version adoption and hoping to start accepting packages like this at some point after 1.4 has sufficiently saturated into our userbase. If this package needs features in the 1.5 version, then it might unfortunately need to wait some time longer, until that version saturates.

[neomax7]

the manifest version is 1.4 with zipped portable executable.

Each of these is somewhat of a blocker currently.

I have tested manifest locally with winget version v1.5.101-preview and it worked without any error.

I have forked the repository and tried to merge and it worked without any conflict.

could you please let me know if there is anything I can do to fix the pulling issue?

The successful install is encouraging. We're monitoring version adoption and hoping to start accepting packages like this at some point after 1.4 has sufficiently saturated into our userbase. If this package needs features in the 1.5 version, then it might unfortunately need to wait some time longer, until that version saturates.

I understand, thank you 😁