https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.60.0 2021-12-15T14:16:26+00:00 2021-12-15T14:16:26+00:00 Laurențiu Nicola lnicola@dend.ro 2021-12-15T14:16:26+00:00 urn:sha1:0ec734af321a7a011e515a1b3bed56e2119d5817 2021-11-02T08:44:14+00:00 Laurențiu Nicola lnicola@dend.ro 2021-11-02T08:44:14+00:00 urn:sha1:ee3b46689b64f5428b95769cd6d770ff9821690a 2021-09-08T07:41:22+00:00 David Carlier devnexen@gmail.com 2021-09-05T21:25:37+00:00 urn:sha1:ec4a9da8681707483112d9eeab5f521d275b7483 adding libproctsta, for the upcoming libc update. 2020-11-06T11:33:12+00:00 Daiki Ihara sasurau4@gmail.com 2020-11-02T12:17:52+00:00 urn:sha1:a1af001a551f382a1962276640e4455b40f7936b 2020-08-09T17:38:52+00:00 Josh Stone jistone@redhat.com 2020-08-05T22:58:35+00:00 urn:sha1:29f5e5c574cebb5960491ba70d07be0c07548132 FreeBSD 10 reached its end-of-life in October 2018, and that toolchain caused issues in the LLVM 11 upgrade (#73526) that are resolved with the toolchain from FreeBSD 11. 2019-11-12T10:06:11+00:00 Pietro Albini pietro@pietroalbini.org 2019-11-04T16:40:18+00:00 urn:sha1:14da85c68e6b5cd8a64a1f2f5ba5cd50c725e38b 2019-08-12T08:31:35+00:00 Pietro Albini pietro@pietroalbini.org 2019-08-12T07:41:06+00:00 urn:sha1:eb832b2a3244166c81d8e00d94805525f3bd7526 Currently mirrors are stored in the rust-lang-ci2 S3 bucket along with CI toolchains. This is problematic for multiple reasons: - CI IAM credentials are allowed to both edit and delete those files. A malicious user gaining access to those credentials would be able to change our mirrored dependencies, possibly backdooring the compiler. - Contents of the rust-lang-ci2 bucket are disposable except for the mirrors' content. When we implement backups for S3 buckets we'd have to replicate just that part of the bucket, complicating the backup logic and increasing the chance of mistakes. A standalone bucket will be way easier to backup. This commit switches our CI to use the new rust-lang-ci-mirrors bucket. 2019-05-29T14:03:50+00:00 Alex Crichton alex@alexcrichton.com 2019-05-28T20:20:43+00:00 urn:sha1:3eda151086c3fe5ad49c7c3f5e68e9bf9b938de8 Ensure that they're all forwards-compatible with AWS updates happening next year by ensuring the bucket name shows up in the domain name. Closes #61168 2019-04-04T18:40:21+00:00 Alex Crichton alex@alexcrichton.com 2019-04-04T18:40:21+00:00 urn:sha1:fcc8b8cef2090389b82e96b1d4f32f70c1195206 These appear to have disappeared from the original server, so I acquired the contents from a different mirror and uploaded them to our S3 bucket 2018-12-26T04:08:33+00:00 Mark Rousskov mark.simulacrum@gmail.com 2018-12-25T15:56:47+00:00 urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718c