-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ocaml 5.2.0 #172795
ocaml 5.2.0 #172795
Conversation
Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request. |
c65731c
to
3d2bed1
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
3d2bed1
to
bd54380
Compare
This comment was marked as resolved.
This comment was marked as resolved.
I'm not sure where the test is in the brew build process, but the problem is that where you load "pr_o.cmo", now you must load "o_keywords.cmo pr_o.cmo". But the old way of invoking camlp5 for preprocessing (e.g. "camlp5 pa_o.cmo pr_o.cmo") is cumbersome and predates findlib. Instead you can use "not-ocamlfind preprocess -syntax camlp5o -package camlp5.pa_o,camlp5.pr_o") as is done here: https://github.com/drjdn/p5scm/pull/4/files |
Yes, "pr_op.cmo" provides extensions to the "pr_o.cmo" printer. The entire methodology of loading individual .cmo files into the camlp5 process is flawed, b/c you have to specify all the files you want, and in a compatible load-order. There is no way to get inference of which other files are needed, for the files you specify, etc. All of this sort of thing is the proper domain of findlib, which knows exactly these things and does it when constructing preprocessor commands -- so that is what |
bd54380
to
eea639c
Compare
Thanks for pointing this. This is my first time updating Homebrew package, so I don't know why this particular test was written this way, but from the comment purpose it was made to check the binary compatibility with the OCaml compiler. I will try to change to that |
Ah, you're trying to check that the output of |
If the issue here is tests, you could use the extensive test-suite that comes with Camlp5. When I took over maintenance, the test-suite was pretty limited, but I've added a massive set of tests of all sorts of function. You can look at the |
7e94cf2
to
1245820
Compare
For now I use the old solution, since the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
99f7d98
to
8baf40a
Compare
Strange error while building Coq:
|
8baf40a
to
1e683eb
Compare
This looks similar to Homebrew/homebrew-test-bot#805 4f236f2, just different paths. |
1e683eb
to
f10e7ec
Compare
bd2a845
to
8802357
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test failures other than hyperkit
look unrelated.
@XVilka, thanks for your contribution to Homebrew! 🎉 🥇 Without awesome contributors like you, it would be impossible to maintain Homebrew to the high level of quality users have come to expect. Thank you!!!! |
sha256 cellar: :any_skip_relocation, ventura: "3b67078315551718bc3c752b943b933713ddb69058f3cb72a0f65faa6e9295ab" | ||
sha256 cellar: :any_skip_relocation, monterey: "da3b0d0374a85af5c649c86fb7796c1eecae468f5783bbb994a96d807e60712a" | ||
sha256 cellar: :any_skip_relocation, big_sur: "f96e7270e9e853ce33f2195136b11338a5cf4d612ee50f3dd51b5c8506b4efcb" | ||
sha256 cellar: :any_skip_relocation, catalina: "cd58afe172473278d3ed9404e9d25e10bee487fb4e27cd6de39c950a0ccaca87" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to followup on this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hyperkit really looks like abandonware now:
- https://github.com/moby/hyperkit/commits/master/
- https://github.com/moby/hyperkit/issues
- https://github.com/moby/hyperkit/pulls
Not much could probably be done for it, until developers/maintainers step in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologize for tagging you @djs55, but since you were hyperkit developer, you might be able to help reviving it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, there are no new commits for the past two years.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not so much abandonware, but stable. There's no need to keep it up-to-date with the very latest OCaml, and I doubt there are many users accessing it via Homebrew. I'm happy to it to be removed from Homebrew to ensure there's no blocker on upstream OCaml updates. Copying in @djs55 as another maintainer of Hyperkit to confirm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would describe it as stable -- it's still shipped in Docker Desktop for Intel Macs. Removing hyperkit from Homebrew is fine.
❌ @chenrui333 bottle request for hyperkit failed. |
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?