Migrate the macOS build docs and CI from pkg-config
to pkgconf
. As the former now just redirects to the later.
Upstream is currently mass-migrating its formula. i.e https://github.com/Homebrew/homebrew-core/pull/198317.
Fixes #31334.
Migrate the macOS build docs and CI from pkg-config
to pkgconf
. As the former now just redirects to the later.
Upstream is currently mass-migrating its formula. i.e https://github.com/Homebrew/homebrew-core/pull/198317.
Fixes #31334.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/31335.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | maflcko, hebasto |
Stale ACK | hodlinator |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
utACK fa9e7fb167d7a1c476af931610ccbae39e29b964
Don’t have a valid Mac to test on but change looks very straightforward and is in a similar vane to the linked upstream change.
Sounds like a TODO? Why not “Fixes #31334”?
Sure, changed to fixes. However it is a TODO in the sense that we shouldn’t need to do any of this for a working CI, and ideally, these changes should be removed at some point, as they are all workaround for other problems.
108@@ -109,7 +109,8 @@ jobs:
109 run: |
110 # A workaround for "The `brew link` step did not complete successfully" error.
111 brew install --quiet python@3 || brew link --overwrite python@3
112- brew install --quiet coreutils ninja pkg-config gnu-getopt ccache boost libevent zeromq qt@5 qrencode
113+ brew unlink pkg-config
pkgconf
is still broken, so we’d need to retain the workaround. We could also just update only the docs, and change the CI later if it starts breaking again.
brew update
. However, it might be time consuming.
unlink
is still required because the pkg-config
package is preinstalled in the GHA image.
Though, I am wondering if brew unlink pkg-config
will start failing once pkg-config is removed from the GHA image?
Wouldn’t a better fix be to drop the unlink
and the install and add a comment to add install pkgconf
in the future?
Wouldn’t a better fix be to drop the unlink and the install and add a comment to add install pkgconf in the future?
See #31335 (review).
Wouldn’t a better fix be to drop the unlink and the install and add a comment to add install pkgconf in the future?
See #31335 (comment).
IIRC you still tried to install. However, my recommendation is to do neither. Otherwise, either can fail, depending on the state of the GHA image.
I tested this in https://github.com/bitcoin/bitcoin/commit/4191e4a34c7f91fe1dfc68baa91998067a144619 and it passed. What am I missing?
Brew has migrated to using the later:
```bash
brew info pkg-config
==> pkgconf: stable 2.3.0 (bottled), HEAD
Package compiler and linker metadata toolkit
https://github.com/pkgconf/pkgconf
```
As pkg-config is now just redirected to the later, but changing this likely
depends on the GHA image being updated first.
ACK fe3457ccfff9a022d9f183e18217422e2e1f7689 🍭
Signature:
0untrusted comment: signature from minisign secret key on empty file; verify via: minisign -Vm "${path_to_any_empty_file}" -P RWTRmVTMeKV5noAMqVlsMugDDCyyTSbA3Re5AkUrhvLVln0tSaFWglOw -x "${path_to_this_whole_four_line_signature_blob}"
1RUTRmVTMeKV5npGrKx1nqXCw5zeVHdtdYURB/KlyA/LMFgpNCs+SkW9a8N95d+U4AP1RJMi+krxU1A3Yux4bpwZNLvVBKy0wLgM=
2trusted comment: ACK fe3457ccfff9a022d9f183e18217422e2e1f7689 🍭
3MAKSEnsFhDvAE/jAJfIhu71YebqfW2OqEWxmRpz6tOmZNLY5GlcCOrkV3BP1SqjgTdTSF89PyBEstFltNJrqAQ==
From the macOS 14 arm64 (20241125) Image Update:
Added:
pkgconf
2.3.0 Deleted:pkg-config
0.29.2