-
Notifications
You must be signed in to change notification settings - Fork 58
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
Has someone deleted the https://github.com/JuliaInterop/ZMQBuilder repo? #228
Comments
You no longer need the ZMQBuilder repo — it's now built through Yggdrasil, and you can install the binary in Julia via What are you trying to do? |
We have an application that is built on julia 0.6, that recently started failing to build in our CI env, that was pulling in ZMQ from that builder repo. It's looking like we will finally have to upgrade it. |
Sorry about that. If you build libzmq yourself, you could easily patch ZMQ.jl to link to whatever build of |
Generally better to use the github archive feature on out-of-date stuff, vs outright deleting it |
I think that was me. Sorry about that. We generally got rid of a bunch of these old Builder scripts when we moved to Yggdrasil several years ago. I don't see a way to restore the repo in my deleted repos. Any ideas how to restore it? Can one email github support? |
@ViralBShah I'm assuming you did, but did you try the step outlined here? https://docs.github.com/en/repositories/creating-and-managing-repositories/restoring-a-deleted-repository#restoring-a-deleted-repository-that-was-owned-by-an-organization |
Unfortunately it doesn't seem like there's anything we can do here, short of anyone having a recent clone of the repo to recreate it :\ I'll close this but keep the issue pinned so it's visible to anyone looking for it. |
I was at least able to pull a binary from the way back machine, which for now at least unblocked our build, and we can plan out an update, thanks. |
We are now getting when trying to build/install zmq.
The text was updated successfully, but these errors were encountered: