-
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
caml.inria.fr is not accessible anymore #13237
Comments
This may have to do with Inria's move?
Maybe somebody from Inria like @xavierleroy or @gasche can tell more?
|
Yep, the servers are moving, and as it says on the error page, "the websites are scheduled to go back online on June 19 or 20, 2024". I was hoping no one relies on caml.inria.fr any longer... |
if this is the case, i think it would be nice for the archives created by hand for each releases to be added to the GitHub release page (cc @Octachron), this way we have a set of immutable archives. I believe this is the only reason people still use caml.inria.fr PS: sorry @shindere i should've thought of adding an alt-text for the image, i'll try to remember for next time |
It is a good idea to add the archive to the GitHub release page anyway. |
Kate (2024/06/17 03:45 -0700):
> I was hoping no one relies on caml.inria.fr any longer...
if this is the case, i think it would be nice for the archives created
by hand for each releases to be added to the GitHub release page (cc
@Octachron), this way we have a set of immutable archives. I believe
this is the only reason people still use caml.inria.fr
And maybe we shold properly retire caml.inria.fr, possibly with
redirections to GitHub?
PS: sorry @shindere i should've thought of adding an alt-text for the
image, i'll try to remember for next time
Thanks, and no worries. It's also my fault as I have been lazy and did
not follow the linkyou mentionned to "see" by myself.
|
It looks like some package managers still have the caml.inria.fr server baked in; e.g. NixOS' nixpkgs: So uploading the caml.inria.fr archives with the same SHA256 hash to the corresponding GitHub release would be indeed a very useful way to make the fix for Nix is a one line change instead of updating all the checksums as well. |
caml.inra.fr is also embedded into the opam build process for 2.0 and 2.1, preventing us from building new Docker base images for the CI system. ocurrent/docker-base-images#283 As the Opam 2.0 needs a lot of effort to get it to pass CI, but 2.1 could easily be patched to remove the dependency on caml.inria.fr. OCaml-CI uses opam 2.1, Opam-repo-ci uses opam-dev. Does anyone still use opam 2.0? |
Further to my last comment, the patch to opam is more straightforward than I thought. It is the bootstrap compiler that is failing, so one patch on master will resolve the issue. See ocaml/opam#6032. |
Would it be possible for inria to redirect requests for these archives (and for opam) to the source on github for the duration of their outage? If so, is that lift light enough that we could expedite to address the immediate impact of these disruptions? |
I fear (1) it's not something we have control over and (2) can't happen
before the beginning of July. @Octachron maybe able to contact the
engineers in charge to see with them what they could do?
|
Note: caml.inria.fr is back online (probably has been since yesterday). |
Gabriel Scherer (2024/06/21 03:20 -0700):
Note: caml.inria.fr is back online (probably has been since
yesterday).
Okay thanks for this update!
In this context, I will close this issue (but anybody should feel free
to re-open it if deemed appropriate). I think we can open more specific
issues to change the URLs in the various places so that they do no
longer refer to caml.inria.fr, and likewise for uploading the releases
to GitHub.
|
I was trying to download the archive for OCaml 4.14.2 and got hit by a "Couldn't connect to server".
Going to the website in HTTPS indeed results in a timeout, and trying the HTTP version nets me this page instead:
The text was updated successfully, but these errors were encountered: