-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Olympus.Olympus version 21.01.11.07 #95906
Olympus.Olympus version 21.01.11.07 #95906
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@lemonjacob - I'm not sure what happened, but anytime I try to check out the commit to test it, I get |
…6fb890-2ec7-4799-b07b-8f9215067ea3
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Head branch was pushed to by a user without write access
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
I think I fixed it |
Thanks! Looks like git is detecting it as a valid tree now, will test! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Policy] Dependencies
@stephengillie / @denelon - Hardware too please
manifests/o/Olympus/Olympus/21.01.11.07/Olympus.Olympus.installer.yaml
Outdated
Show resolved
Hide resolved
manifests/o/Olympus/Olympus/21.01.11.07/Olympus.Olympus.locale.en-US.yaml
Outdated
Show resolved
Hide resolved
Hello @wingetbot, The package manager bot determined there was an issue with one of the installers listed in the url field, and cannot continue. The application included in this pull request failed to install during dynamic validation. This test is designed to ensure that the application installs on all environments without warnings. Please, verify that the application installs correctly on architectures specified in the manifest using winget cli. Template: msftbot/validationError/installers/shellExecute |
…ler.yaml Change to package name to match publishers name Co-authored-by: Kaleb Luedtke <trenlymc@gmail.com>
/AzurePipelines run |
Change package name name to match publishers name Co-authored-by: Kaleb Luedtke <trenlymc@gmail.com>
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
….en-US.yaml Change package name to match publishers name Co-authored-by: Kaleb Luedtke <trenlymc@gmail.com>
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @wingetbot, The package manager bot determined that the metadata was not compliant. Please verify the manifest file is compliant with the package manager 1.4 manifest specification. You could also try our Windows Package Manager Manifest Creator or the YamlCreate script. For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/metadata |
Hello @denelon, This package appears to require specific hardware. This PR is blocked until support for specific hardware requirements is implemented in: Template: msftbot/blockingIssue/hardwareDependency |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow