New Version: Sigil-Ebook.Sigil version 2.1.0#147284
New Version: Sigil-Ebook.Sigil version 2.1.0#147284microsoft-github-policy-service[bot] merged 4 commits intomicrosoft:masterfrom dougmassay:Sigil-Ebook.Sigil-2.1.0-65391d95-afb3-4eae-b7b5-c2506e68e7b7
Conversation
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
I need just a little more to go on than "issue with installing the application" nothing has changed regarding the installer. It works fine everywhere I've tried it. |
|
Automatic Validation ended with:
(Automated response - build 876.) |
|
So it can't install the latest Microsoft.VCRedist.2015+.x64 dependency via it's winget manifest? I'm unaware of anything I can do to affect how that particular dependency gets installed. I've named the dependency correctly in my installer yaml. Surely I don't need to specify an exact version of the VCRedist.2015+.x64 package? |
|
Please advise. I'm seeing this error all over the place here. I can't fix a broken VCRedist.2015+.x64 dependency install by pushing more changes to my branch. |
|
@wingetbot run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
As mentioned previously, there is nothing for me to "fix." something has changed RE dependency packages that is breaking the Azure Pipeline. See #147337 No ability to see any detailed logs referenced above - #147284 (comment) - concerning the error. |
|
Automatic Validation ended with:
(Automated response - build 876.) Edit:
The issue seems to be a scope mismatch. I believe the dependency only has |
There was never a scope mismatch in the past. My yaml hasn't really changed (other than urls, shas, and version numbers) in a long time. If the dependency has changed their scope options, I'm at a loss as to how my package can possibly be installed with the user scope anymore. I'd rather not have to assume the necessary vc++ redist libraries are already installed by removing the dependency from my installer yaml altogether. |
Remove Dependencies property from root of manifest to eliminate a scope mismatch on vcredist dependency. Not an ideal workaround, but I'm tired.
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
=== manifests\s\Sigil-Ebook\Sigil\2.1.0 === |
|
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Checklist for Pull Requests
Manifests
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