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

1493 lines
36 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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
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 = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"winapi",
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
rust: Start porting from failure to anyhow The failure crate isn't actively developed anymore. The main benefit of `anyhow` is it uses the standard error type. More info: https://docs.rs/crate/anyhow/1.0.28 Start the porting process. Note that the `envsubst` crate has a public dependency on `failure`, so we need to start mapping its errors.
2020-03-31 18:30:31 +03:00
[[package]]
name = "anyhow"
build(deps): bump anyhow from 1.0.34 to 1.0.35 in /rust Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.34 to 1.0.35. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](https://github.com/dtolnay/anyhow/compare/1.0.34...1.0.35) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-07 18:35:43 +03:00
version = "1.0.35"
rust: Start porting from failure to anyhow The failure crate isn't actively developed anymore. The main benefit of `anyhow` is it uses the standard error type. More info: https://docs.rs/crate/anyhow/1.0.28 Start the porting process. Note that the `envsubst` crate has a public dependency on `failure`, so we need to start mapping its errors.
2020-03-31 18:30:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump anyhow from 1.0.34 to 1.0.35 in /rust Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.34 to 1.0.35. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](https://github.com/dtolnay/anyhow/compare/1.0.34...1.0.35) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-07 18:35:43 +03:00
checksum = "2c0df63cb2955042487fad3aefd2c6e3ae7389ac5dc1beb28921de0b69f779d4"
rust: Start porting from failure to anyhow The failure crate isn't actively developed anymore. The main benefit of `anyhow` is it uses the standard error type. More info: https://docs.rs/crate/anyhow/1.0.28 Start the porting process. Note that the `envsubst` crate has a public dependency on `failure`, so we need to start mapping its errors.
2020-03-31 18:30:31 +03:00
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "arrayref"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "a4c527152e37cf757a3f78aae5a06fbeefdb07ccc535c980a3208ee3060dd544"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"hermit-abi",
"libc",
"winapi",
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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "cdb031dd78e28731d87d56cc8ffef4a8f36ca26c38fe2de700543e627f8a464a"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
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
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
[[package]]
name = "build-env"
build(deps): bump systemd from 0.7.1 to 0.8.1 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.7.1 to 0.8.1. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.7.1...systemd-0.8.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-16 09:32:42 +03:00
version = "0.3.0"
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump systemd from 0.7.1 to 0.8.1 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.7.1 to 0.8.1. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.7.1...systemd-0.8.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-16 09:32:42 +03:00
checksum = "6cf89846ef2b2674ef1c153256cec98fba587c72bf4ea2c4b2f6d91a19f55926"
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "f747ed2575d426b7cbf0fcba5872db319a600d597391c339779a3d9835d1ea4d"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"version_check 0.1.5",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Rework bindgen/cxx.rs usage and CI build cxx.rs (aka cxxbridge) and cbindgen are both generating source code. Since the last release we've introduced the former, and we need to ensure that the generated cxx.rs source ends up in release tarballs the same way as the cbindgen code. Rationalize and clean up the binding infrastructure. Drop support for the vendored cbindgen which we weren't actually using: Closes: https://github.com/coreos/rpm-ostree/issues/2392 Move the cxx-rs and cbindgen bits into the same place, and update our CoreOS CI build to use a separate `Makefile.bindings` that just generates the code, so our CI still "works like" a main Koji RPM build.
2020-12-31 19:55:19 +03:00
[[package]]
name = "cbindgen"
version = "0.16.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9344318b9c787667b95cd2c5124f5eaf2bde35e959dd01ea04fc5b234c542c11"
dependencies = [
"clap",
"heck",
"indexmap",
"log",
"proc-macro2",
"quote",
"serde",
"serde_json",
"syn",
"tempfile",
"toml",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "cc"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.0.61"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "ed67cbde08356238e75fc4656be4749481eeffb09e19f320a25237d5221c985d"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
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"
build(deps): bump chrono from 0.4.18 to 0.4.19 in /rust Bumps [chrono](https://github.com/chronotope/chrono) from 0.4.18 to 0.4.19. - [Release notes](https://github.com/chronotope/chrono/releases) - [Changelog](https://github.com/chronotope/chrono/blob/main/CHANGELOG.md) - [Commits](https://github.com/chronotope/chrono/compare/v0.4.18...v0.4.19) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-05 10:19:54 +03:00
version = "0.4.19"
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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
"num-integer",
"num-traits",
"serde",
"time",
"winapi",
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: 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"
build(deps): bump clap from 2.33.2 to 2.33.3 in /rust Bumps [clap](https://github.com/clap-rs/clap) from 2.33.2 to 2.33.3. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/v2.33.3/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.33.2...v2.33.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-17 16:47:59 +03:00
version = "2.33.3"
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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "37e58ac78573c40708d45522f0d80fa2f01cc4f9b4e2bf749807255454312002"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"ansi_term",
"atty",
"bitflags",
"strsim",
"textwrap",
"unicode-width",
"vec_map",
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: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "a50aab2529019abfabfa93f1e6c41ef392f91fbf179b347a7e96abb524884a08"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"encode_unicode",
"lazy_static",
"libc",
"regex",
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"terminal_size",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"unicode-width",
"winapi",
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"winapi-util",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
[[package]]
name = "const_fn"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ce90df4c658c62f12d78f7508cf92f9173e5184a539c10bfe54a3107b3ffd0f2"
build(deps): bump rayon from 1.3.1 to 1.4.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.3.1 to 1.4.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/v1.3.1...rayon-core-v1.4.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-09-08 20:04:48 +03:00
[[package]]
name = "crossbeam-channel"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
version = "0.5.0"
build(deps): bump rayon from 1.3.1 to 1.4.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.3.1 to 1.4.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/v1.3.1...rayon-core-v1.4.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-09-08 20:04:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
checksum = "dca26ee1f8d361640700bde38b2c37d8c22b3ce2d360e1fc1c74ea4b0aa7d775"
build(deps): bump rayon from 1.3.1 to 1.4.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.3.1 to 1.4.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/v1.3.1...rayon-core-v1.4.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-09-08 20:04:48 +03:00
dependencies = [
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 1.0.0",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"crossbeam-utils",
build(deps): bump rayon from 1.3.1 to 1.4.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.3.1 to 1.4.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/v1.3.1...rayon-core-v1.4.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-09-08 20:04:48 +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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
checksum = "94af6efb46fef72616855b036a624cf27ba656ffc9be1b9a3c931cfc7749a9a9"
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
dependencies = [
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 1.0.0",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"crossbeam-epoch",
"crossbeam-utils",
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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
version = "0.9.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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
checksum = "ec0f606a85340376eef0d6d8fec399e6d4a544d648386c6645eb6d0653b27d9f"
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
dependencies = [
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 1.0.0",
"const_fn",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"crossbeam-utils",
"lazy_static",
"memoffset",
"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
]
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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
checksum = "ec91540d98355f690a86367e566ecad2e9e579f230230eb7c21398372be73ea5"
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
dependencies = [
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"autocfg",
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 1.0.0",
"const_fn",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"lazy_static",
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"
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
version = "0.1.1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "20bd4e8067c20c7c3a4dea759ef91d4b18418ddb5bd8837ef6e2f2f93ca7ccbb"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 0.1.10",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"memchr",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.4.34"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "e268162af1a5fe89917ae25ba3b0a77c8da752bdc58e7dbb4f15b91fbd33756e"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"curl-sys",
"libc",
"openssl-probe",
"openssl-sys",
"schannel",
"socket2",
"winapi",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.4.38+curl-7.73.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "498ecfb4f59997fd40023d62a9f1e506e768b2baeb59a1d311eb9751cdcd7e3f"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"cc",
"libc",
"libz-sys",
"openssl-sys",
"pkg-config",
"vcpkg",
"winapi",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
[[package]]
name = "cxx"
Bump to cxx-rs 1.0.20 This gives us `c_str()`.
2020-12-23 17:20:51 +03:00
version = "1.0.20"
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump to cxx-rs 1.0.20 This gives us `c_str()`.
2020-12-23 17:20:51 +03:00
checksum = "a9615c89d0b2177de13e42c16baf3e5a5f6614af361ee7cd001e03b0abc2d9ca"
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
dependencies = [
"cc",
"cxxbridge-flags",
"cxxbridge-macro",
"link-cplusplus",
]
[[package]]
name = "cxxbridge-flags"
Bump to cxx-rs 1.0.20 This gives us `c_str()`.
2020-12-23 17:20:51 +03:00
version = "1.0.20"
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump to cxx-rs 1.0.20 This gives us `c_str()`.
2020-12-23 17:20:51 +03:00
checksum = "6b8c8eb327a5cd189223cfdd5fc6ee8a2270097fcdaf8ea813c22f4c3542ade0"
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
[[package]]
name = "cxxbridge-macro"
Bump to cxx-rs 1.0.20 This gives us `c_str()`.
2020-12-23 17:20:51 +03:00
version = "1.0.20"
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump to cxx-rs 1.0.20 This gives us `c_str()`.
2020-12-23 17:20:51 +03:00
checksum = "35002f70d61f451bbd172868be7016074e971b542ad79e5b189c7a1a4c12e02e"
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
Update to openat-ext 0.1.8, use new file writing API This cleans up several cases. Remove the utils path.
2020-10-27 19:37:00 +03:00
[[package]]
name = "drop_bomb"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9bda8e21c04aca2ae33ffc2fd8c23134f3cac46db123ba97bd9d3f3b8a4a85e1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.4.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "134951f4028bdadb9b84baf4232681efbf277da25144b9b0ad65df75946c422b"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "either"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.6.1"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "e78d4f1cc4ae33bbfc157ed5d5a5ef3bc29227303d595861deb238fcec4e9457"
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: 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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "a357d28ed41a50f9c765dbfe56cbc04a64e53e5fc58ba79fbc34c10ef3df831f"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
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"
build(deps): bump envsubst from 0.1.1 to 0.2.0 in /rust Bumps [envsubst](https://github.com/lucab/envsubst-rs) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/lucab/envsubst-rs/releases) - [Commits](https://github.com/lucab/envsubst-rs/compare/0.1.1...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-06 17:53:34 +03:00
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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "87bf9e478f69f88f589c11ddc017e4ddfcfd196ee2c9a4249074c83ddf544162"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"thiserror",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
[[package]]
name = "foreign-types"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "d737d9aa519fb7b749cbc3b962edcf310a8dd1f4b67c91c4f83975dbdd17d965"
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"foreign-types-macros",
"foreign-types-shared",
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
]
[[package]]
name = "foreign-types-macros"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "63f713f8b2aa9e24fec85b0e290c56caee12e3b6ae0aeeda238a75b28251afd6"
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro2",
"quote",
"syn",
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
]
[[package]]
name = "foreign-types-shared"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "7684cf33bb7f28497939e8c7cf17e3e4e3b8d9a0080ffa4f8ae2f515442ee855"
build(deps): bump systemd from 0.4.0 to 0.5.0 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/commits/v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-08-24 18:40:22 +03:00
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "futures"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "5d8e3078b7b2a8a671cb7a3d17b4760e4181ea243227776ba83fd043b4ca034e"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"futures-channel",
"futures-core",
"futures-executor",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
]
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "futures-channel"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "a7a4d35f7401e948629c9c3d6638fb9bf94e0b2121e96c3b428cc4e631f3eb74"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"futures-core",
"futures-sink",
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
]
[[package]]
name = "futures-core"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "d674eaa0056896d5ada519900dbf97ead2e46a7b6621e8160d79e2f2e1e2784b"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "futures-executor"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "cc709ca1da6f66143b8c9bec8e6260181869893714e9b5a490b169b0414144ab"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"futures-core",
"futures-task",
"futures-util",
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "futures-io"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "5fc94b64bb39543b4e432f1790b6bf18e3ee3b74653c5449f63310e9a74b123c"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "futures-macro"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "f57ed14da4603b2554682e9f2ff3c65d7567b53188db96cb71538217fc64581b"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro-hack",
"proc-macro2",
"quote",
"syn",
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "futures-sink"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "0d8764258ed64ebc5d9ed185cf86a95db5cac810269c5d20ececb32e0088abbd"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "futures-task"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "4dd26820a9f3637f1302da8bceba3ff33adbe53464b54ca24d4e2d4f1db30f94"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"once_cell",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
]
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "futures-util"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.6"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "8a894a0acddba51a2d49a6f4263b1e64b8c579ece8af50fa86503d52cd1eea34"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"futures-channel",
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
"pin-project",
"pin-utils",
"proc-macro-hack",
"proc-macro-nested",
"slab",
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +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 = "getrandom"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.1.15"
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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "fc587bc0ec293155d5bfa6b9891ec18a1e330c234f896ea47fbada4cadbe47e6"
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
dependencies = [
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 0.1.10",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"wasi 0.9.0+wasi-snapshot-preview1",
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
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "gio"
build(deps): bump gio from 0.9.0 to 0.9.1 in /rust Bumps [gio](https://github.com/gtk-rs/gio) from 0.9.0 to 0.9.1. - [Release notes](https://github.com/gtk-rs/gio/releases) - [Commits](https://github.com/gtk-rs/gio/compare/0.9.0...0.9.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-09-14 10:14:49 +03:00
version = "0.9.1"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "1fb60242bfff700772dae5d9e3a1f7aa2e4ebccf18b89662a16acb2822568561"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"bitflags",
"futures",
"futures-channel",
"futures-core",
"futures-io",
"futures-util",
"gio-sys",
"glib",
"glib-sys",
"gobject-sys",
"libc",
"once_cell",
"thiserror",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.10.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "5e24fb752f8f5d2cf6bbc2c606fd2bc989c81c5e2fe321ab974d54f8b6344eac"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"glib-sys",
"gobject-sys",
"libc",
"system-deps",
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"winapi",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.10.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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "0c685013b7515e668f1b57a165b009d4d28cb139a8a989bbd699c10dad29d0c5"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"bitflags",
"futures-channel",
"futures-core",
"futures-executor",
"futures-task",
"futures-util",
"glib-macros",
"glib-sys",
"gobject-sys",
"libc",
"once_cell",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
]
[[package]]
name = "glib-macros"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "41486a26d1366a8032b160b59065a59fb528530a46a49f627e7048fb8c064039"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"anyhow",
"heck",
"itertools",
"proc-macro-crate",
"proc-macro-error",
"proc-macro2",
"quote",
"syn",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump glib-sys from 0.10.0 to 0.10.1 in /rust Bumps [glib-sys](https://github.com/gtk-rs/sys) from 0.10.0 to 0.10.1. - [Release notes](https://github.com/gtk-rs/sys/releases) - [Commits](https://github.com/gtk-rs/sys/compare/glib-sys-0.10.0...glib-sys-0.10.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-09-21 10:22:04 +03:00
version = "0.10.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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "c7e9b997a66e9a23d073f2b1abb4dbfc3925e0b8952f67efd8d9b6e168e4cdc1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
"system-deps",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
version = "0.10.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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "952133b60c318a62bf82ee75b93acc7e84028a093e06b9e27981c2b6fe68218c"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"glib-sys",
"libc",
"system-deps",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Rework bindgen/cxx.rs usage and CI build cxx.rs (aka cxxbridge) and cbindgen are both generating source code. Since the last release we've introduced the former, and we need to ensure that the generated cxx.rs source ends up in release tarballs the same way as the cbindgen code. Rationalize and clean up the binding infrastructure. Drop support for the vendored cbindgen which we weren't actually using: Closes: https://github.com/coreos/rpm-ostree/issues/2392 Move the cxx-rs and cbindgen bits into the same place, and update our CoreOS CI build to use a separate `Makefile.bindings` that just generates the code, so our CI still "works like" a main Koji RPM build.
2020-12-31 19:55:19 +03:00
[[package]]
name = "hashbrown"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d7afe4a420e3fe79967a00898cc1f4db7c8a49a9333a29f8a4bd76a253d5cd04"
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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "20564e78d53d2bb135c343b3f47714a56af2061f1c928fdb541dc7b9fdd94205"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"unicode-segmentation",
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
]
[[package]]
name = "hermit-abi"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.1.17"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "5aca5565f760fb5b220e499d72710ed156fdb74e631659e99377d9ebfbd13ae8"
rust: cargo update We haven't done one of these in a while.
2020-01-25 00:59:29 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
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
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "hex"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "644f9158b2f133fd50f5fb3242878846d9eb792e445c893805ff0e3824006e35"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
Rework bindgen/cxx.rs usage and CI build cxx.rs (aka cxxbridge) and cbindgen are both generating source code. Since the last release we've introduced the former, and we need to ensure that the generated cxx.rs source ends up in release tarballs the same way as the cbindgen code. Rationalize and clean up the binding infrastructure. Drop support for the vendored cbindgen which we weren't actually using: Closes: https://github.com/coreos/rpm-ostree/issues/2392 Move the cxx-rs and cbindgen bits into the same place, and update our CoreOS CI build to use a separate `Makefile.bindings` that just generates the code, so our CI still "works like" a main Koji RPM build.
2020-12-31 19:55:19 +03:00
[[package]]
name = "indexmap"
version = "1.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4fb1fa934250de4de8aef298d81c729a7d33d8c239daa3a7575e6b92bfc7313b"
dependencies = [
"autocfg",
"hashbrown",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.14.0 to 0.15.0 in /rust Bumps [indicatif](https://github.com/mitsuhiko/indicatif) from 0.14.0 to 0.15.0. - [Release notes](https://github.com/mitsuhiko/indicatif/releases) - [Commits](https://github.com/mitsuhiko/indicatif/compare/0.14.0...0.15.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-06-15 12:31:43 +03:00
version = "0.15.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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "7baab56125e25686df467fe470785512329883aab42696d661247aca2a2896e4"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"console",
"lazy_static",
"number_prefix",
"regex",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "itertools"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "284f18f85651fe11e8a991b2adb42cb078325c996ed026d994719efcfca1d54b"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"either",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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 = "itoa"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.4.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "dc6f3ad7b9d11a0c00842ff8de1b60ee58661048eb8049ed33c73594f359d7e6"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "libc"
build(deps): bump libc from 0.2.80 to 0.2.81 in /rust Bumps [libc](https://github.com/rust-lang/libc) from 0.2.80 to 0.2.81. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.80...0.2.81) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-07 16:17:25 +03:00
version = "0.2.81"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump libc from 0.2.80 to 0.2.81 in /rust Bumps [libc](https://github.com/rust-lang/libc) from 0.2.80 to 0.2.81. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.80...0.2.81) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-07 16:17:25 +03:00
checksum = "1482821306169ec4d07f6aca392a4681f66c75c9918aa49641a2595db64053cb"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: move libdnf-sys module to its own crate This is just a cleaner arrangement to make the separation more explicit. It also matches what most other wrapper crates do. One advantage of this is that we can tell cbindgen directly that we don't want it to ever export symbols from `libdnf-sys`. Related discussions in: https://github.com/coreos/rpm-ostree/pull/2047
2020-04-07 18:09:17 +03:00
[[package]]
name = "libdnf-sys"
version = "0.1.0"
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
rust: move libdnf-sys module to its own crate This is just a cleaner arrangement to make the separation more explicit. It also matches what most other wrapper crates do. One advantage of this is that we can tell cbindgen directly that we don't want it to ever export symbols from `libdnf-sys`. Related discussions in: https://github.com/coreos/rpm-ostree/pull/2047
2020-04-07 18:09:17 +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 = "libsystemd-sys"
build(deps): bump systemd from 0.7.1 to 0.8.1 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.7.1 to 0.8.1. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.7.1...systemd-0.8.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-16 09:32:42 +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"
build(deps): bump systemd from 0.7.1 to 0.8.1 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.7.1 to 0.8.1. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.7.1...systemd-0.8.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-16 09:32:42 +03:00
checksum = "6e03fd580bcecda68dcdcd5297085ade6a3dc552cd8b030d2b94a9b089ef7ab8"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"build-env",
"libc",
"pkg-config",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.1.2"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "602113192b08db8f38796c4e85c39e960c145965140e918018bcde1952429655"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"cc",
"libc",
"pkg-config",
"vcpkg",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
[[package]]
name = "link-cplusplus"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f96aa785c87218ec773df6c510af203872b34e2df2cf47d6e908e5f36231e354"
dependencies = [
"cc",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.5.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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "8dd5a6d5999d9907cda8ed67bbd137d3af8085216c2ac62de5be860bd41f304a"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "log"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.4.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "4fabed175da42fed1fa0746b0ea71f412aa9d35e76e95e59b192c64b9dc2bf8b"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 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
]
[[package]]
name = "memchr"
build(deps): bump systemd from 0.7.0 to 0.7.1 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.7.0 to 0.7.1. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.7.0...systemd-0.7.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-02 09:51:19 +03:00
version = "2.3.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"
build(deps): bump systemd from 0.7.0 to 0.7.1 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.7.0 to 0.7.1. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.7.0...systemd-0.7.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-02 09:51:19 +03:00
checksum = "0ee1c47aaa256ecabcaea351eae4a9b01ef39ed810004e298d2511ed284b1525"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 a Rust helper to create a sealed memfd, use in shlib backend Prep for other code using memfds.
2021-01-12 21:43:58 +03:00
[[package]]
name = "memfd"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "59c3b335b96d56e116c654a994b2b1b83b4e5b4d0a2a95085fc35464eecf4f03"
dependencies = [
"either",
"libc",
"thiserror",
]
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.5.6"
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "043175f069eda7b85febe4a74abbaeff828d9f8b448515d3151a14a3542811aa"
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"autocfg",
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
]
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
ci: Bump MSRV to 1.43.1 This is available in the RHEL 8.2 buildroot now. Also fixes compilation with latest `openat-ext` crate which uses `std::usize::MAX`.
2020-07-27 17:05:47 +03:00
[[package]]
name = "nix"
Update to openat-ext 0.1.8, use new file writing API This cleans up several cases. Remove the utils path.
2020-10-27 19:37:00 +03:00
version = "0.18.0"
ci: Bump MSRV to 1.43.1 This is available in the RHEL 8.2 buildroot now. Also fixes compilation with latest `openat-ext` crate which uses `std::usize::MAX`.
2020-07-27 17:05:47 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to openat-ext 0.1.8, use new file writing API This cleans up several cases. Remove the utils path.
2020-10-27 19:37:00 +03:00
checksum = "83450fe6a6142ddd95fb064b746083fc4ef1705fe81f64a64e1d4b39f54a1055"
ci: Bump MSRV to 1.43.1 This is available in the RHEL 8.2 buildroot now. Also fixes compilation with latest `openat-ext` crate which uses `std::usize::MAX`.
2020-07-27 17:05:47 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"bitflags",
"cc",
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 0.1.10",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
ci: Bump MSRV to 1.43.1 This is available in the RHEL 8.2 buildroot now. Also fixes compilation with latest `openat-ext` crate which uses `std::usize::MAX`.
2020-07-27 17:05:47 +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"
build(deps): bump nix from 0.19.0 to 0.19.1 in /rust Bumps [nix](https://github.com/nix-rust/nix) from 0.19.0 to 0.19.1. - [Release notes](https://github.com/nix-rust/nix/releases) - [Changelog](https://github.com/nix-rust/nix/blob/master/CHANGELOG.md) - [Commits](https://github.com/nix-rust/nix/compare/v0.19.0...v0.19.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-30 09:29:52 +03:00
version = "0.19.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump nix from 0.19.0 to 0.19.1 in /rust Bumps [nix](https://github.com/nix-rust/nix) from 0.19.0 to 0.19.1. - [Release notes](https://github.com/nix-rust/nix/releases) - [Changelog](https://github.com/nix-rust/nix/blob/master/CHANGELOG.md) - [Commits](https://github.com/nix-rust/nix/compare/v0.19.0...v0.19.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-30 09:29:52 +03:00
checksum = "b2ccba0cfe4fdf15982d1674c69b1fd80bad427d293849982668dfe454bd61f2"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"bitflags",
"cc",
build(deps): bump nix from 0.19.0 to 0.19.1 in /rust Bumps [nix](https://github.com/nix-rust/nix) from 0.19.0 to 0.19.1. - [Release notes](https://github.com/nix-rust/nix/releases) - [Changelog](https://github.com/nix-rust/nix/blob/master/CHANGELOG.md) - [Commits](https://github.com/nix-rust/nix/compare/v0.19.0...v0.19.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-30 09:29:52 +03:00
"cfg-if 1.0.0",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
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
]
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.1.43"
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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "8d59457e662d541ba17869cf51cf177c0b5f0cbf476c66bdc90bf1edac4f875b"
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
dependencies = [
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"autocfg",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"num-traits",
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.2.12"
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "ac267bcc07f48ee5f8935ab0d24f316fb722d7a1292e2913f0cc196b29ffd611"
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"autocfg",
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.13.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"hermit-abi",
"libc",
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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "17b02fc0ff9a9e4b35b3342880f48e896ebf69f2967921fe8646bf5b7125956a"
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
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "once_cell"
version = "1.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "260e51e7efe62b592207e9e13a68e43692a7a279171d6ba57abd208bf23645ad"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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 = "openat"
build(deps): bump openat from 0.1.18 to 0.1.19 in /rust Bumps [openat](https://github.com/tailhook/openat) from 0.1.18 to 0.1.19. - [Release notes](https://github.com/tailhook/openat/releases) - [Commits](https://github.com/tailhook/openat/compare/v0.1.18...v0.1.19) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-06-15 21:32:40 +03:00
version = "0.1.19"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "8eff876e3964841fd6067ecf1d040e0315879c1a1cce2a0f162828e82f04d1ce"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump openat-ext from 0.1.8 to 0.1.9 in /rust Bumps [openat-ext](https://github.com/cgwalters/openat-ext) from 0.1.8 to 0.1.9. - [Release notes](https://github.com/cgwalters/openat-ext/releases) - [Commits](https://github.com/cgwalters/openat-ext/compare/v0.1.8...v0.1.9) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-16 09:32:48 +03:00
version = "0.1.9"
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"
build(deps): bump openat-ext from 0.1.8 to 0.1.9 in /rust Bumps [openat-ext](https://github.com/cgwalters/openat-ext) from 0.1.8 to 0.1.9. - [Release notes](https://github.com/cgwalters/openat-ext/releases) - [Commits](https://github.com/cgwalters/openat-ext/compare/v0.1.8...v0.1.9) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-16 09:32:48 +03:00
checksum = "3dc1b204f9003fc6974231d2ed60e44206821e63c2cac1c8eccff0d2426e50f9"
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
dependencies = [
Update to openat-ext 0.1.8, use new file writing API This cleans up several cases. Remove the utils path.
2020-10-27 19:37:00 +03:00
"drop_bomb",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
Update to openat-ext 0.1.8, use new file writing API This cleans up several cases. Remove the utils path.
2020-10-27 19:37:00 +03:00
"nix 0.18.0",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"openat",
Update to openat-ext 0.1.8, use new file writing API This cleans up several cases. Remove the utils path.
2020-10-27 19:37:00 +03:00
"rand",
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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "77af24da69f9d9341038eba93a073b1fdaaa1b788221b00a69bce9e762cb32de"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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-sys"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.9.58"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "a842db4709b604f0fe5d1170ae3565899be2ad3d9cbc72dedc789ac0511f78de"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"autocfg",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"cc",
"libc",
"pkg-config",
"vcpkg",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "ostree"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.9.1"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "c5d5597fdcbd16285ef7ce0eaa91eb7c0f51514846f107fd5f68164f28006dc7"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"bitflags",
"gio",
"gio-sys",
"glib",
"glib-sys",
"gobject-sys",
"hex",
"libc",
"once_cell",
"ostree-sys",
"radix64",
"thiserror",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
]
[[package]]
name = "ostree-sys"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.7.1"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "6b1095c6e9fa5b19177d4646d1c8fb896322556b6c0da3af09c0ffc440dfcc75"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"gio-sys",
"glib-sys",
"gobject-sys",
"libc",
"system-deps",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
]
Add support for some GObject bridging to cxx-rs cxx-rs has support for bridging types, but it's more awkward for us because those types are defined in other crates, so we need to do a newtype dance. Further cxx-rs doesn't currently support automatically generating wrappers, so add a custom `gobj_wrap()` for now.
2020-12-23 03:51:07 +03:00
[[package]]
name = "paste"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c5d65c4d95931acda4498f675e332fcbdc9a06705cd07086c510e9b6009cd1c1"
Move "ignored script list" to Rust, drop gperf Rust has a nice crate for doing perfect hashing. Move that code into Rust and drop the dependency on `gperf`. This also helps move away from Autotools.
2020-12-23 20:01:33 +03:00
[[package]]
name = "phf"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3dfb61232e34fcb633f43d12c58f83c1df82962dcdfa565a4e866ffc17dafe12"
dependencies = [
"phf_macros",
"phf_shared",
"proc-macro-hack",
]
[[package]]
name = "phf_generator"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "17367f0cc86f2d25802b2c26ee58a7b23faeccf78a396094c13dced0d0182526"
dependencies = [
"phf_shared",
"rand",
]
[[package]]
name = "phf_macros"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f6fde18ff429ffc8fe78e2bf7f8b7a5a5a6e2a8b58bc5a9ac69198bbda9189c"
dependencies = [
"phf_generator",
"phf_shared",
"proc-macro-hack",
"proc-macro2",
"quote",
"syn",
]
[[package]]
name = "phf_shared"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c00cf8b9eafe68dde5e9eaa2cef8ee84a9336a47d566ec55ca16589633b65af7"
dependencies = [
"siphasher",
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "pin-project"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.4.27"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "2ffbc8e94b38ea3d2d8ba92aea2983b503cd75d0888d75b86bb37970b5698e15"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"pin-project-internal",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
]
[[package]]
name = "pin-project-internal"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.4.27"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "65ad2ae56b6abe3a1ee25f15ee605bacadb9a764edaba9c2bf4103800d4a1895"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro2",
"quote",
"syn",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
]
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "pin-utils"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
version = "0.1.0"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +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 = "pkg-config"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.19"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "3831453b3449ceb48b6d9c7ad7c96d5ea673e9b470a1dc578c2ce6521230884c"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "ppv-lite86"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.2.9"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "c36fa947111f5c62a733b652544dd0016a43ce89619538a8ef92724a6f501a20"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "proc-macro-crate"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "1d6ea3c4595b96363c13943497db34af4460fb474a95c43f4446ad341b8c9785"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"toml",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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]]
build(deps): bump structopt from 0.2.18 to 0.3.8 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.2.18 to 0.3.8. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/compare/v0.2.18...v0.3.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-29 10:35:32 +03:00
name = "proc-macro-error"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.0.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "da25490ff9892aab3fcf7c36f08cfb902dd3e71ca0f9f9517bea02a73a5ce38c"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro-error-attr",
"proc-macro2",
"quote",
"syn",
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"version_check 0.9.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
]
[[package]]
build(deps): bump structopt from 0.2.18 to 0.3.8 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.2.18 to 0.3.8. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/compare/v0.2.18...v0.3.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-29 10:35:32 +03:00
name = "proc-macro-error-attr"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.0.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "a1be40180e52ecc98ad80b184934baf3d0d29f979574e439af5a55274b35f869"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro2",
"quote",
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"version_check 0.9.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
]
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "proc-macro-hack"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.5.18"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "99c605b9a0adc77b7211c6b1f722dcb613d68d66859a44f3d485a6da332b0598"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "proc-macro-nested"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.1.6"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "eba180dafb9038b050a4c280019bbedf9f2467b61e5d892dcad585bb57aadc5a"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +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]]
build(deps): bump structopt from 0.2.18 to 0.3.8 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.2.18 to 0.3.8. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/compare/v0.2.18...v0.3.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-29 10:35:32 +03:00
name = "proc-macro2"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.0.24"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "1e0704ee1a7e00d7bb417d0770ea303c1bccbabf0ef1667dae92b5967f5f8a71"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"unicode-xid",
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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.0.7"
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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "aa563d17ecb180e500da1cfd2b028310ac758de548efdd203e18f283af693f37"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro2",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "radix64"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "999718fa65c3be3a74f3f6dae5a98526ff436ea58a82a574f0de89eecd342bee"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"arrayref",
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 0.1.10",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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"
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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"getrandom",
"libc",
"rand_chacha",
"rand_core",
"rand_hc",
Move "ignored script list" to Rust, drop gperf Rust has a nice crate for doing perfect hashing. Move that code into Rust and drop the dependency on `gperf`. This also helps move away from Autotools.
2020-12-23 20:01:33 +03:00
"rand_pcg",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.2.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "f4c8ed856279c9737206bf725bf36935d8666ead7aa69b52be55af369d193402"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"ppv-lite86",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"rand_core",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"getrandom",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"rand_core",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 "ignored script list" to Rust, drop gperf Rust has a nice crate for doing perfect hashing. Move that code into Rust and drop the dependency on `gperf`. This also helps move away from Autotools.
2020-12-23 20:01:33 +03:00
[[package]]
name = "rand_pcg"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "16abd0c1b639e9eb4d7c50c0b8100b0d0f849be2349829c740fe8e6eb4816429"
dependencies = [
"rand_core",
]
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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
version = "1.5.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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
checksum = "8b0d8e0819fadc20c74ea8373106ead0600e3a67ef1fe8da56e39b9ae7275674"
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
dependencies = [
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"autocfg",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"crossbeam-deque",
"either",
"rayon-core",
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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
version = "1.9.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"
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
checksum = "9ab346ac5921dc62ffa9f89b7a773907511cdfa5490c572ae9be1be33e8afa4a"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"crossbeam-channel",
"crossbeam-deque",
"crossbeam-utils",
"lazy_static",
"num_cpus",
rust: Bump crate dependencies Prep for adding other crate deps for sysusers, multiprocessing work. Closes: #1765 Approved by: jlebon
2019-02-26 18:11:05 +03:00
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.1.57"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[package]]
name = "regex"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.4.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "8963b85b8ce3074fecffde43b4b0dded83ce2f367dc8d363afc56679f3ee820b"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"regex-syntax",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.6.20"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "8cab7a364d15cde1e505267766a2d3c4e22a843e1a601f0fa7564c0f82ced11c"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "remove_dir_all"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.5.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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"winapi",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"anyhow",
"c_utf8",
Rework bindgen/cxx.rs usage and CI build cxx.rs (aka cxxbridge) and cbindgen are both generating source code. Since the last release we've introduced the former, and we need to ensure that the generated cxx.rs source ends up in release tarballs the same way as the cbindgen code. Rationalize and clean up the binding infrastructure. Drop support for the vendored cbindgen which we weren't actually using: Closes: https://github.com/coreos/rpm-ostree/issues/2392 Move the cxx-rs and cbindgen bits into the same place, and update our CoreOS CI build to use a separate `Makefile.bindings` that just generates the code, so our CI still "works like" a main Koji RPM build.
2020-12-31 19:55:19 +03:00
"cbindgen",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"chrono",
"clap",
"curl",
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
"cxx",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"envsubst",
"gio",
"gio-sys",
"glib",
"glib-sys",
"indicatif",
"lazy_static",
"libc",
"libdnf-sys",
Add a Rust helper to create a sealed memfd, use in shlib backend Prep for other code using memfds.
2021-01-12 21:43:58 +03:00
"memfd",
build(deps): bump nix from 0.19.0 to 0.19.1 in /rust Bumps [nix](https://github.com/nix-rust/nix) from 0.19.0 to 0.19.1. - [Release notes](https://github.com/nix-rust/nix/releases) - [Changelog](https://github.com/nix-rust/nix/blob/master/CHANGELOG.md) - [Commits](https://github.com/nix-rust/nix/compare/v0.19.0...v0.19.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-30 09:29:52 +03:00
"nix 0.19.1",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"openat",
"openat-ext",
"ostree",
"ostree-sys",
Add support for some GObject bridging to cxx-rs cxx-rs has support for bridging types, but it's more awkward for us because those types are defined in other crates, so we need to do a newtype dance. Further cxx-rs doesn't currently support automatically generating wrappers, so add a custom `gobj_wrap()` for now.
2020-12-23 03:51:07 +03:00
"paste",
Move "ignored script list" to Rust, drop gperf Rust has a nice crate for doing perfect hashing. Move that code into Rust and drop the dependency on `gperf`. This also helps move away from Autotools.
2020-12-23 20:01:33 +03:00
"phf",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"rand",
"rayon",
"serde",
"serde_derive",
"serde_json",
"serde_yaml",
"structopt",
daemon: Rewrite some core initramfs-overlay logic in Rust We had a memory safety/UB bug in the C code; let's use that as a good motivation to rewrite in Rust. It's a nice self contained bit.
2020-10-30 21:43:35 +03:00
"subprocess",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"systemd",
"tempfile",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "ryu"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.0.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "71d301d4193d031abdd79ff7e3dd721168a9572ef3fe51a1517aba235bd8f86e"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "schannel"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.1.19"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "8f05ba609c234e60bee0d547fe94a4c7e9da733d1c962cf6e59efa4cd9c8bc75"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"lazy_static",
"winapi",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde from 1.0.117 to 1.0.118 in /rust Bumps [serde](https://github.com/serde-rs/serde) from 1.0.117 to 1.0.118. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.117...v1.0.118) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-09 00:35:24 +03:00
version = "1.0.118"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde from 1.0.117 to 1.0.118 in /rust Bumps [serde](https://github.com/serde-rs/serde) from 1.0.117 to 1.0.118. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.117...v1.0.118) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-09 00:35:24 +03:00
checksum = "06c64263859d87aa2eb554587e2d23183398d617427327cf2b3d0ed8c69e4800"
Rework bindgen/cxx.rs usage and CI build cxx.rs (aka cxxbridge) and cbindgen are both generating source code. Since the last release we've introduced the former, and we need to ensure that the generated cxx.rs source ends up in release tarballs the same way as the cbindgen code. Rationalize and clean up the binding infrastructure. Drop support for the vendored cbindgen which we weren't actually using: Closes: https://github.com/coreos/rpm-ostree/issues/2392 Move the cxx-rs and cbindgen bits into the same place, and update our CoreOS CI build to use a separate `Makefile.bindings` that just generates the code, so our CI still "works like" a main Koji RPM build.
2020-12-31 19:55:19 +03:00
dependencies = [
"serde_derive",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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_derive"
build(deps): bump serde_derive from 1.0.117 to 1.0.118 in /rust Bumps [serde_derive](https://github.com/serde-rs/serde) from 1.0.117 to 1.0.118. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.117...v1.0.118) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-09 01:57:50 +03:00
version = "1.0.118"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde_derive from 1.0.117 to 1.0.118 in /rust Bumps [serde_derive](https://github.com/serde-rs/serde) from 1.0.117 to 1.0.118. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.117...v1.0.118) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-09 01:57:50 +03:00
checksum = "c84d3526699cd55261af4b941e4e725444df67aa4f9e6a3564f18030d12672df"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro2",
"quote",
"syn",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde_json from 1.0.59 to 1.0.60 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.59 to 1.0.60. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.59...v1.0.60) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-08 02:04:18 +03:00
version = "1.0.60"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde_json from 1.0.59 to 1.0.60 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.59 to 1.0.60. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.59...v1.0.60) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-08 02:04:18 +03:00
checksum = "1500e84d27fe482ed1dc791a56eddc2f230046a040fa908c08bda1d9fb615779"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"itoa",
"ryu",
"serde",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump serde_yaml from 0.8.13 to 0.8.14 in /rust Bumps [serde_yaml](https://github.com/dtolnay/serde-yaml) from 0.8.13 to 0.8.14. - [Release notes](https://github.com/dtolnay/serde-yaml/releases) - [Commits](https://github.com/dtolnay/serde-yaml/compare/0.8.13...0.8.14) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-02 09:51:21 +03:00
version = "0.8.14"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_yaml from 0.8.13 to 0.8.14 in /rust Bumps [serde_yaml](https://github.com/dtolnay/serde-yaml) from 0.8.13 to 0.8.14. - [Release notes](https://github.com/dtolnay/serde-yaml/releases) - [Commits](https://github.com/dtolnay/serde-yaml/compare/0.8.13...0.8.14) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-02 09:51:21 +03:00
checksum = "f7baae0a99f1a324984bcdc5f0718384c1f69775f1c7eec8b859b71b443e3fd7"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"dtoa",
"linked-hash-map",
"serde",
"yaml-rust",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 "ignored script list" to Rust, drop gperf Rust has a nice crate for doing perfect hashing. Move that code into Rust and drop the dependency on `gperf`. This also helps move away from Autotools.
2020-12-23 20:01:33 +03:00
[[package]]
name = "siphasher"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa8f3741c7372e75519bd9346068370c9cdaabcc1f9599cbcf2a2719352286b7"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +03:00
[[package]]
name = "slab"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "c111b5bd5695e56cffe5129854aa230b39c93a305372fdbb2668ca2394eea9f8"
build(deps): bump glib from 0.8.2 to 0.9.3 in /rust Bumps [glib](https://github.com/gtk-rs/glib) from 0.8.2 to 0.9.3. - [Release notes](https://github.com/gtk-rs/glib/releases) - [Commits](https://github.com/gtk-rs/glib/commits/0.9.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-03-09 10:55:56 +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 = "socket2"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.15"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "b1fa70dc5c8104ec096f4fe7ede7a221d35ae13dcd19ba1ad9a81d2cab9a1c44"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 0.1.10",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
"redox_syscall",
"winapi",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump clap from 2.32.0 to 2.33.0 in /rust Bumps [clap](https://github.com/clap-rs/clap) from 2.32.0 to 2.33.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-29 00:46:36 +03:00
version = "0.8.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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
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 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"
build(deps): bump structopt from 0.3.20 to 0.3.21 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.3.20 to 0.3.21. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/compare/v0.3.20...v0.3.21) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-09 00:33:37 +03:00
version = "0.3.21"
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"
build(deps): bump structopt from 0.3.20 to 0.3.21 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.3.20 to 0.3.21. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/compare/v0.3.20...v0.3.21) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-09 00:33:37 +03:00
checksum = "5277acd7ee46e63e5168a80734c9f6ee81b1367a7d8772a2d765df2a3705d28c"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"clap",
"lazy_static",
"structopt-derive",
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-derive"
build(deps): bump structopt from 0.3.20 to 0.3.21 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.3.20 to 0.3.21. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/compare/v0.3.20...v0.3.21) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-09 00:33:37 +03:00
version = "0.4.14"
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"
build(deps): bump structopt from 0.3.20 to 0.3.21 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.3.20 to 0.3.21. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/compare/v0.3.20...v0.3.21) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-09 00:33:37 +03:00
checksum = "5ba9cdfda491b814720b6b06e0cac513d922fc407582032e8706e9f137976f90"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"heck",
"proc-macro-error",
"proc-macro2",
"quote",
"syn",
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
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "strum"
version = "0.18.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "57bd81eb48f4c437cadc685403cad539345bf703d78e63707418431cecd4522b"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "strum_macros"
version = "0.18.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "87c85aa3f8ea653bfd3ddf25f7ee357ee4d204731f6aa9ad04002306f6e2774c"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"heck",
"proc-macro2",
"quote",
"syn",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
]
daemon: Rewrite some core initramfs-overlay logic in Rust We had a memory safety/UB bug in the C code; let's use that as a good motivation to rewrite in Rust. It's a nice self contained bit.
2020-10-30 21:43:35 +03:00
[[package]]
name = "subprocess"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "69b9ad6c3e1b525a55872a4d2f2d404b3c959b7bbcbfd83c364580f68ed157bd"
dependencies = [
"libc",
"winapi",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
version = "1.0.54"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
Use cxx-rs for core.rs This is much better than bindgen because it's fully safe. It's much more ergonomic too: - Invoke Rust methods-on-structs just like C++ methods-on-structs - Rust `Result<>` is translated automatically to exceptions See https://cxx.rs/context.html for more.
2020-12-11 04:21:33 +03:00
checksum = "9a2af957a63d6bd42255c359c93d9bfdb97076bd3b820897ce55ffbfbf107f44"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro2",
"quote",
"unicode-xid",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "system-deps"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "0f3ecc17269a19353b3558b313bba738b25d82993e30d62a18406a24aba4649b"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"heck",
"pkg-config",
"strum",
"strum_macros",
"thiserror",
"toml",
"version-compare",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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 = "systemd"
build(deps): bump systemd from 0.7.1 to 0.8.1 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.7.1 to 0.8.1. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.7.1...systemd-0.8.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-16 09:32:42 +03:00
version = "0.8.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"
build(deps): bump systemd from 0.7.1 to 0.8.1 in /rust Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.7.1 to 0.8.1. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.7.1...systemd-0.8.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-16 09:32:42 +03:00
checksum = "2543596c055336b02064936256d572f2893c8be356c8cd8414337f7df3d8cdd0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"cstr-argument",
"foreign-types",
"libc",
"libsystemd-sys",
"log",
"memchr",
"utf8-cstr",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "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
dependencies = [
build(deps): bump rayon from 1.4.1 to 1.5.0 in /rust Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.4.1 to 1.5.0. - [Release notes](https://github.com/rayon-rs/rayon/releases) - [Changelog](https://github.com/rayon-rs/rayon/blob/master/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.4.1...rayon-core-v1.5.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-10-26 09:32:58 +03:00
"cfg-if 0.1.10",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
"rand",
"redox_syscall",
"remove_dir_all",
"winapi",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
name = "terminal_size"
version = "0.1.13"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "9a14cd9f8c72704232f0bfc8455c0e861f0ad4eb60cc9ec8a170e231414c1e13"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"winapi",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump clap from 2.32.0 to 2.33.0 in /rust Bumps [clap](https://github.com/clap-rs/clap) from 2.32.0 to 2.33.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-29 00:46:36 +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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"unicode-width",
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
]
build(deps): bump envsubst from 0.1.1 to 0.2.0 in /rust Bumps [envsubst](https://github.com/lucab/envsubst-rs) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/lucab/envsubst-rs/releases) - [Commits](https://github.com/lucab/envsubst-rs/compare/0.1.1...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-06 17:53:34 +03:00
[[package]]
name = "thiserror"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.0.21"
build(deps): bump envsubst from 0.1.1 to 0.2.0 in /rust Bumps [envsubst](https://github.com/lucab/envsubst-rs) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/lucab/envsubst-rs/releases) - [Commits](https://github.com/lucab/envsubst-rs/compare/0.1.1...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-06 17:53:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "318234ffa22e0920fe9a40d7b8369b5f649d490980cf7aadcf1eb91594869b42"
build(deps): bump envsubst from 0.1.1 to 0.2.0 in /rust Bumps [envsubst](https://github.com/lucab/envsubst-rs) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/lucab/envsubst-rs/releases) - [Commits](https://github.com/lucab/envsubst-rs/compare/0.1.1...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-06 17:53:34 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"thiserror-impl",
build(deps): bump envsubst from 0.1.1 to 0.2.0 in /rust Bumps [envsubst](https://github.com/lucab/envsubst-rs) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/lucab/envsubst-rs/releases) - [Commits](https://github.com/lucab/envsubst-rs/compare/0.1.1...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-06 17:53:34 +03:00
]
[[package]]
name = "thiserror-impl"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "1.0.21"
build(deps): bump envsubst from 0.1.1 to 0.2.0 in /rust Bumps [envsubst](https://github.com/lucab/envsubst-rs) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/lucab/envsubst-rs/releases) - [Commits](https://github.com/lucab/envsubst-rs/compare/0.1.1...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-06 17:53:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "cae2447b6282786c3493999f40a9be2a6ad20cb8bd268b0a0dbf5a065535c0ab"
build(deps): bump envsubst from 0.1.1 to 0.2.0 in /rust Bumps [envsubst](https://github.com/lucab/envsubst-rs) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/lucab/envsubst-rs/releases) - [Commits](https://github.com/lucab/envsubst-rs/compare/0.1.1...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-06 17:53:34 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"proc-macro2",
"quote",
"syn",
build(deps): bump envsubst from 0.1.1 to 0.2.0 in /rust Bumps [envsubst](https://github.com/lucab/envsubst-rs) from 0.1.1 to 0.2.0. - [Release notes](https://github.com/lucab/envsubst-rs/releases) - [Commits](https://github.com/lucab/envsubst-rs/compare/0.1.1...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-06 17:53:34 +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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.1.44"
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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "6db9e6914ab8b1ae1c260a4ae7a49b6c5611b40328a735b21862567685e73255"
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
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"libc",
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
"wasi 0.10.0+wasi-snapshot-preview1",
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"winapi",
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
]
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "toml"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.5.7"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "75cf45bb0bef80604d001caaec0d09da99611b3c0fd39d3080468875cdb65645"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"serde",
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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 = "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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "e83e153d1053cbb5a118eeff7fd5be06ed99153f00dbcd8ae310c5fb2b22edc0"
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 = "unicode-width"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.1.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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "9337591893a19b88d8d87f2cec1e73fad5cdfd10e5a6f349f498ad6ea2ffb1e3"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "unicode-xid"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "f7fe0bb3479651439c9112f72b6c505038574c9fbb575ed1bf3b797fa39dd564"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "55bcbb425141152b10d5693095950b51c3745d019363fc2929ffd8f61449b628"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "vcpkg"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.2.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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "6454029bf181f092ad1b853286f23e2c507d8e8194d01d92da4a55c274a5508c"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "vec_map"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.8.2"
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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "f1bddf1187be692e79c5ffeab891132dfb0f236ed36a43c7ed39f1165ee20191"
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
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +03:00
[[package]]
name = "version-compare"
version = "0.0.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "d63556a25bae6ea31b52e640d7c41d1ab27faba4ccb600013837a3d0b3994ca1"
Use ostree-rs, and oxidize more treefile checksumming The main goal here is simply to start the ball rolling in having rpm-ostree use the ostree-rs crate, so we can use it for other code in the future. We also bump the glib crate to a new major, but no code changes were required for that. I spent a bit of time looking through our C code for an example to oxidize, but almost all of our C code using libostree also has calls back into other nontrivial rpm-ostree C code. To make a lot more oxidation progress I think we need to invent an internal `librpmostree-sys` crate so we can have Rust -> C calls. I found this bit of treefile code computing the checksum that we can oxidize - and as soon as we have more libdnf bindings we can move all of the checksumming into Rust too.
2020-08-24 16:01:39 +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 = "version_check"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "914b1a6776c4c929a602fafd8bc742e06365d4bcbe48c30f9cca5824f70dc9dd"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
build(deps): bump structopt from 0.3.12 to 0.3.13 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.3.12 to 0.3.13. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-13 11:48:49 +03:00
[[package]]
name = "version_check"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.9.2"
build(deps): bump structopt from 0.3.12 to 0.3.13 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.3.12 to 0.3.13. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-13 11:48:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "b5a972e5669d67ba988ce3dc826706fb0a8b01471c088cb0b6110b805cc36aed"
build(deps): bump structopt from 0.3.12 to 0.3.13 in /rust Bumps [structopt](https://github.com/TeXitoi/structopt) from 0.3.12 to 0.3.13. - [Release notes](https://github.com/TeXitoi/structopt/releases) - [Changelog](https://github.com/TeXitoi/structopt/blob/master/CHANGELOG.md) - [Commits](https://github.com/TeXitoi/structopt/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-04-13 11:48: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]]
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"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
[[package]]
name = "wasi"
version = "0.10.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a143597ca7c7793eff794def352d41792a93c481eb1042423ff7ff72ba2c31f"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "winapi"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
version = "0.3.9"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
"winapi",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = "yaml-rust"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +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"
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
checksum = "39f0c922f1a334134dc2f7a8b67dc5d25f0735263feec974345ff706bcf20b0d"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
dependencies = [
build(deps): bump serde_json from 1.0.57 to 1.0.59 in /rust Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.57 to 1.0.59. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.57...v1.0.59) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-16 00:56:59 +03:00
"linked-hash-map",
]
Reference in New Issue Copy Permalink