Hi @sethrj! I noticed that the following package(s) don't yet have maintainers:

• go-bootstrap

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers = ['sethrj']

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame go-bootstrap

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

Thanks @becker33 for giving me the missing syntax!

@sethrj can you rebase this on develop? The CI bugfix has been merged

@becker33 I thought I'd replied to your question but it seems not to be showing up:

It can't build from gcc languages=go?

GCC can't build yet on M1 (GCC12 is required but not yet released). The Homebrew GCC doesn't include golang support, and even then there are environment variables missing from the go build step that would be needed to work. This also triggered #28827 which tried to make my external GCC "automatically" gain go support even when it's missing.

ping @becker33

Ping @becker33

Thanks for reviewing @trws !