You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the update to 2.3.0 I see on Homebrew this message:
opam believes some required external dependencies are missing. opam can:
> 1. Run brew to install them (may need root/sudo access)
2. Display the recommended brew command and wait while you run it manually (e.g. in another terminal)
3. Continue anyway, and, upon success, permanently register that this external dependency is present, but not detectable
4. Abort the installation
[1/2/3/4] 4
Since I cannot reproduce this locally (I am locally using MacPorts), I need a way to know what went wrong in the CI runner. It would really help if opam would default to list the brew commands.
Also a general `--headless' option would help, which would produce more useful output in headless scenarios.
I must say I don't quite understand how my build works with homebrew. The log says that bison is keg-onlyref which means it is not put into the PATH by homebrew. On the other hand I am sure that I have packages which cannot live with the MacOS supplied bison 2.3. So somehow opam manages to get the brew keg-only packages in the path - or the github runners come by default with an updated bison. I have 8 such keg-only dependencies, according to the log.
The text was updated successfully, but these errors were encountered:
Since the update to 2.3.0 I see on Homebrew this message:
See https://github.com/coq/platform/actions/runs/11838273102/job/32987032575#step:7:631
Since I cannot reproduce this locally (I am locally using MacPorts), I need a way to know what went wrong in the CI runner. It would really help if opam would default to list the brew commands.
Also a general `--headless' option would help, which would produce more useful output in headless scenarios.
Note: I saw that
conf-bison
has two hands - see https://github.com/coq/platform/actions/runs/11838273102/job/32987032575#step:7:631.Does this mean there is an issue with
conf-bison
?I must say I don't quite understand how my build works with homebrew. The log says that
bison is keg-only
ref which means it is not put into the PATH by homebrew. On the other hand I am sure that I have packages which cannot live with the MacOS supplied bison 2.3. So somehow opam manages to get the brew keg-only packages in the path - or the github runners come by default with an updated bison. I have 8 such keg-only dependencies, according to the log.The text was updated successfully, but these errors were encountered: