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

1014 lines
46 KiB
Plaintext
Raw Normal View History

rust: Add nix as a dependency I have multiple outstanding PRs that use it and they conflict on this, so let's just upstream it now. It helps avoid some use of `unsafe` talking to libc directly.
2019-08-30 16:17:40 +03:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
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 = [
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"winapi 0.3.8 (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
]
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]]
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
name = "atty"
version = "0.2.14"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"hermit-abi 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.8 (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]]
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
name = "autocfg"
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"
[[package]]
name = "autocfg"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +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"
[[package]]
name = "backtrace"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.3.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"backtrace-sys 0.1.32 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"rustc-demangle 0.1.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
]
[[package]]
name = "backtrace-sys"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.1.32"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"cc 1.0.50 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.66 (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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.2.1"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "c2-chacha"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.2.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"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"ppv-lite86 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +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 = "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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.0.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 = "cfg-if"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.1.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"
rust/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +03:00
[[package]]
name = "chrono"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.4.10"
rust/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"num-integer 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.104 (registry+https://github.com/rust-lang/crates.io-index)",
rust/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +03:00
"time 0.1.42 (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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"atty 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)",
"bitflags 1.2.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
"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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"unicode-width 0.1.7 (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
"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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "1.0.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"atty 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"winapi 0.3.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
]
[[package]]
name = "console"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.9.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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"clicolors-control 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"encode_unicode 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"regex 1.3.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
"termios 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"unicode-width 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"winapi 0.3.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
]
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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.7.2"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"crossbeam-epoch 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.7.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
]
[[package]]
name = "crossbeam-epoch"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.8.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"autocfg 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"crossbeam-utils 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"memoffset 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"scopeguard 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "crossbeam-queue"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.2.1"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.7.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
]
[[package]]
name = "crossbeam-utils"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.7.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"autocfg 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.4.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
]
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.4.25"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"curl-sys 0.4.25 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.66 (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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"openssl-sys 0.9.53 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"schannel 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)",
"socket2 0.3.11 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
[[package]]
name = "curl-sys"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.4.25"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"cc 1.0.50 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.66 (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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"openssl-sys 0.9.53 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
"vcpkg 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"winapi 0.3.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
]
[[package]]
name = "dtoa"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.4.4"
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 = "either"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "1.5.3"
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"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.3.6"
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"
treefile: allow ${releasever} in more keys Besides allowing ${releasever}, only do the substitution as the final pass after merging the treefiles for all the keys (currently ${basearch} and ${releasever}) instead of doing it per parse. This way we have the expected semantics where one could do: ``` include: "fedora-coreos.yaml" releasever: "42" ``` and have that releasever used. Fixes #1809 Signed-off-by: Rafael Fonseca <r4f4rfs@gmail.com> Closes: #1848 Approved by: cgwalters
2019-06-04 12:09:35 +03:00
[[package]]
name = "envsubst"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"failure 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
treefile: allow ${releasever} in more keys Besides allowing ${releasever}, only do the substitution as the final pass after merging the treefiles for all the keys (currently ${basearch} and ${releasever}) instead of doing it per parse. This way we have the expected semantics where one could do: ``` include: "fedora-coreos.yaml" releasever: "42" ``` and have that releasever used. Fixes #1809 Signed-off-by: Rafael Fonseca <r4f4rfs@gmail.com> Closes: #1848 Approved by: cgwalters
2019-06-04 12:09:35 +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]]
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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.1.6"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"backtrace 0.3.42 (registry+https://github.com/rust-lang/crates.io-index)",
"failure_derive 0.1.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]]
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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.1.6"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"proc-macro2 1.0.8 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 1.0.14 (registry+https://github.com/rust-lang/crates.io-index)",
"synstructure 0.12.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]]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "getrandom"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.1.14"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"wasi 0.9.0+wasi-snapshot-preview1 (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
]
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 = "gio-sys"
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
version = "0.8.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 Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
"glib-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"gobject-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.17 (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"
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +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 = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
"glib-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"gobject-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (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 Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
version = "0.8.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.17 (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 = "gobject-sys"
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
version = "0.8.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 Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
"glib-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.17 (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 hidden `coreos-rootfs seal` command All this does is put the immutable bit on the target directory. The intention is to replace this bit to start: https://github.com/coreos/coreos-assembler/blob/8b205bfbb971707382ace76bbb39e46ed3fc560d/src/create_disk.sh#L229 However, the real goal here is to add code in this file to handle redeploying the rootfs for Fedora CoreOS which combines OSTree+Ignition: https://github.com/coreos/fedora-coreos-tracker/issues/94 Basically doing this in proper Rust is going to be a lot nicer than shell script in dracut modules. Among other details, coreutils `mv` doesn't seem to do the right thing for SELinux labels when policy isn't loaded.
2019-09-25 14:52:44 +03:00
[[package]]
name = "heck"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"unicode-segmentation 1.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "hermit-abi"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
Add hidden `coreos-rootfs seal` command All this does is put the immutable bit on the target directory. The intention is to replace this bit to start: https://github.com/coreos/coreos-assembler/blob/8b205bfbb971707382ace76bbb39e46ed3fc560d/src/create_disk.sh#L229 However, the real goal here is to add code in this file to handle redeploying the rootfs for Fedora CoreOS which combines OSTree+Ignition: https://github.com/coreos/fedora-coreos-tracker/issues/94 Basically doing this in proper Rust is going to be a lot nicer than shell script in dracut modules. Among other details, coreutils `mv` doesn't seem to do the right thing for SELinux labels when policy isn't loaded.
2019-09-25 14:52:44 +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 = "indicatif"
build(deps): bump indicatif from 0.11.0 to 0.13.0 in /rust Bumps [indicatif](https://github.com/mitsuhiko/indicatif) from 0.11.0 to 0.13.0. - [Release notes](https://github.com/mitsuhiko/indicatif/releases) - [Commits](https://github.com/mitsuhiko/indicatif/compare/0.11.0...0.13.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-28 22:28:34 +03:00
version = "0.13.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"console 0.9.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump indicatif from 0.11.0 to 0.13.0 in /rust Bumps [indicatif](https://github.com/mitsuhiko/indicatif) from 0.11.0 to 0.13.0. - [Release notes](https://github.com/mitsuhiko/indicatif/releases) - [Commits](https://github.com/mitsuhiko/indicatif/compare/0.11.0...0.13.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-28 22:28:34 +03:00
"number_prefix 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"regex 1.3.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 = "itoa"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.4.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]]
name = "lazy_static"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "1.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 = "libc"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.2.66"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.17 (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 = "libz-sys"
version = "1.0.25"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"cc 1.0.50 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
"vcpkg 0.2.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
]
[[package]]
name = "linked-hash-map"
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
version = "0.5.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 = "log"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.4.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 = [
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (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 = "memoffset"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.5.3"
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
dependencies = [
"rustc_version 0.2.3 (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 nix as a dependency I have multiple outstanding PRs that use it and they conflict on this, so let's just upstream it now. It helps avoid some use of `unsafe` talking to libc directly.
2019-08-30 16:17:40 +03:00
[[package]]
name = "nix"
version = "0.15.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"cc 1.0.50 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add nix as a dependency I have multiple outstanding PRs that use it and they conflict on this, so let's just upstream it now. It helps avoid some use of `unsafe` talking to libc directly.
2019-08-30 16:17:40 +03:00
"void 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +03:00
[[package]]
name = "num-integer"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.1.42"
rust/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"autocfg 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
rust/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +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 = "num-traits"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.2.11"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"autocfg 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +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
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.12.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"hermit-abi 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.66 (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"
build(deps): bump indicatif from 0.11.0 to 0.13.0 in /rust Bumps [indicatif](https://github.com/mitsuhiko/indicatif) from 0.11.0 to 0.13.0. - [Release notes](https://github.com/mitsuhiko/indicatif/releases) - [Commits](https://github.com/mitsuhiko/indicatif/compare/0.11.0...0.13.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-28 22:28:34 +03:00
version = "0.3.0"
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
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 = "openat"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.1.18"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (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
]
Move openat_utils to its own crate I wanted to use this in another project, and I don't think we're the only ones. I extracted the code, added better docs and tests, and published to crates.io: https://crates.io/crates/openat-ext
2019-08-21 04:42:49 +03:00
[[package]]
name = "openat-ext"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.1.2"
Move openat_utils to its own crate I wanted to use this in another project, and I don't think we're the only ones. I extracted the code, added better docs and tests, and published to crates.io: https://crates.io/crates/openat-ext
2019-08-21 04:42:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"openat 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
Move openat_utils to its own crate I wanted to use this in another project, and I don't think we're the only ones. I extracted the code, added better docs and tests, and published to crates.io: https://crates.io/crates/openat-ext
2019-08-21 04:42:49 +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 = "openssl-probe"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "openssl-sys"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.9.53"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"autocfg 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
"cc 1.0.50 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
"vcpkg 0.2.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
]
[[package]]
name = "pkg-config"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.3.17"
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "ppv-lite86"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.2.6"
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "proc-macro2"
version = "0.4.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"
dependencies = [
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"unicode-xid 0.1.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]]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "proc-macro2"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.0.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 = [
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"unicode-xid 0.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
]
[[package]]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "quote"
version = "0.6.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"
dependencies = [
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"proc-macro2 0.4.30 (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
]
[[package]]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "quote"
version = "1.0.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"proc-macro2 1.0.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
]
[[package]]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "rand"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.7.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 = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"getrandom 0.1.14 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"rand_chacha 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_hc 0.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
]
[[package]]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "rand_chacha"
version = "0.2.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"c2-chacha 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"rand_core 0.5.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
]
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "rand_core"
version = "0.5.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"getrandom 0.1.14 (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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "rand_hc"
version = "0.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"
dependencies = [
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"rand_core 0.5.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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.3.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"crossbeam-deque 0.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"either 1.5.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"rayon-core 1.7.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
]
[[package]]
name = "rayon-core"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.7.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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"crossbeam-deque 0.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-queue 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"num_cpus 1.12.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
]
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.1.56"
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 = "regex"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.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"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"regex-syntax 0.6.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 = "regex-syntax"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.6.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 = "remove_dir_all"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.5.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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"winapi 0.3.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
]
[[package]]
name = "rpmostree-rust"
version = "0.1.0"
dependencies = [
"c_utf8 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"chrono 0.4.10 (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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"curl 0.4.25 (registry+https://github.com/rust-lang/crates.io-index)",
treefile: allow ${releasever} in more keys Besides allowing ${releasever}, only do the substitution as the final pass after merging the treefiles for all the keys (currently ${basearch} and ${releasever}) instead of doing it per parse. This way we have the expected semantics where one could do: ``` include: "fedora-coreos.yaml" releasever: "42" ``` and have that releasever used. Fixes #1809 Signed-off-by: Rafael Fonseca <r4f4rfs@gmail.com> Closes: #1848 Approved by: cgwalters
2019-06-04 12:09:35 +03:00
"envsubst 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"failure 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
"gio-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"glib 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
"glib-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump indicatif from 0.11.0 to 0.13.0 in /rust Bumps [indicatif](https://github.com/mitsuhiko/indicatif) from 0.11.0 to 0.13.0. - [Release notes](https://github.com/mitsuhiko/indicatif/releases) - [Commits](https://github.com/mitsuhiko/indicatif/compare/0.11.0...0.13.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-28 22:28:34 +03:00
"indicatif 0.13.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Add nix as a dependency I have multiple outstanding PRs that use it and they conflict on this, so let's just upstream it now. It helps avoid some use of `unsafe` talking to libc directly.
2019-08-30 16:17:40 +03:00
"nix 0.15.0 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"openat 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
"openat-ext 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"rayon 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.104 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.104 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.45 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_yaml 0.8.11 (registry+https://github.com/rust-lang/crates.io-index)",
Add hidden `coreos-rootfs seal` command All this does is put the immutable bit on the target directory. The intention is to replace this bit to start: https://github.com/coreos/coreos-assembler/blob/8b205bfbb971707382ace76bbb39e46ed3fc560d/src/create_disk.sh#L229 However, the real goal here is to add code in this file to handle redeploying the rootfs for Fedora CoreOS which combines OSTree+Ignition: https://github.com/coreos/fedora-coreos-tracker/issues/94 Basically doing this in proper Rust is going to be a lot nicer than shell script in dracut modules. Among other details, coreutils `mv` doesn't seem to do the right thing for SELinux labels when policy isn't loaded.
2019-09-25 14:52:44 +03:00
"structopt 0.2.18 (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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"tempfile 3.1.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 = "rustc-demangle"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.1.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"
[[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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.0.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 = "schannel"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.1.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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
[[package]]
name = "scopeguard"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +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"
[[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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.0.104"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.0.104"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"proc-macro2 1.0.8 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"syn 1.0.14 (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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.0.45"
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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"itoa 0.4.5 (registry+https://github.com/rust-lang/crates.io-index)",
"ryu 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.104 (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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.8.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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"dtoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
"linked-hash-map 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"serde 1.0.104 (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 = "socket2"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.3.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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
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"
Add hidden `coreos-rootfs seal` command All this does is put the immutable bit on the target directory. The intention is to replace this bit to start: https://github.com/coreos/coreos-assembler/blob/8b205bfbb971707382ace76bbb39e46ed3fc560d/src/create_disk.sh#L229 However, the real goal here is to add code in this file to handle redeploying the rootfs for Fedora CoreOS which combines OSTree+Ignition: https://github.com/coreos/fedora-coreos-tracker/issues/94 Basically doing this in proper Rust is going to be a lot nicer than shell script in dracut modules. Among other details, coreutils `mv` doesn't seem to do the right thing for SELinux labels when policy isn't loaded.
2019-09-25 14:52:44 +03:00
[[package]]
name = "structopt"
version = "0.2.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"clap 2.32.0 (registry+https://github.com/rust-lang/crates.io-index)",
"structopt-derive 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "structopt-derive"
version = "0.2.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"heck 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.15.44 (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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.15.44"
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.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
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
[[package]]
name = "syn"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.0.14"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"proc-macro2 1.0.8 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-xid 0.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
[[package]]
name = "synstructure"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.12.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 = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"proc-macro2 1.0.8 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 1.0.14 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-xid 0.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
]
[[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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (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)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"log 0.4.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
"utf8-cstr 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "tempfile"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "3.1.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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.7.3 (registry+https://github.com/rust-lang/crates.io-index)",
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
"remove_dir_all 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
[[package]]
name = "termios"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (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 = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"unicode-width 0.1.7 (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
]
rust/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +03:00
[[package]]
name = "time"
version = "0.1.42"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
rust/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +03:00
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
Add hidden `coreos-rootfs seal` command All this does is put the immutable bit on the target directory. The intention is to replace this bit to start: https://github.com/coreos/coreos-assembler/blob/8b205bfbb971707382ace76bbb39e46ed3fc560d/src/create_disk.sh#L229 However, the real goal here is to add code in this file to handle redeploying the rootfs for Fedora CoreOS which combines OSTree+Ignition: https://github.com/coreos/fedora-coreos-tracker/issues/94 Basically doing this in proper Rust is going to be a lot nicer than shell script in dracut modules. Among other details, coreutils `mv` doesn't seem to do the right thing for SELinux labels when policy isn't loaded.
2019-09-25 14:52:44 +03:00
[[package]]
name = "unicode-segmentation"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "1.6.0"
Add hidden `coreos-rootfs seal` command All this does is put the immutable bit on the target directory. The intention is to replace this bit to start: https://github.com/coreos/coreos-assembler/blob/8b205bfbb971707382ace76bbb39e46ed3fc560d/src/create_disk.sh#L229 However, the real goal here is to add code in this file to handle redeploying the rootfs for Fedora CoreOS which combines OSTree+Ignition: https://github.com/coreos/fedora-coreos-tracker/issues/94 Basically doing this in proper Rust is going to be a lot nicer than shell script in dracut modules. Among other details, coreutils `mv` doesn't seem to do the right thing for SELinux labels when policy isn't loaded.
2019-09-25 14:52:44 +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 = "unicode-width"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +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"
[[package]]
name = "unicode-xid"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "unicode-xid"
version = "0.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"
[[package]]
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "utf8-cstr"
version = "0.1.6"
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 = "vcpkg"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.2.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"
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"
rust: Add nix as a dependency I have multiple outstanding PRs that use it and they conflict on this, so let's just upstream it now. It helps avoid some use of `unsafe` talking to libc directly.
2019-08-30 16:17:40 +03:00
[[package]]
name = "void"
version = "1.0.2"
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
name = "wasi"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
version = "0.9.0+wasi-snapshot-preview1"
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 = "winapi"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
version = "0.3.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 = [
"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-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 = [
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
"linked-hash-map 0.5.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
]
[metadata]
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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum atty 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)" = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
"checksum autocfg 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "1d49d90015b3c36167a20fe2810c5cd875ad504b39cff3d4eae7977e6b7c1cb2"
"checksum autocfg 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "f8aac770f1885fd7e387acedd76065302551364496e46b3dd00860b2f8359b9d"
"checksum backtrace 0.3.42 (registry+https://github.com/rust-lang/crates.io-index)" = "b4b1549d804b6c73f4817df2ba073709e96e426f12987127c48e6745568c350b"
"checksum backtrace-sys 0.1.32 (registry+https://github.com/rust-lang/crates.io-index)" = "5d6575f128516de27e3ce99689419835fce9643a9b215a14d2b5b685be018491"
"checksum bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
"checksum c2-chacha 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "214238caa1bf3a496ec3392968969cab8549f96ff30652c9e56885329315f6bb"
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 c_utf8 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "f747ed2575d426b7cbf0fcba5872db319a600d597391c339779a3d9835d1ea4d"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum cc 1.0.50 (registry+https://github.com/rust-lang/crates.io-index)" = "95e28fa049fda1c330bcf9d723be7663a899c4679724b34c81e9f5a326aab8cd"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)" = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum chrono 0.4.10 (registry+https://github.com/rust-lang/crates.io-index)" = "31850b4a4d6bae316f7a09e691c944c28299298837edc0a03f755618c23cbc01"
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: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum clicolors-control 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "90082ee5dcdd64dc4e9e0d37fbf3ee325419e39c0092191e0393df65518f741e"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum console 0.9.1 (registry+https://github.com/rust-lang/crates.io-index)" = "f5d540c2d34ac9dd0deb5f3b5f54c36c79efa78f6b3ad19106a554d07a7b5d9f"
"checksum crossbeam-deque 0.7.2 (registry+https://github.com/rust-lang/crates.io-index)" = "c3aa945d63861bfe624b55d153a39684da1e8c0bc8fba932f7ee3a3c16cea3ca"
"checksum crossbeam-epoch 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "5064ebdbf05ce3cb95e45c8b086f72263f4166b29b97f6baff7ef7fe047b55ac"
"checksum crossbeam-queue 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "c695eeca1e7173472a32221542ae469b3e9aac3a4fc81f7696bcad82029493db"
"checksum crossbeam-utils 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ce446db02cdc3165b94ae73111e570793400d0794e46125cc4056c81cbb039f4"
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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum curl 0.4.25 (registry+https://github.com/rust-lang/crates.io-index)" = "06aa71e9208a54def20792d877bc663d6aae0732b9852e612c4a933177c31283"
"checksum curl-sys 0.4.25 (registry+https://github.com/rust-lang/crates.io-index)" = "0c38ca47d60b86d0cc9d42caa90a0885669c2abc9791f871c81f58cdf39e979b"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum dtoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)" = "ea57b42383d091c85abcc2706240b94ab2a8fa1fc81c10ff23c4de06e2a90b5e"
"checksum either 1.5.3 (registry+https://github.com/rust-lang/crates.io-index)" = "bb1f6b1ce1c140482ea30ddd3335fc0024ac7ee112895426e0a629a6c20adfe3"
"checksum encode_unicode 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "a357d28ed41a50f9c765dbfe56cbc04a64e53e5fc58ba79fbc34c10ef3df831f"
treefile: allow ${releasever} in more keys Besides allowing ${releasever}, only do the substitution as the final pass after merging the treefiles for all the keys (currently ${basearch} and ${releasever}) instead of doing it per parse. This way we have the expected semantics where one could do: ``` include: "fedora-coreos.yaml" releasever: "42" ``` and have that releasever used. Fixes #1809 Signed-off-by: Rafael Fonseca <r4f4rfs@gmail.com> Closes: #1848 Approved by: cgwalters
2019-06-04 12:09:35 +03:00
"checksum envsubst 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "13cf19a8d534c83456ea13365a1935810a39f0e43bf1ec9371077e1966da396a"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum failure 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "f8273f13c977665c5db7eb2b99ae520952fe5ac831ae4cd09d80c4c7042b5ed9"
"checksum failure_derive 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "0bc225b78e0391e4b8683440bf2e63c2deeeb2ce5189eab46e2b68c6d3725d08"
"checksum getrandom 0.1.14 (registry+https://github.com/rust-lang/crates.io-index)" = "7abc8dd8451921606d809ba32e95b6111925cd2906060d2dcc29c070220503eb"
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
"checksum gio-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "04957c40df00dd72f7c9ec8e382b01ff8ed4a904fcd2fa608b7ae7fbaccfda8f"
"checksum glib 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)" = "0c4e8fdc159c196a5dfa53a92929ac4c10c8a6637ffb43951f3fff89c2cd2365"
"checksum glib-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "5bda542f3caee39a027638e9644ff89204101ad916fd7370b585ad2c5fc97e61"
"checksum gobject-sys 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "23e05a14290d3dc255223cba51db4b0f3da438d5250657996fa99b2a30faf43e"
Add hidden `coreos-rootfs seal` command All this does is put the immutable bit on the target directory. The intention is to replace this bit to start: https://github.com/coreos/coreos-assembler/blob/8b205bfbb971707382ace76bbb39e46ed3fc560d/src/create_disk.sh#L229 However, the real goal here is to add code in this file to handle redeploying the rootfs for Fedora CoreOS which combines OSTree+Ignition: https://github.com/coreos/fedora-coreos-tracker/issues/94 Basically doing this in proper Rust is going to be a lot nicer than shell script in dracut modules. Among other details, coreutils `mv` doesn't seem to do the right thing for SELinux labels when policy isn't loaded.
2019-09-25 14:52:44 +03:00
"checksum heck 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "20564e78d53d2bb135c343b3f47714a56af2061f1c928fdb541dc7b9fdd94205"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum hermit-abi 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "eff2656d88f158ce120947499e971d743c05dbcbed62e5bd2f38f1698bbc3772"
build(deps): bump indicatif from 0.11.0 to 0.13.0 in /rust Bumps [indicatif](https://github.com/mitsuhiko/indicatif) from 0.11.0 to 0.13.0. - [Release notes](https://github.com/mitsuhiko/indicatif/releases) - [Commits](https://github.com/mitsuhiko/indicatif/compare/0.11.0...0.13.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-28 22:28:34 +03:00
"checksum indicatif 0.13.0 (registry+https://github.com/rust-lang/crates.io-index)" = "8572bccfb0665e70b7faf44ee28841b8e0823450cd4ad562a76b5a3c4bf48487"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum itoa 0.4.5 (registry+https://github.com/rust-lang/crates.io-index)" = "b8b7a7c0c47db5545ed3fef7468ee7bb5b74691498139e4b3f6a20685dc6dd8e"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)" = "d515b1f41455adea1313a4a2ac8a8a477634fbae63cc6100e3aebb207ce61558"
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"
rust: Bump dependencies Now that our minimum Rust toolchain version was bumped, we can bump all our deps to the latest and drop the frozen `rand` version that was done for #1777. Closes: #1810 Approved by: jlebon
2019-04-03 18:35:04 +03:00
"checksum linked-hash-map 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "ae91b68aebc4ddb91978b11a1b02ddd8602a05ec19002801c5666000e05e0f83"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)" = "14b6052be84e6b71ab17edffc2eeabf5c2c3ae1fdb464aae35ac50c67a44e1f7"
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 memchr 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "148fab2e51b4f1cfc66da2a7c32981d1d3c083a803978268bb11fe4b86925e7a"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum memoffset 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)" = "75189eb85871ea5c2e2c15abbdd541185f63b408415e5051f5cac122d8c774b9"
rust: Add nix as a dependency I have multiple outstanding PRs that use it and they conflict on this, so let's just upstream it now. It helps avoid some use of `unsafe` talking to libc directly.
2019-08-30 16:17:40 +03:00
"checksum nix 0.15.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3b2e0b4f3320ed72aaedb9a5ac838690a8047c7b275da22711fddff4f8a14229"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum num-integer 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)" = "3f6ea62e9d81a77cd3ee9a2a5b9b609447857f3d358704331e4ef39eb247fcba"
"checksum num-traits 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)" = "c62be47e61d1842b9170f0fdeec8eba98e60e90e5446449a0545e5152acd7096"
"checksum num_cpus 1.12.0 (registry+https://github.com/rust-lang/crates.io-index)" = "46203554f085ff89c235cd12f7075f3233af9b11ed7c9e16dfe2560d03313ce6"
build(deps): bump indicatif from 0.11.0 to 0.13.0 in /rust Bumps [indicatif](https://github.com/mitsuhiko/indicatif) from 0.11.0 to 0.13.0. - [Release notes](https://github.com/mitsuhiko/indicatif/releases) - [Commits](https://github.com/mitsuhiko/indicatif/compare/0.11.0...0.13.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-28 22:28:34 +03:00
"checksum number_prefix 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "17b02fc0ff9a9e4b35b3342880f48e896ebf69f2967921fe8646bf5b7125956a"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum openat 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)" = "cce57a26bf1be2fd7f170bf3bdcd94a07a6d28d3cb1f3aa368453126cf42819a"
"checksum openat-ext 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "281b3223dcb8d9101d1e73ac59964fe38d0c73252a9730c055690cfef8c9ce76"
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 openssl-probe 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "77af24da69f9d9341038eba93a073b1fdaaa1b788221b00a69bce9e762cb32de"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum openssl-sys 0.9.53 (registry+https://github.com/rust-lang/crates.io-index)" = "465d16ae7fc0e313318f7de5cecf57b2fbe7511fd213978b457e1c96ff46736f"
"checksum pkg-config 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)" = "05da548ad6865900e60eaba7f589cc0783590a92e940c26953ff81ddbab2d677"
"checksum ppv-lite86 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)" = "74490b50b9fbe561ac330df47c08f3f33073d2d00c150f719147d7c54522fa1b"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)" = "cf3d2011ab5c909338f7887f4fc896d35932e29146c12c8d01da6b22a80ba759"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum proc-macro2 1.0.8 (registry+https://github.com/rust-lang/crates.io-index)" = "3acb317c6ff86a4e579dfa00fc5e6cca91ecbb4e7eb2df0468805b674eb88548"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)" = "6ce23b6b870e8f94f81fb0a363d65d86675884b34a09043c81e5562f11c1f8e1"
"checksum quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "053a8c8bcc71fcce321828dc897a98ab9760bef03a4fc36693c231e5b3216cfe"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum rand 0.7.3 (registry+https://github.com/rust-lang/crates.io-index)" = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum rand_chacha 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "03a2a90da8c7523f554344f921aa97283eadf6ac484a6d2a7d0212fa7f8d6853"
"checksum rand_core 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
"checksum rand_hc 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum rayon 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "db6ce3297f9c85e16621bb8cca38a06779ffc31bb8184e1be4bed2be4678a098"
"checksum rayon-core 1.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "08a89b46efaf957e52b18062fb2f4660f8b8a4dde1807ca002690868ef2c85a9"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)" = "2439c63f3f6139d1b57529d16bc3b8bb855230c8efcc5d3a896c8bea7c3b1e84"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum regex 1.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "b5508c1941e4e7cb19965abef075d35a9a8b5cdf0846f30b4050e9b55dc55e87"
"checksum regex-syntax 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)" = "e734e891f5b408a29efbf8309e656876276f49ab6a6ac208600b4419bd893d90"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum remove_dir_all 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "4a83fa3702a688b9359eccba92d153ac33fd2e8462f9e0e3fdf155239ea7792e"
"checksum rustc-demangle 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)" = "4c691c0e608126e00913e33f0ccf3727d5fc84573623b8d65b2df340b5201783"
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"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum ryu 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "bfa8506c1de11c9c4e4c38863ccbe02a305c8188e85a05a784c9e11e1c3910c8"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum schannel 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)" = "87f550b06b6cba9c8b8be3ee73f391990116bf527450d2556e9b9ce263b9a021"
"checksum scopeguard 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b42e15e59b18a828bbf5c58ea01debb36b9b096346de35d941dcb89009f24a0d"
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 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: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum serde 1.0.104 (registry+https://github.com/rust-lang/crates.io-index)" = "414115f25f818d7dfccec8ee535d76949ae78584fc4f79a6f45a904bf8ab4449"
"checksum serde_derive 1.0.104 (registry+https://github.com/rust-lang/crates.io-index)" = "128f9e303a5a29922045a830221b8f78ec74a5f544944f3d5984f8ec3895ef64"
"checksum serde_json 1.0.45 (registry+https://github.com/rust-lang/crates.io-index)" = "eab8f15f15d6c41a154c1b128a22f2dfabe350ef53c40953d84e36155c91192b"
"checksum serde_yaml 0.8.11 (registry+https://github.com/rust-lang/crates.io-index)" = "691b17f19fc1ec9d94ec0b5864859290dff279dbd7b03f017afda54eb36c3c35"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum socket2 0.3.11 (registry+https://github.com/rust-lang/crates.io-index)" = "e8b74de517221a2cb01a53349cf54182acdc31a074727d3079068448c0676d85"
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"
Add hidden `coreos-rootfs seal` command All this does is put the immutable bit on the target directory. The intention is to replace this bit to start: https://github.com/coreos/coreos-assembler/blob/8b205bfbb971707382ace76bbb39e46ed3fc560d/src/create_disk.sh#L229 However, the real goal here is to add code in this file to handle redeploying the rootfs for Fedora CoreOS which combines OSTree+Ignition: https://github.com/coreos/fedora-coreos-tracker/issues/94 Basically doing this in proper Rust is going to be a lot nicer than shell script in dracut modules. Among other details, coreutils `mv` doesn't seem to do the right thing for SELinux labels when policy isn't loaded.
2019-09-25 14:52:44 +03:00
"checksum structopt 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)" = "16c2cdbf9cc375f15d1b4141bc48aeef444806655cd0e904207edc8d68d86ed7"
"checksum structopt-derive 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)" = "53010261a84b37689f9ed7d395165029f9cc7abb9f56bbfe86bee2597ed25107"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum syn 0.15.44 (registry+https://github.com/rust-lang/crates.io-index)" = "9ca4b3b69a77cbe1ffc9e198781b7acb0c7365a883670e8f1c1bc66fba79a5c5"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum syn 1.0.14 (registry+https://github.com/rust-lang/crates.io-index)" = "af6f3550d8dff9ef7dc34d384ac6f107e5d31c8f57d9f28e0081503f547ac8f5"
"checksum synstructure 0.12.3 (registry+https://github.com/rust-lang/crates.io-index)" = "67656ea1dc1b41b1451851562ea232ec2e5a80242139f7e679ceccfb5d61f545"
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 systemd 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "daf2fd2d346d2dfb5fdc5f47b355f60dcfc35f5ee3e89e64e7ae2849ec8792a5"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7a6e24d9338a0a5be79593e2fa15a648add6138caa803e2d5bc782c371732ca9"
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 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/lockfile: Add more metadata to generated lockfiles E.g. the generation timestamp, repos that were enabled, and their generation timestamps. This is just generally useful, though I'd like to make use specifically of the new `metadata.generated` key in FCOS to drive versioning: https://github.com/coreos/fedora-coreos-releng-automation/pull/50
2019-11-11 16:50:58 +03:00
"checksum time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)" = "db8dcfca086c1143c9270ac42a2bbd8a7ee477b78ac8e45b19abfb0cbede4b6f"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum unicode-segmentation 1.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e83e153d1053cbb5a118eeff7fd5be06ed99153f00dbcd8ae310c5fb2b22edc0"
"checksum unicode-width 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "caaa9d531767d1ff2150b9332433f32a24622147e5ebb1f26409d5da67afd479"
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 unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fc72304796d0818e357ead4e000d19c9c174ab23dc11093ac919054d20a6a7fc"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum unicode-xid 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "826e7639553986605ec5979c7dd957c7895e93eabed50ab2ffa7f6128a75097c"
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 utf8-cstr 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "55bcbb425141152b10d5693095950b51c3745d019363fc2929ffd8f61449b628"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum vcpkg 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "3fc439f2794e98976c88a2a2dafce96b930fe8010b0a256b3c2199a773933168"
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"
rust: Add nix as a dependency I have multiple outstanding PRs that use it and they conflict on this, so let's just upstream it now. It helps avoid some use of `unsafe` talking to libc directly.
2019-08-30 16:17:40 +03:00
"checksum void 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
"checksum wasi 0.9.0+wasi-snapshot-preview1 (registry+https://github.com/rust-lang/crates.io-index)" = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
rust: cargo update Been a while. I think we may be clear to do this now. A lot of stuff like newer rand, etc. Closes: #1912 Approved by: jlebon
2019-09-26 00:09:25 +03:00
"checksum winapi 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)" = "8093091eeb260906a183e6ae1abdba2ef5ef2257a21801128899c3fc699229c6"
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 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