/AzurePipelines run

Automatic Validation ended with:

2024-04-05 07:35:26.318 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFC396BC11F: (caller: 00007FFC39448D6F) LogHr(1) tid(15d8) 8A15005E Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFC395C2B08: (caller: 00007FFC3966BC20) Exception(1) tid(15d8) 8A15005E ]
2024-04-05 07:35:26.318 [REPO] Failed to open available source: msstore
2024-04-05 07:35:34.198 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFC21B0C11F: (caller: 00007FFC21898D6F) LogHr(1) tid(aec) 8A15005E Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFC21A12B08: (caller: 00007FFC21ABBC20) Exception(1) tid(aec) 8A15005E ]
2024-04-05 07:35:34.198 [REPO] Failed to open available source: msstore
2024-04-05 07:35:35.683 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0

(Automated response - build 876.)

2024-04-05 07:35:35.683 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0

@denelon - This definitely seems to be a CLI issue and not a manifest issue

This version of VCRedist appears to not have a user scope. Could this be a scope mismatch?

This version of VCRedist appears to not have a user scope. Could this be a scope mismatch?

It's possible. Unless something changed in the CLI or pipelines recently though, I thought that the scope was omitted when searching for dependencies?

I can very easily foresee many, many cases where a dependency is only available in machine scope but the requested package is available in both user or machine scope.

I also know that many wix and burn packages have machine scope specified because the installers only ever write to HKLM even if it is a user scoped install.

If the dependency flow takes a hard requirement when --scope is passed in, then many manifests which were previously working may now be broken due to newer versions of the dependent package specifying scope differently than expected

Scope should not matter in the installer verification pipeline with regard to dependencies in my opinion. The winget client can easily accommodate a machine scope dependency (in a user scope install) by prompting for admin elevation. This installer failure where dependencies are concerned is new behavior.

I had the very same issue with the recent 2.1.0 Sigil-Ebook.Sigil update: #147284

My only recourse to get it merged was to remove the dependency from the user scope installer altogether. I don't find that to be a very pleasing workaround.

A further note: the VCRedist.2015+.x64 dependency package in my manifests has never had a user scope installer available. And it never mattered to my manifests in the past.

@wingetbot run

/AzurePipelines run

Automatic Validation ended with:

2024-04-08 11:17:39.309 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFA5924C11F: (caller: 00007FFA58FD8D6F) LogHr(1) tid(1ea4) 8A15005E Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFA59152B08: (caller: 00007FFA591FBC20) Exception(1) tid(1ea4) 8A15005E ]
2024-04-08 11:17:39.309 [REPO] Failed to open available source: msstore
2024-04-08 11:17:47.858 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFA3908C11F: (caller: 00007FFA38E18D6F) LogHr(1) tid(18a0) 8A15005E Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFA38F92B08: (caller: 00007FFA3903BC20) Exception(1) tid(18a0) 8A15005E ]
2024-04-08 11:17:47.859 [REPO] Failed to open available source: msstore
2024-04-08 11:17:49.119 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0

(Automated response - build 876.)

Still pending investigation on the cli side

/AzurePipelines run

Automatic Validation ended with:

2024-05-07 12:27:05.169 [REPO] Failed to open available source: msstore
2024-05-07 12:27:13.367 [REPO] Failed to open available source: msstore
2024-05-07 12:27:14.703 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0

(Automated response - build 880.)

Bump

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