-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ppx_deriving.4.4, with 4.08 support #14454
Conversation
🌤️ opam-lint warnings 587c1be
☀️ Installability check (+1)
|
The revdeps look good (there are few 4.08-available dependencies to test, but some like |
Once OCaml 4.08 enabled there was a lot of revdeps failures. I fixed most of them but this one seems rather weird:
There are a few broken packages to deal with but let's leave it like that for today |
That's quite interesting, in principle it should not depend on |
@kit-ty-kate thanks! I think that the failure that you are seeing on nocrypto is a 4.08.0 compiler bug that we have fixed in the 4.08 branch upstream, ocaml/ocaml#8770 |
I studied more revdeps failures, and I didn't find anything very suspicious. (ppx_deriving_argparse is failing because of a hardcoded .cmxs path that changed when we moved to a Dune build, I can send a fix upstream and ask for a new release.) There are some unrelated failures and some plugins that really need a 4.08 upgrade. I will complete the release and rebase this PR to point to the definitive archive. Thanks again @kit-ty-kate for the work triaging the issues and marking 4.08 incompatibility in dependent packages. |
Ahem. I force-pushed to my github clone out of habit, and lost the extra commits that @kit-ty-kate had pushed. Apologies... @kit-ty-kate, can I find them in your own github fork? (I just looked but I don't see the branch.) |
(No worries, I just got the missing patches from github: https://github.com/ocaml/opam-repository/compare/6506d59227c0380f861d6a647558cecb87673f55..8be19ff9ffa3517d2d749d13a847e589536bdfcc.patch ) |
I had them locally. It was pushed on your branch directly. You might want to use |
ppx_deriving.4.3 installs each plugin in a separate subdirectory, which breaks the hardcoded paths in the build system of the "make test" rule of ppx_deriving_argparse.
49f96c0
to
fac68a7
Compare
oops sorry my bad, I thought there was a mistake |
Wow, I just pushed an updated version of the branch that should be final (CI can always tell otherwise). I restricted the package to (< 4.09), so that we avoid use-side build failures in the future. I restricted ppx_deriving_argparse to 4.3 instead of 4.4 (the failure is not new). |
Are you sure? check.ocamllabs.io tells me otherwise: http://check.ocamllabs.io/log/1562505242-7152ba482366e28003d2457509dd618295bc655d/4.07.1/good/ppx_deriving_argparse.0.0.4 (but that's not really important anyway) |
The failure is only in the |
|
thanks a lot! |
Ping to maintainers of packages of which latest version is not available with OCaml 4.08:
|
Well, someone (@kit-ty-kate or @gasche?) marked |
That's part of the maintenance operations that we (most of that work is done by @kit-ty-kate) perform when the build of a package breaks (the idea is to mark it incompatible as soon as possible to avoid end-users seeing build failures). You were just "told" by the cc above: -- done by @kit-ty-kate when the change to the Here is what I get if I try to build
|
4.02 nit in the tests ocaml-ppx/ppx_deriving#188
(ELLIOTTCABLE)
when using reason-language-server
Support empty Location.input_name in input ast ocaml-ppx/ppx_deriving#196
(Ryan Artecona)
4.08 support ocaml-ppx/ppx_deriving#193, Add
Result.result
to the .mli file ocaml-ppx/ppx_deriving#197, Result: ensure Result.t and Result.result are exposed under both 4.08 and earlier versions ocaml-ppx/ppx_deriving#200(Gabriel Scherer)