-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Metro Commander version 1.3.87.0 #18164
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @ValeraFinebits, |
Where can I find logs to find out what the problem is? |
Just tested the 1.3.86.0 Manifest and it seems to have the same issue
This was detected in #621 but it somehow got approved AFTER adding the |
Yes, I tested. It perfectly working locally. |
You're not wrong, it says locally... Should get changed to VM/Sandbox or properly tested.. When you manually run the installer it installs Microsoft Engagement Framework and Microsoft.UI.Xaml.2.3 Also you did get a answer from a technician #16142 (comment) |
I deleted Microsoft.Advertising.Xaml, but I can't remove the dependence on Microsoft.UI.Xaml. |
microsoft/winget-cli#163
Example of Dependency which exist in the winget pkgs repo
|
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @ValeraFinebits, Please verify the manifest file is compliant with the package manager 1.0 manifest specification. You could also try our Windows Package Manager Manifest Creator Preview. For details on the specific error, see the details link below in the build pipeline. |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @ValeraFinebits, |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @ValeraFinebits, |
Yeeeeh there is no way, you just have to wait for dependency support |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @ValeraFinebits, |
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