New version: pizzaboxer.Bloxstrap version 2.2.0

[pizzaboxer]

Pull request has been created with WinGet Releaser v2 🚀

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pizzaboxer]

Defer this PR until #102611 has some resolution.

[microsoft-github-policy-service]

Hello @pizzaboxer,

During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

[stephengillie]

@wingetbot waivers Add Validation-Unattended-Failed

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

The issue in previous PRs is that the dependency needs to be x86, but the x64 version is installed by default. Not sure how to specify dependency architecture. Would it be possible to upgrade the package to use the x64 dependency?

[pizzaboxer]

The issue in previous PRs is that the dependency needs to be x86, but the x64 version is installed by default. Not sure how to specify dependency architecture. Would it be possible to upgrade the package to use the x64 dependency?

Oh, I didn't realize that. The problem is that I publish both x64 and x86 versions of the application (for now), so I guess I could choose the option of not publishing x86 versions to Winget?

[microsoft-github-policy-service]

pizzaboxer,

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

[microsoft-github-policy-service]

Hello pizzaboxer,
Validation has completed.

Template: msftbot/validationCompleted

[stephengillie]

The issue in previous PRs is that the dependency needs to be x86, but the x64 version is installed by default. Not sure how to specify dependency architecture. Would it be possible to upgrade the package to use the x64 dependency?

Oh, I didn't realize that. The problem is that I publish both x64 and x86 versions of the application (for now), so I guess I could choose the option of not publishing x86 versions to Winget?

Thinking on this again, the x86 version needs to use the x86 dependency to work on 32-bit OSes. This is an issue with our validating, not your package. I'll work to solve this in my processes.

[pizzaboxer]

The issue in previous PRs is that the dependency needs to be x86, but the x64 version is installed by default. Not sure how to specify dependency architecture. Would it be possible to upgrade the package to use the x64 dependency?

Oh, I didn't realize that. The problem is that I publish both x64 and x86 versions of the application (for now), so I guess I could choose the option of not publishing x86 versions to Winget?

Thinking on this again, the x86 version needs to use the x86 dependency to work on 32-bit OSes. This is an issue with our validating, not your package. I'll work to solve this in my processes.

Thank you. I appreciate the response, though I wouldn't mind only publishing the x64 version since x86 usage is very small (about 4% according to GitHub releases), and it's due to be removed very soon anyway.

[wingetbot]

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