Closed marcprux closed 2 years ago
FTR, this started happening after https://github.com/actions/runner-images/issues/6283
Sorry, but we don't provide support for source builds. This includes building from --HEAD
. These can fail for a plethora of reasons and we don't have the resources to diagnose and fix them.
Is there any reason why you're not able to use the bottles? We provide them precisely so that users don't build from source.
I understand that building from source it isn't supported in general, but I need to build bottles from my own packages that aren't yet in homebrew-core. Like the homebrew testbot, I build and deploy the bottles from an ubuntu runner. I've been doing this for a year with no issues until now.
Looking at https://github.com/Homebrew/homebrew-core/actions/runs/3239943658/jobs/5310019666 , it appears that the bottling process is now happening on an ubuntu-22.04 runner. I'll try switching my runner to 22.04 and see if it helps.
22.04 will help, yes. We require glibc 2.35+ and ship our own if it's too old. Looks like Swift unfortunately still picks up the old glibc.
I'll look into it but if you can switch to 22.04, please do as it'll fix your issues.
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
Install a swift package like
create-api
from source on Ubuntu 20.05.5 with:brew install -v --head create-api
This same error seems to occur for all the swift packages (such as
swiftformat
andpublish
). It started happening around the time GitHub updated their Ubuntu runners, making me suspect there was some change to the glibc version. The errors do pre-date the update to swift 5.7 (I had been hoping that the 5.7 update would magically fix the build failures, but it didn't).What happened (include all command output)?
Full build log at https://github.com/marcprux/MemoZ/actions/runs/3266574514/jobs/5370502445
What did you expect to happen?
I expected
create-api
to be build and install like it used to.Step-by-step reproduction instructions (by running
brew
commands)In the GitHub runner environment, you can reproduce this with a workflow like the following (see the full workflow that results in the error at https://github.com/marcprux/MemoZ/blob/main/.github/workflows/ci.yml).