Closed dennisameling closed 1 year ago
Here's a successful CI run of building git-extra
that has this fix applied: https://github.com/dennisameling/git-for-windows-automation/actions/runs/3771761998/jobs/6412324785
Here's a successful CI run of building
git-extra
that has this fix applied: https://github.com/dennisameling/git-for-windows-automation/actions/runs/3771761998/jobs/6412324785
And here is a successful run that built and deployed mingw-w64-aarch64-git-extra
: https://github.com/git-for-windows/git-for-windows-automation/actions/runs/3825495631/jobs/6508527516
Now https://wingit.blob.core.windows.net/aarch64/git-for-windows.db is ready to rumble.
Thank you so much @dennisameling!
Now https://wingit.blob.core.windows.net/aarch64/git-for-windows.db is ready to rumble.
Even more importantly, https://wingit.blob.core.windows.net/aarch64/git-for-windows-aarch64.db is ready to rumble. That means that we can finally add that [git-for-windows-aarch64]
section to /etc/pacman.conf
.
Yay! That's great news! Thank you! š
As reported here, the
Get GPG key(s)
step wasn't working on arm64.After way too many (failed) attempts to fix things, I debugged by trying
gpg-agent --daemon
directly in the pipeline and found the following:Doh š¤¦š¼āāļø I changed the path of the runner from
D:\actions-runner
toD:\a
to get below the 100-character limit. Note that GH does this too on their hosted runners, that's why it didn't fail on the x86_64 job. See e.g. this x86_64 run.