-
Notifications
You must be signed in to change notification settings - Fork 163
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
https://static.rust-lang.org/dist/index.html no longer works #215
Comments
We indeed no longer update that page (primarily due to budget/time of index costs); this has been the case for I think up to 4-6 release cycles now. What is the specific use case/requirement? In theory, all minor stable releases are at "well known" URLs (i.e., stable release dates are every 6 weeks). Beyond that, we don't currently have any good way of scanning all of the data. |
The use case is that sometimes I'm too slow in packaging the latest rustc for Debian so I need to download older versions. Unfortunately the |
Unfortunately not. FWIW, we do have http://static.rust-lang.org/dist/channel-rust-1.13.0.toml and so on for stable releases -- nightly release manifest are found in dist/YYYY-MM-DD/channel-rust-nightly.toml (e.g., https://static.rust-lang.org/dist/2019-04-05/channel-rust-nightly.toml). Maybe that's enough for your purposes? Presumably the nightly index wouldn't be too useful anyway since almost every date has one... |
@pietroalbini and I separately discovered that S3/AWS has a feature, S3 Inventory, that may be helpful to restore functionality here (perhaps fully, perhaps even more usefully). I think it's likely that if you wanted this to happen sooner rather than later we would be happy to integrate something into our release process. I've not personally investigated too much but a list of steps or something along those lines would help us move faster here I think. |
Pulls in the version of rustfmt that is shipped with Rust 1.39.0. Distribution path/version found in official release channel TOML. See http://static.rust-lang.org/dist/channel-rust-1.39.0.toml, and rust-lang/rust-forge#215 for more information on this. Relates to bazelbuild#87.
Pulls in the version of rustfmt that is shipped with Rust 1.39.0. Distribution path/version found in official release channel TOML. See http://static.rust-lang.org/dist/channel-rust-1.39.0.toml, and rust-lang/rust-forge#215 for more information on this. Relates to bazelbuild#87.
Pulls in the version of rustfmt that is shipped with Rust 1.39.0. Distribution path/version found in official release channel TOML. See http://static.rust-lang.org/dist/channel-rust-1.39.0.toml, and rust-lang/rust-forge#215 for more information on this. Relates to bazelbuild#87.
* Fetch and expose the rustfmt binary Pulls in the version of rustfmt that is shipped with Rust 1.39.0. Distribution path/version found in official release channel TOML. See http://static.rust-lang.org/dist/channel-rust-1.39.0.toml, and rust-lang/rust-forge#215 for more information on this. Relates to #87. * Set LC_ALL in fetch_shas.sh The order of `sort`'s output depends on this variable, and different users may have it set differently. * Add rustfmt hashes to known_shas rustfmt is versioned independently of the other Rust tools, which necessitates keeping track of its version separately. Binaries are also not provided for FreeBSD, and so a separate targets list is also used. * Expose rustfmt binary via the Rust toolchain * Add test that rustfmt binary works
@Mark-Simulacrum The toml file works for my use-case so we can close this. Hopefully no plans to drop it any time soon? |
No, the toml files are necessary for rustup and more broadly, so I would not expect us to drop them. I'll close this then. |
This prevents Debian infrastructure from automatically downloading old versions of the source code using our generic scraper tool
uscan
, used for archival and maintenance purposes.Is there an alternative?
The github releases page of "rustc" is not suitable since it only contains stuff from the top-level git repository and e.g. not vendor crates.
The text was updated successfully, but these errors were encountered: