-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
+lwt.2.7.0, lwt_ssl.1.0.0, lwt_glib.1.0.0, lwt_react.1.0.0 #8196
Conversation
❌ opam-lint errors 7a71502
✅ Installability check (5949 → 5953)
|
Any chance you could also merge in the lwt 2.7.0 PR into this branch please? It'll unblock CI. |
Yes, I can do that. Do you mean after that PR is merged, or immediately? |
Immediately would be good, as then the additional packages can be tested. There is also a new set of CI tests that can test reverse dependencies that will run. |
09d2a50
to
587ff5d
Compare
I rebased over the Lwt base package branch, not including new upper bounds as waiting for the revdeps build to complete. Let me know what subsequent other squashes/rebases/merges/whatever you want, and also feel free to merge any way that is appropriate. |
587ff5d
to
cfdc9b3
Compare
Thank you for all the upper bounds! One missing in the CI is
All the others pass, yay! |
Anil, I did add an upper bound on
It is failing because of deprecation warnings unrelated to Lwt. |
Do you want me to constrain it anyway? I guess it requires OCaml < 4.03, but I can look in more detail. |
Also, since the CI is working out fine, I suppose we should rename this PR and abandon the other one. Reasonable? |
Constraining it to build would be great. |
Yep already looking to be sure of the constraint, will add a commit shortly. |
Ok, all releases of So I constrained them all to require < 4.03, except for release cc @andrenth |
@avsm are you ok to merge this one? It seems that the remaining errors were already there. |
Ideally we'd like to enable -warn-error for developer builds but disable -warn-error for tagged release builds. This patch disables -warn-error for both cases: it's not worth too much work on the current build and packaging system when we're likely to switch over to topkg soon. This allows vpnkit to build with lwt.2.7.0. Related to [ocaml/opam-repository#8195] Related to [ocaml/opam-repository#8196] Signed-off-by: David Scott <dave.scott@docker.com>
Good to go! Thanks for all the hard work with the release, @aantron! |
Ideally we would keep this as -warn-error for developer builds but disable for tagged release builds. This patch disables -warn-error for warning 3 for both cases: it's not worth too much work on the current build and packaging system when we're likely to switch over to topkg soon. This allows vpnkit to build with lwt.2.7.0. Related to [ocaml/opam-repository#8195] Related to [ocaml/opam-repository#8196] Signed-off-by: David Scott <dave.scott@docker.com>
Packages being factored out of Lwt, to be removed from the base
lwt
package in Lwt 3.0.0. See ocsigen/lwt#301.I submitted these in a separate PR because I suspect they won't build in CI (due to constraints) until Lwt 2.7.0 is accepted.
EDIT: #8195.