-
Notifications
You must be signed in to change notification settings - Fork 96
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
Bazel mirror of bazel-toolchains 3.2.0 broken link #891
Comments
Hi @leighmcculloch, Yes the mirror is still being maintained. We switched to using release archives instead of commit archives a while ago:
Looks like our release notes generator still generates the old links for the list of "previous releases". I'll look into having that fixed. |
yashykt
pushed a commit
to grpc/grpc
that referenced
this issue
Jun 14, 2022
See bazelbuild/bazel-toolchains#891 (comment) and #27410 (comment) Seems like the mirror for bazel toolchains changed the URL and they mirror downloads but not archives. This should fix any issues with missing mirror and workaround bazelbuild/bazel-toolchains#972 Signed-off-by: Vihang Mehta <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm seeing warnings building common projects that have the
bazel-toolchains
as a dependency because the following mirror.bazel.build URL is 404ing.https://mirror.bazel.build/github.com/bazelbuild/bazel-toolchains/archive/3.2.0.tar.gz
An example of one project whose bazel build process is displaying warnings about this is the @google Tink project:
https://github.com/google/tink/blob/23ce810c979b1105fe6a657a5667a7275764b411/tink_base_deps.bzl#L69-L79
This is the error I see:
According to the releases page the bazel-toolchains (link below) is supposed to be available at two URLs, one being the mirror, but it seems the mirror is missing version 3.2.0.
https://releases.bazel.build/bazel-toolchains.html
Is the mirror being maintained?
Should we continue to use the mirror as a dependency location?
The text was updated successfully, but these errors were encountered: