Guillaume Bougard

Hi, I had the same problem on building GLPI-Agent which is based on StrawberryPerl. The build occurs in the GH Actions windows latest image context. It seems to use StrawberryPerl...

Hi, I confirm there's still a problem. In [my last run](https://github.com/glpi-project/glpi-agent/actions/runs/9028671669/job/24812194237), I still obtained this error: ``` ##2024/04/10-09:06:27## [step:3] starting 'UpgradeCpanModules' getting upgrade module list ##2024/04/10-09:06:28## BUILD FAILURE: Inappropriate I/O...

Indeed, `candle.exe` & `light.exe` are required by `OutputMSI` and the related step will fail if run with not functional such binary. But you can remove the related step from your...

> @g-bougard That's what I am doing. Can you at least share the output showing your issue ? And maybe your script ?

I don't know if it's really related to your issue, but I'm thinking to enhance **Collect task** to support `JSON file parsing` to permit collecting specific data from a well-known...

Hello there, maybe using [SignPath](https://signpath.org/) is the solution and they supports GH Actions. A lot of OpenSource project are still using freely this service as exposed here: https://signpath.org/projects

Imho, "just" forking perl repo into StrawberryPerl orga and adapt build processes to use the fork could be sufficient to adhere the terms. The question could probably be discusses with...

Hi @genio > Either way, having someone work with us to update our Wix configuration to include the certs and clean up some other things is still a pain point...

Thanks @shawnlaffan for the point. Yes, 6 hours is really an issue. Here maybe Perl::Dist::Strawberry module "Step" concept is not adapt to GH Actions processing. I think, but maybe I'm...

Hi @shawnlaffan as far I understand attest-build-provenance workflow only permits to use a command to verify the provenance of a binary. This seems not a way to sign a binary...