Action doesn't work on Windows

[gmitch215]

Hello,

The action appears to fail on windows.

This issue was reported here on a different CI operating system, but that issue was solved. This only happens on windows runners.

Run dlang-community/setup-dlang@v2
  with:
    compiler: dmd
    gh_token: ***
    gdmd_sha: latest

Enabling dmd
Downloading https://downloads.dlang.org/releases/2.x/2.111.0/dmd.2.111.0.windows.7z
Verifying the download with GPG
C:\hostedtoolcache\windows\Ruby\3.4.4\x64\msys64\usr\bin\gpg.exe --lock-never --verify --keyring D:/a/_temp/128b5b8e-0994-4638-b839-ef6a09a7e514 --no-default-keyring D:/a/_temp/ee70e1a2-6033-45cb-be6e-0a9350152edf D:\a\_temp\d2eaf3b8-7d4d-44d8-b7d7-292317efe481
gpg: invalid key resource URL 'D:/a/_temp/128b5b8e-0994-4638-b839-ef6a09a7e514'
gpg: keyblock resource '(null)': General error
gpg: Signature made Mon, Mar 31, 2025 11:29:31 AM CUT
gpg:                using RSA key F3F896F3274BBD9BBBA59058710592E7FB7AF6CA
gpg: Can't check signature: No public key
The process 'C:\hostedtoolcache\windows\Ruby\3.4.4\x64\msys64\usr\bin\gpg.exe' failed with exit code 2
Error: The process 'C:\hostedtoolcache\windows\Ruby\3.4.4\x64\msys64\usr\bin\gpg.exe' failed with exit code 2

Related logs are available here.

[the-horo]

From the runner logs:

C:\hostedtoolcache\windows\Ruby\3.4.4\x64\msys64\usr\bin\gpg.exe --lock-never --verify --keyring D:/a/_temp/128b5b8e-0994-4638-b839-ef6a09a7e514 --no-default-keyring D:/a/_temp/ee70e1a2-6033-45cb-be6e-0a9350152edf D:\a\_temp\d2eaf3b8-7d4d-44d8-b7d7-292317efe481

When you install Ruby it is messing up PATH which makes gpg.exe resolve to a different program than the one that comes with the runner images. From a little testing in wine that version of gpg.exe expects the path passed to --keyring to be like /c/foo/bar/keyring so the C: drive become the directory /c, whereas gpg4win (which I assume is the one used by default by the github runners) expects the paths to be like C:/foo/bar/keyring so the drive letter appears normally. I couldn't find a common path format that is accepted by both programs.

As a quick fix I think installing dub before ruby should avoid the problem. As a better solution try to make ruby not setup a different flavor of gpg (rming the file seems appropriate if you can do it in the runner script).

I suppose adding an option to skip gpg verification in this action would also work but that, again, is only hiding the problem.

[gmitch215]

@the-horo Thank you, it works perfectly!

Adding an option to skip GPG verification could be good for testing/edge cases where the public key needs to be updated so that builds aren't broken.