keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
633f173484
rpm-ostree/rust/Cargo.lock

1027 lines
46 KiB
Plaintext
Raw Normal View History

rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "aho-corasick"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.6.10"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"memchr 2.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
[[package]]
name = "ansi_term"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "0.11.0"
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
dependencies = [
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
[[package]]
name = "arrayvec"
version = "0.4.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"nodrop 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "atty"
version = "0.2.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"termion 1.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "autocfg"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.1.2"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "backtrace"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.3.14"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"autocfg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"backtrace-sys 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cfg-if 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"rustc-demangle 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "backtrace-sys"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.1.28"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cc 1.0.30 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "bitflags"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "c_utf8"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"version_check 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "cc"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
version = "1.0.30"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "cfg-if"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
version = "0.1.7"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
[[package]]
name = "clap"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "2.32.0"
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"ansi_term 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
"atty 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
"bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"strsim 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
"textwrap 0.10.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
"unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"vec_map 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "clicolors-control"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "1.0.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"atty 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "console"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.7.5"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"atty 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"clicolors-control 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
"encode_unicode 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"parking_lot 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"regex 1.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"termios 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
[[package]]
name = "crossbeam-deque"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"crossbeam-epoch 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "crossbeam-epoch"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"arrayvec 0.4.10 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cfg-if 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
"crossbeam-utils 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
"memoffset 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"nodrop 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)",
"scopeguard 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "crossbeam-utils"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cfg-if 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "cstr-argument"
version = "0.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cfg-if 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"memchr 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "curl"
version = "0.4.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"curl-sys 0.4.16 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"openssl-probe 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"openssl-sys 0.9.42 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"schannel 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"socket2 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "curl-sys"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.4.16"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cc 1.0.30 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"libz-sys 1.0.25 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"openssl-sys 0.9.42 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
"vcpkg 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "dtoa"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
[[package]]
name = "either"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "1.5.1"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
name = "encode_unicode"
version = "0.3.5"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
name = "failure"
version = "0.1.5"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"backtrace 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
"failure_derive 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
name = "failure_derive"
version = "0.1.5"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"proc-macro2 0.4.27 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.11 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"syn 0.15.27 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"synstructure 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
name = "fuchsia-zircon"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"fuchsia-zircon-sys 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "fuchsia-zircon-sys"
version = "0.3.3"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "gio-sys"
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
version = "0.7.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
"glib-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
"gobject-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "glib"
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
version = "0.6.1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
"glib-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
"gobject-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "glib-sys"
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
version = "0.7.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "gobject-sys"
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
version = "0.7.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
"glib-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "indicatif"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "0.11.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"console 0.7.5 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"number_prefix 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"parking_lot 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"regex 1.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "itoa"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "lazy_static"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "1.3.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "libc"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
version = "0.2.50"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "libsystemd-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "libz-sys"
version = "1.0.25"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cc 1.0.30 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
"vcpkg 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "linked-hash-map"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "lock_api"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"owning_ref 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"scopeguard 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "log"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cfg-if 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "memchr"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "memchr"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "2.2.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
[[package]]
name = "memoffset"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "nodrop"
version = "0.1.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
[[package]]
name = "num-traits"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
[[package]]
name = "num_cpus"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "1.10.0"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
]
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
[[package]]
name = "number_prefix"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"num-traits 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "openat"
version = "0.1.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "openssl-probe"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "openssl-sys"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
version = "0.9.42"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cc 1.0.30 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"vcpkg 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "owning_ref"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"stable_deref_trait 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "parking_lot"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.7.1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"lock_api 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "parking_lot_core"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"smallvec 0.6.9 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "pkg-config"
version = "0.3.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "proc-macro2"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.4.27"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "quote"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.6.11"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"proc-macro2 0.4.27 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "rand"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
version = "0.6.1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
"fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"rand_chacha 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"rand_hc 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_isaac 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"rand_pcg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_xorshift 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rand_chacha"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.1.1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"autocfg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rand_core"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "rand_core"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.4.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "rand_hc"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "rand_isaac"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "rand_pcg"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.1.2"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"autocfg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "rand_xorshift"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.1.1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
[[package]]
name = "rayon"
version = "1.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"crossbeam-deque 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"either 1.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
"rayon-core 1.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rayon-core"
version = "1.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"crossbeam-deque 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"num_cpus 1.10.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "redox_syscall"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.1.51"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "redox_termios"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"redox_syscall 0.1.51 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "regex"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
version = "1.1.2"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"aho-corasick 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
"memchr 2.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"regex-syntax 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
"utf8-ranges 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "regex-syntax"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.6.5"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"ucd-util 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "remove_dir_all"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rpmostree-rust"
version = "0.1.0"
dependencies = [
"c_utf8 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"clap 2.32.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"curl 0.4.19 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
"gio-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
"glib 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)",
"glib-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"indicatif 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"openat 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"rand 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)",
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
"rayon 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"serde 1.0.89 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.89 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.39 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
"serde_yaml 0.8.8 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"systemd 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"tempfile 3.0.7 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "rustc-demangle"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.1.13"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"semver 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "ryu"
version = "0.2.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "schannel"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.1.15"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "scopeguard"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"semver-parser 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "serde"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "1.0.89"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "serde_derive"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "1.0.89"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"proc-macro2 0.4.27 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.11 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"syn 0.15.27 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "serde_json"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "1.0.39"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"itoa 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
"ryu 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"serde 1.0.89 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "serde_yaml"
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
version = "0.8.8"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"dtoa 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
"linked-hash-map 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"serde 1.0.89 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"yaml-rust 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "smallvec"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "0.6.9"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "socket2"
version = "0.3.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cfg-if 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"redox_syscall 0.1.51 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "stable_deref_trait"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
[[package]]
name = "strsim"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "0.7.0"
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "syn"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
version = "0.15.27"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"proc-macro2 0.4.27 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.11 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "synstructure"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"proc-macro2 0.4.27 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.11 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"syn 0.15.27 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "systemd"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"cstr-argument 0.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"libsystemd-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
"utf8-cstr 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "tempfile"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
version = "3.0.7"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"cfg-if 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"redox_syscall 0.1.51 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"remove_dir_all 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "termion"
version = "1.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"redox_syscall 0.1.51 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"redox_termios 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "termios"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
[[package]]
name = "textwrap"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
version = "0.10.0"
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "thread_local"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
[[package]]
name = "ucd-util"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "unicode-width"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "unicode-xid"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "utf8-cstr"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "utf8-ranges"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "vcpkg"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
[[package]]
name = "vec_map"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "version_check"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "winapi"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "winapi"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "winapi-build"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "yaml-rust"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
version = "0.4.3"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"linked-hash-map 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[metadata]
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum aho-corasick 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)" = "81ce3d38065e618af2d7b77e10c5ad9a069859b4be3c2250f674af3840d9c8a5"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum ansi_term 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
"checksum arrayvec 0.4.10 (registry+https://github.com/rust-lang/crates.io-index)" = "92c7fb76bc8826a8b33b4ee5bb07a247a81e76764ab4d55e8f73e3a4d8808c71"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum atty 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)" = "9a7d5b8723950951411ee34d271d99dddcc2035a16ab25310ea2c8cfd4369652"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum autocfg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "a6d640bee2da49f60a4068a7fae53acde8982514ab7bae8b8cea9e88cbcfd799"
"checksum backtrace 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)" = "cd5a90e2b463010cd0e0ce9a11d4a9d5d58d9f41d4a6ba3dcaf9e68b466e88b4"
"checksum backtrace-sys 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)" = "797c830ac25ccc92a7f8a7b9862bde440715531514594a6154e3d4a54dd769b6"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "228047a76f468627ca71776ecdebd732a3423081fcf5125585bcd7c49886ce12"
"checksum c_utf8 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "f747ed2575d426b7cbf0fcba5872db319a600d597391c339779a3d9835d1ea4d"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"checksum cc 1.0.30 (registry+https://github.com/rust-lang/crates.io-index)" = "d01c69d08ff207f231f07196e30f84c70f1c815b04f980f8b7b01ff01f05eb92"
"checksum cfg-if 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "11d43355396e872eefb45ce6342e4374ed7bc2b3a502d1b28e36d6e23c05d1f4"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum clap 2.32.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b957d88f4b6a63b9d70d5f454ac8011819c6efa7727858f458ab71c756ce2d3e"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum clicolors-control 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "73abfd4c73d003a674ce5d2933fca6ce6c42480ea84a5ffe0a2dc39ed56300f9"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum console 0.7.5 (registry+https://github.com/rust-lang/crates.io-index)" = "2bf3720d3f3fc30b721ef1ae54e13af3264af4af39dc476a8de56a6ee1e2184b"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
"checksum crossbeam-deque 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "f739f8c5363aca78cfb059edf753d8f0d36908c348f3d8d1503f03d8b75d9cf3"
"checksum crossbeam-epoch 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "927121f5407de9956180ff5e936fe3cf4324279280001cd56b669d28ee7e9150"
"checksum crossbeam-utils 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "2760899e32a1d58d5abb31129f8fae5de75220bc2176e77ff7c627ae45c918d9"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum cstr-argument 0.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "514570a4b719329df37f93448a70df2baac553020d0eb43a8dfa9c1f5ba7b658"
"checksum curl 0.4.19 (registry+https://github.com/rust-lang/crates.io-index)" = "c7c9d851c825e0c033979d4516c9173bc19a78a96eb4d6ae51d4045440eafa16"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum curl-sys 0.4.16 (registry+https://github.com/rust-lang/crates.io-index)" = "ca79238a79fb294be6173b4057c95b22a718c94c4e38475d5faa82b8383f3502"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum dtoa 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "6d301140eb411af13d3115f9a562c85cc6b541ade9dfa314132244aaee7489dd"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum either 1.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "c67353c641dc847124ea1902d69bd753dee9bb3beff9aa3662ecf86c971d1fac"
"checksum encode_unicode 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)" = "90b2c9496c001e8cb61827acdefad780795c42264c137744cae6f7d9e3450abd"
"checksum failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "795bd83d3abeb9220f257e597aa0080a508b27533824adf336529648f6abf7e2"
"checksum failure_derive 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "ea1063915fd7ef4309e222a5a07cf9c319fb9c7836b1f89b85458672dbb127e1"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"checksum fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
"checksum fuchsia-zircon-sys 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
"checksum gio-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "6975ada29f7924dc1c90b30ed3b32d777805a275556c05e420da4fbdc22eb250"
"checksum glib 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)" = "7a333edf5b9f1411c246ef14e7881b087255f04c56dbef48c64a0cb039b4b340"
"checksum glib-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3573351e846caed9f11207b275cd67bc07f0c2c94fb628e5d7c92ca056c7882d"
"checksum gobject-sys 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "08475e4a08f27e6e2287005950114735ed61cec2cb8c1187682a5aec8c69b715"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum indicatif 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)" = "2c60da1c9abea75996b70a931bba6c750730399005b61ccd853cee50ef3d0d0c"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum itoa 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "1306f3464951f30e30d12373d31c79fbd52d236e5e896fd92f96ec7babbbe60b"
"checksum kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "bc5729f27f159ddd61f4df6228e827e86643d4d3e7c32183cb30a1c08f604a14"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"checksum libc 0.2.50 (registry+https://github.com/rust-lang/crates.io-index)" = "aab692d7759f5cd8c859e169db98ae5b52c924add2af5fbbca11d12fefb567c1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum libsystemd-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "d7b98458cd04a5c3aacba6f1a3a3c4b9abcb0ae4d66a055eee502e0d52dc226b"
"checksum libz-sys 1.0.25 (registry+https://github.com/rust-lang/crates.io-index)" = "2eb5e43362e38e2bca2fd5f5134c4d4564a23a5c28e9b95411652021a8675ebe"
"checksum linked-hash-map 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "70fb39025bc7cdd76305867c4eccf2f2dcf6e9a57f5b21a93e1c2d86cd03ec9e"
"checksum lock_api 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "62ebf1391f6acad60e5c8b43706dde4582df75c06698ab44511d15016bc2442c"
"checksum log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c84ec4b527950aa83a329754b01dbe3f58361d1c5efacd1f6d68c494d08a17c6"
"checksum memchr 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "148fab2e51b4f1cfc66da2a7c32981d1d3c083a803978268bb11fe4b86925e7a"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum memchr 2.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "2efc7bc57c883d4a4d6e3246905283d8dae951bb3bd32f49d6ef297f546e1c39"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
"checksum memoffset 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "0f9dc261e2b62d7a622bf416ea3c5245cdd5d9a7fcc428c0d06804dfce1775b3"
"checksum nodrop 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)" = "2f9667ddcc6cc8a43afc9b7917599d7216aa09c463919ea32c59ed6cac8bc945"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum num-traits 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)" = "0b3a5d7cc97d6d30d8b9bc8fa19bf45349ffe46241e8816f50f62f6d6aaabee1"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum num_cpus 1.10.0 (registry+https://github.com/rust-lang/crates.io-index)" = "1a23f0ed30a54abaa0c7e83b1d2d87ada7c3c23078d1d87815af3e3b6385fbba"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum number_prefix 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "dbf9993e59c894e3c08aa1c2712914e9e6bf1fcbfc6bef283e2183df345a4fee"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum openat 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)" = "65154ad9f41c6a323e81fd19a9bb96c0aba2b84f99a063fa43ff1dc0cc84b48a"
"checksum openssl-probe 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "77af24da69f9d9341038eba93a073b1fdaaa1b788221b00a69bce9e762cb32de"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"checksum openssl-sys 0.9.42 (registry+https://github.com/rust-lang/crates.io-index)" = "cb534d752bf98cf363b473950659ac2546517f9c6be9723771614ab3f03bbc9e"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum owning_ref 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "49a4b8ea2179e6a2e27411d3bca09ca6dd630821cf6894c6c7c8467a8ee7ef13"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum parking_lot 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)" = "ab41b4aed082705d1056416ae4468b6ea99d52599ecf3169b00088d43113e337"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum parking_lot_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "94c8c7923936b28d546dfd14d4472eaf34c99b14e1c973a32b3e6d4eb04298c9"
"checksum pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)" = "676e8eb2b1b4c9043511a9b7bea0915320d7e502b0a079fb03f9635a5252b18c"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum proc-macro2 0.4.27 (registry+https://github.com/rust-lang/crates.io-index)" = "4d317f9caece796be1980837fd5cb3dfec5613ebdb04ad0956deea83ce168915"
"checksum quote 0.6.11 (registry+https://github.com/rust-lang/crates.io-index)" = "cdd8e04bd9c52e0342b406469d494fcb033be4bdbe5c606016defbb1681411e1"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"checksum rand 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)" = "ae9d223d52ae411a33cf7e54ec6034ec165df296ccd23533d671a28252b6f66a"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum rand_chacha 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "556d3a1ca6600bfcbab7c7c91ccb085ac7fbbcd70e008a98742e7847f4f7bcef"
"checksum rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
"checksum rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d0e7a549d590831370895ab7ba4ea0c1b6b011d106b5ff2da6eee112615e6dc0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum rand_hc 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7b40677c7be09ae76218dc623efbf7b18e34bced3f38883af07bb75630a21bc4"
"checksum rand_isaac 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "ded997c9d5f13925be2a6fd7e66bf1872597f759fd9dd93513dd7e92e5a5ee08"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum rand_pcg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "abf9b09b01790cfe0364f52bf32995ea3c39f4d2dd011eac241d2914146d0b44"
"checksum rand_xorshift 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "cbf7e9e623549b0e21f6e97cf8ecf247c1a8fd2e8a992ae265314300b2455d5c"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
"checksum rayon 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "373814f27745b2686b350dd261bfd24576a6fb0e2c5919b3a2b6005f820b0473"
"checksum rayon-core 1.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "b055d1e92aba6877574d8fe604a63c8b5df60f60e5982bf7ccbb1338ea527356"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum redox_syscall 0.1.51 (registry+https://github.com/rust-lang/crates.io-index)" = "423e376fffca3dfa06c9e9790a9ccd282fafb3cc6e6397d01dbf64f9bacc6b85"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum redox_termios 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "7e891cfe48e9100a70a3b6eb652fef28920c117d366339687bd5576160db0f76"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"checksum regex 1.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "53ee8cfdddb2e0291adfb9f13d31d3bbe0a03c9a402c01b1e24188d86c35b24f"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum regex-syntax 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)" = "8c2f35eedad5295fdf00a63d7d4b238135723f92b434ec06774dad15c7ab0861"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum remove_dir_all 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "3488ba1b9a2084d38645c4c08276a1752dcbf2c7130d74f1569681ad5d2799c5"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum rustc-demangle 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)" = "adacaae16d02b6ec37fdc7acfcddf365978de76d1983d3ee22afc260e1ca9619"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
"checksum ryu 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)" = "eb9e9b8cde282a9fe6a42dd4681319bfb63f121b8a8ee9439c6f4107e58a46f7"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum schannel 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)" = "f2f6abf258d99c3c1c5c2131d99d064e94b7b3dd5f416483057f308fea253339"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum scopeguard 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "94258f53601af11e6a49f722422f6e3425c52b06245a5cf9bc09908b174f5e27"
"checksum semver 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
"checksum semver-parser 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum serde 1.0.89 (registry+https://github.com/rust-lang/crates.io-index)" = "92514fb95f900c9b5126e32d020f5c6d40564c27a5ea6d1d7d9f157a96623560"
"checksum serde_derive 1.0.89 (registry+https://github.com/rust-lang/crates.io-index)" = "bb6eabf4b5914e88e24eea240bb7c9f9a2cbc1bbbe8d961d381975ec3c6b806c"
"checksum serde_json 1.0.39 (registry+https://github.com/rust-lang/crates.io-index)" = "5a23aa71d4a4d43fdbfaac00eff68ba8a06a51759a89ac3304323e800c4dd40d"
rust: Bump dependencies This leaves only indicatif outdated (see link in diff). Closes: #1720 Approved by: cgwalters
2018-12-19 23:33:17 +03:00
"checksum serde_yaml 0.8.8 (registry+https://github.com/rust-lang/crates.io-index)" = "0887a8e097a69559b56aa2526bf7aff7c3048cf627dff781f0b56a6001534593"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum smallvec 0.6.9 (registry+https://github.com/rust-lang/crates.io-index)" = "c4488ae950c49d403731982257768f48fada354a5203fe81f9bb6f43ca9002be"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum socket2 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)" = "c4d11a52082057d87cb5caa31ad812f4504b97ab44732cd8359df2e9ff9f48e7"
"checksum stable_deref_trait 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "dba1a27d3efae4351c8051072d619e3ade2820635c3958d826bfea39d59b54c8"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum strsim 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "bb4f380125926a99e52bc279241539c018323fab05ad6368b56f93d9369ff550"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"checksum syn 0.15.27 (registry+https://github.com/rust-lang/crates.io-index)" = "525bd55255f03c816e5d7f615587bd13030c7103354fadb104993dcee6a788ec"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum synstructure 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)" = "73687139bf99285483c96ac0add482c3776528beac1d97d444f6e91f203a2015"
"checksum systemd 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "daf2fd2d346d2dfb5fdc5f47b355f60dcfc35f5ee3e89e64e7ae2849ec8792a5"
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
"checksum tempfile 3.0.7 (registry+https://github.com/rust-lang/crates.io-index)" = "b86c784c88d98c801132806dadd3819ed29d8600836c4088e855cdf3e178ed8a"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum termion 1.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "689a3bdfaab439fd92bc87df5c4c78417d3cbe537487274e9b0b2dce76e92096"
"checksum termios 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "72b620c5ea021d75a735c943269bb07d30c9b77d6ac6b236bc8b5c496ef05625"
rust: Bump dependencies Notably, the latest indicatif compiles fine again. This is now the latest of everything, except the glib stack: ``` $ cargo outdated -R Name Project Compat Latest Kind Platform ---- ------- ------ ------ ---- -------- gio-sys 0.7.0 --- 0.8.0 Normal --- glib 0.6.1 --- 0.7.1 Normal --- glib-sys 0.7.0 --- 0.8.0 Normal --- ``` because it requires a newer rustc than we're currently locked at. Closes: #1770 Approved by: cgwalters
2019-03-01 18:19:01 +03:00
"checksum textwrap 0.10.0 (registry+https://github.com/rust-lang/crates.io-index)" = "307686869c93e71f94da64286f9a9524c0f308a9e1c87a583de8e9c9039ad3f6"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c6b53e329000edc2b34dbe8545fd20e55a333362d0a321909685a19bd28c3f1b"
"checksum ucd-util 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "535c204ee4d8434478593480b8f86ab45ec9aae0e83c568ca81abf0fd0e88f86"
"checksum unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "882386231c45df4700b275c7ff55b6f3698780a650026380e72dabe76fa46526"
"checksum unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fc72304796d0818e357ead4e000d19c9c174ab23dc11093ac919054d20a6a7fc"
"checksum utf8-cstr 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "55bcbb425141152b10d5693095950b51c3745d019363fc2929ffd8f61449b628"
"checksum utf8-ranges 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "796f7e48bef87609f7ade7e06495a87d5cd06c7866e6a5cbfceffc558a243737"
"checksum vcpkg 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)" = "def296d3eb3b12371b2c7d0e83bfe1403e4db2d7a0bba324a12b21c4ee13143d"
rust: Add clap A few of my outstanding Rust PRs use this (multiprocess, sysusers). Let's add it now. Closes: #1764 Approved by: jlebon
2019-02-25 03:59:42 +03:00
"checksum vec_map 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)" = "05c78687fb1a80548ae3250346c3db86a80a7cdd77bda190189f2d0a0987c81a"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
"checksum version_check 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "914b1a6776c4c929a602fafd8bc742e06365d4bcbe48c30f9cca5824f70dc9dd"
"checksum winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
"checksum winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "92c1eb33641e276cfa214a0522acad57be5c56b10cb348b3c5117db75f3ac4b0"
"checksum winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
"checksum winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
"checksum winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
rust: Freeze rand crate to v0.6.1 The recent dep bump caused rand to jump to v0.6.5, which pulled in `fuchsia-cprng`. Sadly, the cargo version we're frozen on chokes on it because its manifest makes use of the `edition` keyword, which wasn't stabilized yet. Let's just freeze the problematic crate for now. We should be able to bump our Rust toolchain soon-ish. (Note this commit also does some other minor crate bumps as a result of regenerating the lockfile to prune away `fuchsia-cprng`.) Closes: #1777 Closes: #1778 Approved by: cgwalters
2019-03-07 23:24:10 +03:00
"checksum yaml-rust 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "65923dd1784f44da1d2c3dbbc5e822045628c590ba72123e1c73d3c230c4434d"
Reference in New Issue Copy Permalink