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

2196 lines
52 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.
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "adler"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
[[package]]
name = "ahash"
version = "0.4.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "739f4a8db6605981345c5654f3a85b056ce52f37a39d34da03f25bf2151ea16e"
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "aho-corasick"
version = "0.7.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7404febffaa47dac81aa44dba71523c9d069b1bdc50a77db41195149e17f68e5"
dependencies = [
"memchr",
]
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
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "ansi_term"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d52a9bb7ec0cf484c551830a7ce27bd20d67eac647e1befb56b0be4ee39a55d2"
dependencies = [
"winapi",
]
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 rust-ini from 0.16.1 to 0.17.0 Bumps [rust-ini](https://github.com/zonyitoo/rust-ini) from 0.16.1 to 0.17.0. - [Release notes](https://github.com/zonyitoo/rust-ini/releases) - [Commits](https://github.com/zonyitoo/rust-ini/compare/v0.16.1...v0.17.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-30 15:39:33 +03:00
version = "1.0.40"
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 rust-ini from 0.16.1 to 0.17.0 Bumps [rust-ini](https://github.com/zonyitoo/rust-ini) from 0.16.1 to 0.17.0. - [Release notes](https://github.com/zonyitoo/rust-ini/releases) - [Commits](https://github.com/zonyitoo/rust-ini/compare/v0.16.1...v0.17.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-30 15:39:33 +03:00
checksum = "28b2cd92db5cbd74e8e5028f7e27dd7aa3090e89e4f2a197cc7c8dfb69c7063b"
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
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "byteorder"
version = "1.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "bytes"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b700ce4376041dcd0a327fd0097c41095743c4c8af8887265942faf1100bd040"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "camino"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d4648c6d00a709aa069a236adcaae4f605a6241c72bf5bee79331a4b625921a9"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "1.0.66"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "4c0496836a84f8d0495758516b8621a622beb77c0fed418570e50764093ced48"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 system-deps from 3.0.0 to 3.1.0 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 3.0.0 to 3.1.0. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v3.0.0...v3.1.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 20:01:31 +03:00
[[package]]
name = "cfg-expr"
version = "0.7.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "30aa9e2ffbb838c6b451db14f3cd8e63ed622bf859f9956bc93845a10fafc26a"
dependencies = [
"smallvec",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
]
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "cjson"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2b601fb350e2fdbbd2ffb19aef2141fa90864d8fdca83d64466cb9bdb5694a7"
dependencies = [
"itoa",
"serde",
"serde_derive",
"serde_json",
]
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 = [
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
"ansi_term 0.11.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
"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
]
Move libdnf build over to Cargo This is now further migration towards Cargo/Rust possible because we switched our main binary. We've had an internal `libdnf-sys` crate for a while, but now it can take over the build of the underlying library too (like many `-sys` crates support). This itself is just an incremental step towards migrating the main rpm-ostree build system to e.g. cmake too (or perhaps directly with the `cc` crate, not sure yet) and driving it via `cargo` too.
2021-01-29 22:47:48 +03:00
[[package]]
name = "cmake"
version = "0.1.45"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eb6210b637171dfba4cda12e579ac6dc73f5165ad56133e5d72ef3131f320855"
dependencies = [
"cc",
]
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +03:00
[[package]]
name = "codespan-reporting"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c6ce42b8998a383572e0a802d859b1f00c79b7b7474e62fff88ee5c2845d9c13"
dependencies = [
"termcolor",
"unicode-width",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.14.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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "7cc80946b3480f421c2f17ed1cb841753a371c7c5104f51d507e13f532c856aa"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.4.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "28b9d6de7f49e22cf97ad17fc4036ece69300032f45f78f30b4a4482cdc3f4a6"
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
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "crc32fast"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "81156fece84ab6a9f2afdb109ce3ae577e42b1228441eded99bd77f627953b1a"
dependencies = [
"cfg-if 1.0.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
[[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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.9.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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "a1aaa739f95311c2c7887a76863f500026092fb1dce0161dab577e559ef3569d"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.8.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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "02d96d1e189ef58269ebe5b97953da3274d83a93af647c2ddd6f9dab28cedb8d"
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",
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"
build(deps): bump curl from 0.4.37 to 0.4.38 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.37 to 0.4.38. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.37...0.4.38) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-31 09:10:34 +03:00
version = "0.4.38"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 curl from 0.4.37 to 0.4.38 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.37 to 0.4.38. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.37...0.4.38) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-31 09:10:34 +03:00
checksum = "003cb79c1c6d1c93344c7e1201bb51c2148f24ec2bd9c253709d6b2efb796515"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump curl from 0.4.37 to 0.4.38 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.37 to 0.4.38. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.37...0.4.38) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-31 09:10:34 +03:00
version = "0.4.44+curl-7.77.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 curl from 0.4.37 to 0.4.38 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.37 to 0.4.38. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.37...0.4.38) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-31 09:10:34 +03:00
checksum = "4b6d85e9322b193f117c966e79c2d6929ec08c02f339f950044aba12e20bbaf1"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump cxx from 1.0.48 to 1.0.49 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.48 to 1.0.49. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.48...1.0.49) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 12:03:40 +03:00
version = "1.0.49"
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"
build(deps): bump cxx from 1.0.48 to 1.0.49 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.48 to 1.0.49. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.48...1.0.49) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 12:03:40 +03:00
checksum = "65369ae12626651c9d8c5ca8b44ffdb9fe7ba710508074d2997315d2fe4f4276"
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",
]
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +03:00
[[package]]
name = "cxx-build"
build(deps): bump cxx-build from 1.0.47 to 1.0.49 Bumps [cxx-build](https://github.com/dtolnay/cxx) from 1.0.47 to 1.0.49. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.47...1.0.49) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 12:03:49 +03:00
version = "1.0.49"
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump cxx-build from 1.0.47 to 1.0.49 Bumps [cxx-build](https://github.com/dtolnay/cxx) from 1.0.47 to 1.0.49. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.47...1.0.49) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 12:03:49 +03:00
checksum = "8f5bde7453f995f4edcbe37c653dbc434018a4fda5941b3437005a36f69b156a"
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +03:00
dependencies = [
"cc",
"codespan-reporting",
"lazy_static",
"proc-macro2",
"quote",
"scratch",
"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
[[package]]
name = "cxxbridge-flags"
build(deps): bump cxx from 1.0.48 to 1.0.49 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.48 to 1.0.49. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.48...1.0.49) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 12:03:40 +03:00
version = "1.0.49"
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"
build(deps): bump cxx from 1.0.48 to 1.0.49 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.48 to 1.0.49. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.48...1.0.49) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 12:03:40 +03:00
checksum = "f9198d12d90c4a743fa06d45901ea419b81f250ad8f97635763cfaa791429ba1"
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"
build(deps): bump cxx from 1.0.48 to 1.0.49 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.48 to 1.0.49. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.48...1.0.49) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 12:03:40 +03:00
version = "1.0.49"
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"
build(deps): bump cxx from 1.0.48 to 1.0.49 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.48 to 1.0.49. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.48...1.0.49) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 12:03:40 +03:00
checksum = "63138f3cc0d24ef4c5a71e0def78e5375bd52d17a58cefc645b091c361dc7c3e"
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",
]
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
[[package]]
name = "dlv-list"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1b391911b9a786312a10cb9d2b3d0735adfd5a8113eb3648de26a75e91b0826c"
dependencies = [
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
"rand 0.7.3",
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36: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 = "dtoa"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.4.7"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "88d7ed2934d741c6b37e33e3832298e8850b53fd2d2bea03873375596c7cea4e"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "env_logger"
version = "0.8.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "17392a012ea30ef05a610aa97dfb49496e71c9f676b27879922ea5bdf60d9d3f"
dependencies = [
"atty",
"humantime",
"log",
"regex",
"termcolor",
]
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
]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "filetime"
version = "0.2.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1d34cfa13a63ae058bfa601fe9e313bbdb3746427c1459185464ce0fcf62e1e8"
dependencies = [
"cfg-if 1.0.0",
"libc",
"redox_syscall",
"winapi",
]
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "flate2"
version = "1.0.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cd3aec53de10fe96d7d8c565eb17f2c687bb5518a2ec453b5b1252964526abe0"
dependencies = [
"cfg-if 1.0.0",
"crc32fast",
"libc",
"miniz_oxide",
]
rust: Add and use fn-error-context Same motivation as https://github.com/coreos/bootupd/pull/163 Effectively what we're doing here is creating a human-readable subset of the stack trace. This is nicer than having the calling functions add with_context() because it's more verbose (gets duplicative at each call site), easy to forget, etc.
2021-03-09 22:01:35 +03:00
[[package]]
name = "fn-error-context"
build(deps): bump cxx from 1.0.45 to 1.0.46 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.45 to 1.0.46. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.45...1.0.46) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-26 13:23:55 +03:00
version = "0.1.2"
rust: Add and use fn-error-context Same motivation as https://github.com/coreos/bootupd/pull/163 Effectively what we're doing here is creating a human-readable subset of the stack trace. This is nicer than having the calling functions add with_context() because it's more verbose (gets duplicative at each call site), easy to forget, etc.
2021-03-09 22:01:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump cxx from 1.0.45 to 1.0.46 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.45 to 1.0.46. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.45...1.0.46) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-26 13:23:55 +03:00
checksum = "7dbe237cce37ed07377a50ccd977c78ee936f0f64b731caaab25ea5553b2d149"
rust: Add and use fn-error-context Same motivation as https://github.com/coreos/bootupd/pull/163 Effectively what we're doing here is creating a human-readable subset of the stack trace. This is nicer than having the calling functions add with_context() because it's more verbose (gets duplicative at each call site), easy to forget, etc.
2021-03-09 22:01:35 +03:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "foreign-types"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
dependencies = [
"foreign-types-shared 0.1.1",
]
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",
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
"foreign-types-shared 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
]
[[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
]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "foreign-types-shared"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "0e7e43a803dae2fa37c1f6a8fe121e1f7bf9548b4dfc0522a42f34145dadfc27"
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "e682a68b29a882df0545c143dc3646daefe80ba479bcdede94d5a703de2871e2"
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "0402f765d8a89a26043b889b26ce3c4679d268fa6bb22cd7c6aad98340e179d1"
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "badaa6a909fac9e7236d0620a2f57f7664640c56575b71a7552fbd68deafab79"
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "acc499defb3b348f8d8f3f66415835a9131856ff7714bf10dadfc4ec4bdb29a1"
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "a4c40298486cdf52cc00cd6d6987892ba502c7656a16a4192a9992b1ccedd121"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11: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
"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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "a57bead0ceff0d6dde8f465ecd96c9338121bb7717d3e7b108059531870c4282"
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "8a16bef9fc1a4dddb5bee51c989e3fbba26569cbb0e31f5b303c184e3dd33dae"
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.3.15"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "feb5c238d27e2bf94ffdfd27b2c29e3df4a68c4193bb6427384259e2bf191967"
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11: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
"futures-channel",
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
"pin-project-lite",
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-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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.1.16"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "8fc3cb4d91f53b50155bdcfd23f6a4c39ae1969c2ae85982b135750cccaf5fce"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +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: 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
]
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
[[package]]
name = "getrandom"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c9495705279e7140bf035dde1f6e750c162df8b625267cd52cc44e0b156732c8"
dependencies = [
"cfg-if 1.0.0",
"libc",
"wasi 0.10.0+wasi-snapshot-preview1",
]
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",
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
"system-deps 1.3.2",
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",
build(deps): bump system-deps from 2.0.3 to 3.0.0 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 2.0.3 to 3.0.0. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v2.0.3...v3.0.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-18 02:21:53 +03:00
"itertools 0.9.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
"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",
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
"system-deps 1.3.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]]
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",
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
"system-deps 1.3.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
]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "gvariant"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f7a982b6b38ff2380ea1b1b480cb7f5b51dac917aceff2e16af0c207781e13a"
dependencies = [
"gvariant-macro",
"memchr",
"ref-cast",
]
[[package]]
name = "gvariant-macro"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9915719ccd7435a28103eea8dba78bcf35a25d5637c70273b47dbb49c6d2eb6d"
dependencies = [
"syn",
]
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"
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
dependencies = [
"ahash",
]
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
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.3.2"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "87cbf45460356b7deeb5e3415b5563308c0a9b057c85e12b06ad551f98d0a6ac"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.1.18"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "322f4de77956e22ed0e5032c359a0f1273f1f7f0d79bfa3b8ffbc730d7fbcc5c"
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"
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
version = "0.4.3"
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"
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
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 Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "humantime"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
]
rust: Use indoc crate I came across this crate the other day randomly - yet *another* dtolnay dependency. We have a bunch of these inline multi-line strings that are just much nicer to read this way. I only converted this one use, if this merges I'll do more over time.
2021-03-27 22:51:59 +03:00
[[package]]
name = "indoc"
version = "1.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e5a75aeaaef0ce18b58056d306c27b07436fbb34b8816c53094b76dd81803136"
dependencies = [
"unindent",
]
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "instant"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "61124eeebbd69b8190558df225adf7e4caafce0d743919e5d6b19652314ec5ec"
dependencies = [
"cfg-if 1.0.0",
]
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
]
build(deps): bump system-deps from 2.0.3 to 3.0.0 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 2.0.3 to 3.0.0. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v2.0.3...v3.0.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-18 02:21:53 +03:00
[[package]]
name = "itertools"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "37d572918e350e82412fe766d24b15e6682fb2ed2bbe018280caa810397cb319"
dependencies = [
"either",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.4.7"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "dd25036021b0de88a0aff6b850051563c6516d0bf53f8638938edbb9de732736"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.93 to 0.2.94 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.93 to 0.2.94. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.93...0.2.94) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-28 22:34:27 +03:00
version = "0.2.94"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.93 to 0.2.94 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.93 to 0.2.94. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.93...0.2.94) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-28 22:34:27 +03:00
checksum = "18794a8ad5b29321f790b55d93dfba91e125cb1a9edbd4f8e3150acc771c1a5e"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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-sys: Explicit workspace, move libdnf deps to crate First explicitly state that we're a workspace. AIUI this is actually implicit today via our use of a `path` dependency, but in the future we may have other sub-crates. So let's make it explicit now. Also move the libdnf dependencies directly to that sub-crate.
2021-02-02 02:33:55 +03:00
"anyhow",
Move libdnf build over to Cargo This is now further migration towards Cargo/Rust possible because we switched our main binary. We've had an internal `libdnf-sys` crate for a while, but now it can take over the build of the underlying library too (like many `-sys` crates support). This itself is just an incremental step towards migrating the main rpm-ostree build system to e.g. cmake too (or perhaps directly with the `cc` crate, not sure yet) and driving it via `cargo` too.
2021-01-29 22:47:48 +03:00
"cmake",
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +03:00
"cxx",
"cxx-build",
Introduce CxxGObjectArray, use in lockfile code cxx-rs only supports a few basic types in `Vec<T>`/`CxxVector<T>` and we need to pass an array of GObjects in a few cases. Add a wrapper class hack instead of using `u64` so we at least have some basic safety here and have a convenient place to grep for later when we want to improve this.
2021-03-02 21:20:22 +03:00
"glib",
build(deps): bump system-deps from 3.1.0 to 3.1.1 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v3.1.0...v3.1.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-31 23:44:51 +03:00
"system-deps 3.1.1",
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "1.0.5"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "8f1becd27d473556dc610b8afa1636ef90747b574a84553bc11e82371d5ef2d1"
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",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.5.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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "7fb9b38af92608140b86b693604b9ffcc5824240a484d1ecd4795bacb2fe88f3"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "lock_api"
version = "0.4.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0382880606dff6d15c9476c416d18690b72742aa7b605bb6dd6ec9030fbf07eb"
dependencies = [
"scopeguard",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.4.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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "fcf3805d4480bb5b86070dcfeb9e2cb2ebc148adb753c5cca5f884d1d65a42b2"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
]
cargo: add maplit
2021-03-01 18:22:36 +03:00
[[package]]
name = "maplit"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3e2e65a1a2e43cfcb47a895c4c8b10d1f4a61097f9f254f183aee60cad9c651d"
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "matchers"
version = "0.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f099785f7595cc4b4553a174ce30dd7589ef93391ff414dbb67f62392b9e0ce1"
dependencies = [
"regex-automata",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump memfd from 0.3.0 to 0.4.0 Bumps [memfd](https://github.com/lucab/memfd-rs) from 0.3.0 to 0.4.0. - [Release notes](https://github.com/lucab/memfd-rs/releases) - [Commits](https://github.com/lucab/memfd-rs/compare/v0.3.0...v0.4.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-17 03:31:25 +03:00
version = "0.4.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump memfd from 0.3.0 to 0.4.0 Bumps [memfd](https://github.com/lucab/memfd-rs) from 0.3.0 to 0.4.0. - [Release notes](https://github.com/lucab/memfd-rs/releases) - [Commits](https://github.com/lucab/memfd-rs/compare/v0.3.0...v0.4.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-17 03:31:25 +03:00
checksum = "d9d93fa0e6de9bf1ec418e4784cdc59062d21e77e940a3beab4323fcc4655c31"
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
dependencies = [
"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
[[package]]
name = "memoffset"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "157b4208e3059a8f9e78d559edc658e13df41410cb3ae03979c83130067fdd87"
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
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "miniz_oxide"
version = "0.4.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a92518e98c078586bc6c934028adcca4c92a53d6a958196de835170a01d84e4b"
dependencies = [
"adler",
"autocfg",
]
[[package]]
name = "mio"
version = "0.7.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cf80d3e903b34e0bd7282b218398aec54e082c840d9baf8339e0080a0c542956"
dependencies = [
"libc",
"log",
"miow",
"ntapi",
"winapi",
]
[[package]]
name = "miow"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9f1c5b025cda876f66ef43a113f91ebc9f4ccef34843000e0adf6ebbab84e21"
dependencies = [
"winapi",
]
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.1 to 0.20.0 Bumps [nix](https://github.com/nix-rust/nix) from 0.19.1 to 0.20.0. - [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/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-22 17:20:48 +03:00
version = "0.20.0"
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.1 to 0.20.0 Bumps [nix](https://github.com/nix-rust/nix) from 0.19.1 to 0.20.0. - [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/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-22 17:20:48 +03:00
checksum = "fa9b4819da1bc61c0ea48b63b7bc8604064dd43013e7cc325df098d49cd7c18a"
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
]
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "ntapi"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f6bb902e437b6d86e03cce10a7e2af662292c5dfef23b65899ea3ac9354ad44"
dependencies = [
"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
[[package]]
name = "num-integer"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "d2cc698a63b549a70bc047073d2949cce27cd1c7b0a4a862d08a8031bc2801db"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.2.14"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "9a64b1ec5cda2586e284722486d802acf1f7dbdc623e2bfc57e65ca1cd099290"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "1.5.2"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "13bd41f508810a131401606d54ac32a467c97172d74ba7662562ebba5ad07fa0"
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.20 to 0.1.21 Bumps [openat](https://github.com/tailhook/openat) from 0.1.20 to 0.1.21. - [Release notes](https://github.com/tailhook/openat/releases) - [Commits](https://github.com/tailhook/openat/compare/v0.1.20...v0.1.21) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-19 13:14:18 +03:00
version = "0.1.21"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 openat from 0.1.20 to 0.1.21 Bumps [openat](https://github.com/tailhook/openat) from 0.1.20 to 0.1.21. - [Release notes](https://github.com/tailhook/openat/releases) - [Commits](https://github.com/tailhook/openat/compare/v0.1.20...v0.1.21) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-19 13:14:18 +03:00
checksum = "95aa7c05907b3ebde2610d602f4ddd992145cc6a84493647c30396f30ba83abe"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.2.0 to 0.2.1 Bumps [openat-ext](https://github.com/coreos/openat-ext) from 0.2.0 to 0.2.1. - [Release notes](https://github.com/coreos/openat-ext/releases) - [Commits](https://github.com/coreos/openat-ext/compare/v0.2.0...v0.2.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-29 10:12:31 +03:00
version = "0.2.1"
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.2.0 to 0.2.1 Bumps [openat-ext](https://github.com/coreos/openat-ext) from 0.2.0 to 0.2.1. - [Release notes](https://github.com/coreos/openat-ext/releases) - [Commits](https://github.com/coreos/openat-ext/compare/v0.2.0...v0.2.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-29 10:12:31 +03:00
checksum = "64d8c39f87cebbf893a221d307e578da316157c6c65aa1c1518c573be0cd8c11"
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 = [
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",
build(deps): bump openat-ext from 0.2.0 to 0.2.1 Bumps [openat-ext](https://github.com/coreos/openat-ext) from 0.2.0 to 0.2.1. - [Release notes](https://github.com/coreos/openat-ext/releases) - [Commits](https://github.com/coreos/openat-ext/compare/v0.2.0...v0.2.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-29 10:12:31 +03:00
"nix",
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",
build(deps): bump openat-ext from 0.2.0 to 0.2.1 Bumps [openat-ext](https://github.com/coreos/openat-ext) from 0.2.0 to 0.2.1. - [Release notes](https://github.com/coreos/openat-ext/releases) - [Commits](https://github.com/coreos/openat-ext/compare/v0.2.0...v0.2.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-29 10:12:31 +03:00
"rand 0.8.3",
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
]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "openssl"
version = "0.10.33"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a61075b62a23fef5a29815de7536d940aa35ce96d18ce0cc5076272db678a577"
dependencies = [
"bitflags",
"cfg-if 1.0.0",
"foreign-types 0.3.2",
"libc",
"once_cell",
"openssl-sys",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
version = "0.9.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"
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
checksum = "313752393519e876837e09e1fa183ddef0be7735868dced3196f4472d536277f"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
]
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
[[package]]
name = "ordered-multimap"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1c672c7ad9ec066e428c00eb917124a06f08db19e2584de982cc34b1f4c12485"
dependencies = [
"dlv-list",
"hashbrown",
]
[[package]]
name = "os-release"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "82f29ae2f71b53ec19cc23385f8e4f3d90975195aa3d09171ba3bef7159bec27"
dependencies = [
"lazy_static",
]
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"
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
version = "0.11.0"
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"
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
checksum = "84c424e3b6d40b39383b07e39b4e7972738a9250080e0cb416967023e565ebb1"
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
]
rust: Factor out an ostree-host crate In preparation for publishing this to crates.io and moving into e.g. github.com/ostreedev/ostree-host-rs So that ostree upstream can move forward with more Rust on the "top level".
2021-03-19 15:58:03 +03:00
[[package]]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
name = "ostree-ext"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.1.2"
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "ec01cc74ccf8d3b3ed81f0006cf984f0ab859959e56509fafe6bc2ed4d896c84"
rust: Factor out an ostree-host crate In preparation for publishing this to crates.io and moving into e.g. github.com/ostreedev/ostree-host-rs So that ostree upstream can move forward with more Rust on the "top level".
2021-03-19 15:58:03 +03:00
dependencies = [
"anyhow",
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
"bytes",
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
"camino",
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
"cjson",
"flate2",
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
"fn-error-context",
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
"futures",
rust: Factor out an ostree-host crate In preparation for publishing this to crates.io and moving into e.g. github.com/ostreedev/ostree-host-rs So that ostree upstream can move forward with more Rust on the "top level".
2021-03-19 15:58:03 +03:00
"gio",
"glib",
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
"glib-sys",
"gvariant",
"hex",
"libc",
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
"nix",
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
"openat",
"openat-ext",
"openssl",
rust: Factor out an ostree-host crate In preparation for publishing this to crates.io and moving into e.g. github.com/ostreedev/ostree-host-rs So that ostree upstream can move forward with more Rust on the "top level".
2021-03-19 15:58:03 +03:00
"ostree",
"ostree-sys",
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
"phf",
"serde",
"serde_json",
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
"tar",
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
"tempfile",
"tokio",
"tokio-stream",
"tokio-util",
"tracing",
rust: Factor out an ostree-host crate In preparation for publishing this to crates.io and moving into e.g. github.com/ostreedev/ostree-host-rs So that ostree upstream can move forward with more Rust on the "top level".
2021-03-19 15:58:03 +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-sys"
build(deps): bump ostree-sys from 0.7.2 to 0.7.3 Bumps [ostree-sys](https://gitlab.com/fkrull/ostree-rs) from 0.7.2 to 0.7.3. - [Release notes](https://gitlab.com/fkrull/ostree-rs/tags) - [Commits](https://gitlab.com/fkrull/ostree-rs/commits/master) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-19 13:15:38 +03:00
version = "0.7.3"
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 ostree-sys from 0.7.2 to 0.7.3 Bumps [ostree-sys](https://gitlab.com/fkrull/ostree-rs) from 0.7.2 to 0.7.3. - [Release notes](https://gitlab.com/fkrull/ostree-rs/tags) - [Commits](https://gitlab.com/fkrull/ostree-rs/commits/master) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-19 13:15:38 +03:00
checksum = "2d9ea917750072931dd9c57e536f5c36422060603bd7e755beb74bf7be797564"
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",
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
"system-deps 1.3.2",
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 curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "parking_lot"
version = "0.11.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d7744ac029df22dca6284efe4e898991d28e3085c706c972bcd7da4a27a15eb"
dependencies = [
"instant",
"lock_api",
"parking_lot_core",
]
[[package]]
name = "parking_lot_core"
version = "0.8.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa7a782938e745763fe6907fc6ba86946d72f49fe7e21de074e08128a99fb018"
dependencies = [
"cfg-if 1.0.0",
"instant",
"libc",
"redox_syscall",
"smallvec",
"winapi",
]
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"
build(deps): bump paste from 1.0.4 to 1.0.5 Bumps [paste](https://github.com/dtolnay/paste) from 1.0.4 to 1.0.5. - [Release notes](https://github.com/dtolnay/paste/releases) - [Commits](https://github.com/dtolnay/paste/compare/1.0.4...1.0.5) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-15 09:51:41 +03:00
version = "1.0.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump paste from 1.0.4 to 1.0.5 Bumps [paste](https://github.com/dtolnay/paste) from 1.0.4 to 1.0.5. - [Release notes](https://github.com/dtolnay/paste/releases) - [Commits](https://github.com/dtolnay/paste/compare/1.0.4...1.0.5) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-15 09:51:41 +03:00
checksum = "acbf547ad0c65e31259204bd90935776d1c693cec2f4ff7abb7a1bbbd40dfe58"
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
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",
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
"rand 0.7.3",
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_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]]
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
name = "pin-project-lite"
version = "0.2.4"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "439697af366c49a6d0a010c56a0d97685bc140ce0d377b13a2ea2aa42d64a827"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "ac74c624d6b2d21f425f752262f42188365d7b8ff1aff74c82e45136510a4857"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.5.19"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "dbf0c48bc1d91375ae5c3cd81e3722dff1abcf81a30960240640d223f59fe0e5"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.1.7"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "bc881b2c22681370c6a780e47af9840ef841837bc98118431d4e1868bd0c1086"
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"
build(deps): bump cxx-build from 1.0.41 to 1.0.42 Bumps [cxx-build](https://github.com/dtolnay/cxx) from 1.0.41 to 1.0.42. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.41...1.0.42) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-05 09:57:50 +03:00
version = "1.0.26"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 cxx-build from 1.0.41 to 1.0.42 Bumps [cxx-build](https://github.com/dtolnay/cxx) from 1.0.41 to 1.0.42. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.41...1.0.42) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-05 09:57:50 +03:00
checksum = "a152013215dca273577e18d2bf00fa862b89b24169fb78c4c95aeb07992c9cec"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "1.0.8"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "991431c3519a3f36861882da93630ce66b52918dcf1b8e2fd66b397fc96f28df"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
"getrandom 0.1.16",
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",
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
"rand_chacha 0.2.2",
"rand_core 0.5.1",
"rand_hc 0.2.0",
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
]
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
[[package]]
name = "rand"
build(deps): bump rand from 0.8.2 to 0.8.3 Bumps [rand](https://github.com/rust-random/rand) from 0.8.2 to 0.8.3. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-26 13:34:13 +03:00
version = "0.8.3"
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rand from 0.8.2 to 0.8.3 Bumps [rand](https://github.com/rust-random/rand) from 0.8.2 to 0.8.3. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-26 13:34:13 +03:00
checksum = "0ef9e7e66b4468674bfcb0c81af8b7fa0bb154fa9f28eb840da5c447baeb8d7e"
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
dependencies = [
"libc",
"rand_chacha 0.3.0",
"rand_core 0.6.1",
"rand_hc 0.3.0",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
[[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 tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
"rand_core 0.5.1",
]
[[package]]
name = "rand_chacha"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e12735cf05c9e10bf21534da50a147b924d555dc7a547c42e6bb2d5b6017ae0d"
dependencies = [
"ppv-lite86",
"rand_core 0.6.1",
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
"getrandom 0.1.16",
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
]
[[package]]
name = "rand_core"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c026d7df8b298d90ccbbc5190bd04d85e159eaf5576caeacf8741da93ccbd2e5"
dependencies = [
"getrandom 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
]
[[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 tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
"rand_core 0.5.1",
]
[[package]]
name = "rand_hc"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3190ef7066a446f2e7f42e239d161e905420ccab01eb967c9eb27d21b2322a73"
dependencies = [
"rand_core 0.6.1",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
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 = [
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
"rand_core 0.5.1",
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
]
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.5.0 to 1.5.1 Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.5.0 to 1.5.1. - [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.5.0...v1.5.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-24 09:14:55 +03:00
version = "1.5.1"
Add rayon dependency, do postprocessing in parallel Obviously doing these trivial functions in parallel doesn't matter, but I wanted to dip my toes into Rayon (and Rust parallelism in general). `try_for_each()` is just...staggeringly simple and beautiful. Closes: #1727 Approved by: jlebon
2019-01-07 20:49:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rayon from 1.5.0 to 1.5.1 Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.5.0 to 1.5.1. - [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.5.0...v1.5.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-24 09:14:55 +03:00
checksum = "c06aca804d41dbc8ba42dfd964f0d01334eceb64314b9ecf7c5fad5188a06d90"
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.5.0 to 1.5.1 Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.5.0 to 1.5.1. - [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.5.0...v1.5.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-24 09:14:55 +03:00
version = "1.9.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"
build(deps): bump rayon from 1.5.0 to 1.5.1 Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.5.0 to 1.5.1. - [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.5.0...v1.5.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-24 09:14:55 +03:00
checksum = "d78120e2c850279833f1dd3582f730c4ab53ed95aeaaaa862a2a5c71b1656d8e"
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
]
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
[[package]]
name = "redox_syscall"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "05ec8ca9416c5ea37062b502703cd7fcb207736bc294f6e0cf367ac6fc234570"
dependencies = [
"bitflags",
]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "ref-cast"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "300f2a835d808734ee295d45007adacb9ebb29dd3ae2424acfa17930cae541da"
dependencies = [
"ref-cast-impl",
]
[[package]]
name = "ref-cast-impl"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4c38e3aecd2b21cb3959637b883bb3714bc7e43f0268b9a29d3743ee3e55cdd2"
dependencies = [
"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 = "regex"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "1.4.3"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "d9251239e129e16308e70d853559389de218ac275b515068abc96829d05b948a"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 = [
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
"aho-corasick",
"memchr",
"regex-syntax",
"thread_local",
]
[[package]]
name = "regex-automata"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ae1ded71d66a4a97f5e961fd0cb25a5f366a42a41570d16a763a69c092c26ae4"
dependencies = [
"byteorder",
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.6.22"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "b5eb417147ba9860a96cfe72a0b93bf88fee1744b5636ec99ab20c1aa9376581"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
]
Add an rpmostree-client sub-crate This is intended to be published to https://crates.io/crates/rpmostree-client Part of https://github.com/coreos/rpm-ostree/issues/2389 This directly imports the code from https://github.com/ostreedev/ostree/blob/5551c54c6e6eba8145b95bd3b28223f1941a9e8d/tests/inst/src/rpmostree.rs Once merged and released I'll try converting the ostree test suite over as well as Zincati. Internally add a testutils helper to validate it works.
2021-02-12 21:47:36 +03:00
[[package]]
name = "rpmostree-client"
version = "0.1.0"
dependencies = [
"anyhow",
"serde",
"serde_derive",
"serde_json",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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",
Add and use the `camino` library for UTF-8 paths ostree hard requires UTF-8 paths (and really we should never have any non-UTF-8 paths in the OS in general). The camino library has types that are both `Path` and `&str` and has a convenient `try_into()` too to avoid us duplicating the error handling.
2021-04-30 16:56:05 +03:00
"camino",
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",
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
"env_logger",
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",
rust: Add and use fn-error-context Same motivation as https://github.com/coreos/bootupd/pull/163 Effectively what we're doing here is creating a human-readable subset of the stack trace. This is nicer than having the calling functions add with_context() because it's more verbose (gets duplicative at each call site), easy to forget, etc.
2021-03-09 22:01:35 +03:00
"fn-error-context",
Update to ostree-ext v0.1.2, add new `ex-container` command This new `rpm-ostree ex-container` CLI is just code copied from the `ostree-ext-cli container` binary code. In the future I may just add the CLI code as a library API too to simplify this. For now, I don't want to try to add a new Rust CLI as an RPM package for example. This exposes it via rpm-ostree, and in the future rpm-ostree may have some layering on top of this anyways.
2021-05-12 00:57:43 +03:00
"futures",
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",
"gio-sys",
"glib",
"glib-sys",
Introduce CxxGObjectArray, use in lockfile code cxx-rs only supports a few basic types in `Vec<T>`/`CxxVector<T>` and we need to pass an array of GObjects in a few cases. Add a wrapper class hack instead of using `u64` so we at least have some basic safety here and have a convenient place to grep for later when we want to improve this.
2021-03-02 21:20:22 +03:00
"gobject-sys",
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
"indicatif",
rust: Use indoc crate I came across this crate the other day randomly - yet *another* dtolnay dependency. We have a bunch of these inline multi-line strings that are just much nicer to read this way. I only converted this one use, if this merges I'll do more over time.
2021-03-27 22:51:59 +03:00
"indoc",
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",
"libc",
"libdnf-sys",
cargo: add maplit
2021-03-01 18:22:36 +03:00
"maplit",
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 openat-ext from 0.2.0 to 0.2.1 Bumps [openat-ext](https://github.com/coreos/openat-ext) from 0.2.0 to 0.2.1. - [Release notes](https://github.com/coreos/openat-ext/releases) - [Commits](https://github.com/coreos/openat-ext/compare/v0.2.0...v0.2.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-29 10:12:31 +03:00
"nix",
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",
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
"os-release",
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
"ostree",
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
"ostree-ext",
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
"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 rand from 0.8.2 to 0.8.3 Bumps [rand](https://github.com/rust-random/rand) from 0.8.2 to 0.8.3. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-26 13:34:13 +03:00
"rand 0.8.3",
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
"rayon",
Add an rpmostree-client sub-crate This is intended to be published to https://crates.io/crates/rpmostree-client Part of https://github.com/coreos/rpm-ostree/issues/2389 This directly imports the code from https://github.com/ostreedev/ostree/blob/5551c54c6e6eba8145b95bd3b28223f1941a9e8d/tests/inst/src/rpmostree.rs Once merged and released I'll try converting the ostree test suite over as well as Zincati. Internally add a testutils helper to validate it works.
2021-02-12 21:47:36 +03:00
"rpmostree-client",
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
"rust-ini",
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",
"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 system-deps from 3.1.0 to 3.1.1 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v3.1.0...v3.1.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-31 23:44:51 +03:00
"system-deps 3.1.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
"systemd",
"tempfile",
Update to ostree-ext v0.1.2, add new `ex-container` command This new `rpm-ostree ex-container` CLI is just code copied from the `ostree-ext-cli container` binary code. In the future I may just add the CLI code as a library API too to simplify this. For now, I don't want to try to add a new Rust CLI as an RPM package for example. This exposes it via rpm-ostree, and in the future rpm-ostree may have some layering on top of this anyways.
2021-05-12 00:57:43 +03:00
"tokio",
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
"tracing",
"tracing-subscriber",
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
]
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
[[package]]
name = "rust-ini"
build(deps): bump rust-ini from 0.16.1 to 0.17.0 Bumps [rust-ini](https://github.com/zonyitoo/rust-ini) from 0.16.1 to 0.17.0. - [Release notes](https://github.com/zonyitoo/rust-ini/releases) - [Commits](https://github.com/zonyitoo/rust-ini/compare/v0.16.1...v0.17.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-30 15:39:33 +03:00
version = "0.17.0"
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rust-ini from 0.16.1 to 0.17.0 Bumps [rust-ini](https://github.com/zonyitoo/rust-ini) from 0.16.1 to 0.17.0. - [Release notes](https://github.com/zonyitoo/rust-ini/releases) - [Commits](https://github.com/zonyitoo/rust-ini/compare/v0.16.1...v0.17.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-30 15:39:33 +03:00
checksum = "63471c4aa97a1cf8332a5f97709a79a4234698de6a1f5087faf66f2dae810e22"
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
dependencies = [
build(deps): bump rust-ini from 0.16.1 to 0.17.0 Bumps [rust-ini](https://github.com/zonyitoo/rust-ini) from 0.16.1 to 0.17.0. - [Release notes](https://github.com/zonyitoo/rust-ini/releases) - [Commits](https://github.com/zonyitoo/rust-ini/compare/v0.16.1...v0.17.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-30 15:39:33 +03:00
"cfg-if 1.0.0",
Cargo.lock: Update for DNF Count Me support
2021-01-06 18:36:44 +03:00
"ordered-multimap",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +03:00
[[package]]
name = "scratch"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7e114536316b51a5aa7a0e59fc49661fd263c5507dd08bd28de052e57626ce69"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.125 to 1.0.126 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.125 to 1.0.126. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.125...v1.0.126) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 14:15:08 +03:00
version = "1.0.126"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.125 to 1.0.126 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.125 to 1.0.126. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.125...v1.0.126) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 14:15:08 +03:00
checksum = "ec7505abeacaec74ae4778d9d9328fe5a5d04253220a85c4ee022239fc996d03"
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 from 1.0.125 to 1.0.126 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.125 to 1.0.126. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.125...v1.0.126) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 14:15:08 +03:00
version = "1.0.126"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.125 to 1.0.126 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.125 to 1.0.126. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.125...v1.0.126) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 14:15:08 +03:00
checksum = "963a7dbc9895aeac7ac90e74f34a5d5261828f79df35cbed41e10189d3804d43"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.62 to 1.0.64 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.62 to 1.0.64. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.62...v1.0.64) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-01 10:03:14 +03:00
version = "1.0.64"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.62 to 1.0.64 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.62 to 1.0.64. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.62...v1.0.64) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-01 10:03:14 +03:00
checksum = "799e97dc9fdae36a5c8b8f2cae9ce2ee9fdce2058c57a93e6099d919fd982f79"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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.16 to 0.8.17 Bumps [serde_yaml](https://github.com/dtolnay/serde-yaml) from 0.8.16 to 0.8.17. - [Release notes](https://github.com/dtolnay/serde-yaml/releases) - [Commits](https://github.com/dtolnay/serde-yaml/compare/0.8.16...0.8.17) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-22 23:34:52 +03:00
version = "0.8.17"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_yaml from 0.8.16 to 0.8.17 Bumps [serde_yaml](https://github.com/dtolnay/serde-yaml) from 0.8.16 to 0.8.17. - [Release notes](https://github.com/dtolnay/serde-yaml/releases) - [Commits](https://github.com/dtolnay/serde-yaml/compare/0.8.16...0.8.17) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-22 23:34:52 +03:00
checksum = "15654ed4ab61726bf918a39cb8d98a2e2995b002387807fa6ba58fdf7f59bb23"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
]
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "sharded-slab"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "79c719719ee05df97490f80a45acfc99e5a30ce98a1e4fb67aee422745ae14e3"
dependencies = [
"lazy_static",
]
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "signal-hook-registry"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "16f1d0fef1604ba8f7a073c7e701f213e056707210e9020af4528e0101ce11a6"
dependencies = [
"libc",
]
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
build(deps): bump system-deps from 3.0.0 to 3.1.0 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 3.0.0 to 3.1.0. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v3.0.0...v3.1.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 20:01:31 +03:00
[[package]]
name = "smallvec"
version = "1.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fe0f37c9e8f3c5a4a66ad655a93c74daac4ad00c441533bf5c6e7990bb42604e"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump curl from 0.4.35 to 0.4.36 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.35 to 0.4.36. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.35...curl-sys-0.4.36) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-19 15:29:29 +03:00
version = "0.4.0"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump curl from 0.4.35 to 0.4.36 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.35 to 0.4.36. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.35...curl-sys-0.4.36) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-19 15:29:29 +03:00
checksum = "9e3dfc207c526015c632472a77be09cf1b6e46866581aecae5cc38fb4235dea2"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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",
"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
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
[[package]]
name = "strum"
version = "0.20.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7318c509b5ba57f18533982607f24070a55d353e90d4cae30c467cdb2ad5ac5c"
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
]
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
[[package]]
name = "strum_macros"
version = "0.20.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ee8bc6b87a5112aeeab1f4a9f7ab634fe6cbefc4850006df31267f4cfb9e3149"
dependencies = [
"heck",
"proc-macro2",
"quote",
"syn",
]
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"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
version = "0.2.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
checksum = "334b801f9ca2529ba9605109f1d2835f15aff94cd6cfe5afe6ce8cf71e5fd3c4"
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
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"
build(deps): bump cxx from 1.0.46 to 1.0.47 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.46 to 1.0.47. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.46...1.0.47) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-28 22:34:23 +03:00
version = "1.0.71"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 cxx from 1.0.46 to 1.0.47 Bumps [cxx](https://github.com/dtolnay/cxx) from 1.0.46 to 1.0.47. - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](https://github.com/dtolnay/cxx/compare/1.0.46...1.0.47) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-28 22:34:23 +03:00
checksum = "ad184cc9470f9117b2ac6817bfe297307418819ba40552f9b3846f05c33d5373"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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",
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
"strum 0.18.0",
"strum_macros 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
"thiserror",
"toml",
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
"version-compare 0.0.10",
]
[[package]]
name = "system-deps"
build(deps): bump system-deps from 3.1.0 to 3.1.1 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v3.1.0...v3.1.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-31 23:44:51 +03:00
version = "3.1.1"
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump system-deps from 3.1.0 to 3.1.1 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v3.1.0...v3.1.1) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-31 23:44:51 +03:00
checksum = "c248107ad7bc1ac07066a4d003cae9e9a7bc2e27d3418f7a9cdcdc8699dbea70"
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
dependencies = [
build(deps): bump system-deps from 2.0.3 to 3.0.0 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 2.0.3 to 3.0.0. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v2.0.3...v3.0.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-18 02:21:53 +03:00
"anyhow",
build(deps): bump system-deps from 3.0.0 to 3.1.0 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 3.0.0 to 3.1.0. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v3.0.0...v3.1.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 20:01:31 +03:00
"cfg-expr",
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
"heck",
build(deps): bump system-deps from 2.0.3 to 3.0.0 Bumps [system-deps](https://github.com/gdesmott/system-deps) from 2.0.3 to 3.0.0. - [Release notes](https://github.com/gdesmott/system-deps/releases) - [Commits](https://github.com/gdesmott/system-deps/compare/v2.0.3...v3.0.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-02-18 02:21:53 +03:00
"itertools 0.10.0",
rust: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
"pkg-config",
"strum 0.20.0",
"strum_macros 0.20.1",
"thiserror",
"toml",
"version-compare 0.0.11",
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.8.1 to 0.8.2 Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.8.1 to 0.8.2. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.8.1...systemd-0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 14:42:11 +03:00
version = "0.8.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"
build(deps): bump systemd from 0.8.1 to 0.8.2 Bumps [systemd](https://github.com/jmesmon/rust-systemd) from 0.8.1 to 0.8.2. - [Release notes](https://github.com/jmesmon/rust-systemd/releases) - [Commits](https://github.com/jmesmon/rust-systemd/compare/systemd-0.8.1...systemd-0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 14:42:11 +03:00
checksum = "f722cabda922e471742300045f56dbaa53fafbb4520fca304e51258019bfe91d"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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",
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
"foreign-types 0.5.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",
"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
]
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "tar"
version = "0.4.33"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0bcfbd6a598361fda270d82469fff3d65089dc33e175c9a131f7b4cd395f228"
dependencies = [
"filetime",
"libc",
"xattr",
]
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
version = "3.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 tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +03:00
checksum = "dac1c663cfc93810f88aed9b8941d48cabf856a1b111c29a40439018d870eb22"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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 tempfile from 3.1.0 to 3.2.0 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.1.0 to 3.2.0. - [Release notes](https://github.com/Stebalien/tempfile/releases) - [Changelog](https://github.com/Stebalien/tempfile/blob/master/NEWS) - [Commits](https://github.com/Stebalien/tempfile/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 16:50:45 +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",
build(deps): bump rand from 0.8.2 to 0.8.3 Bumps [rand](https://github.com/rust-random/rand) from 0.8.2 to 0.8.3. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-26 13:34:13 +03:00
"rand 0.8.3",
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
"redox_syscall",
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
"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
]
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +03:00
[[package]]
name = "termcolor"
version = "1.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2dfed899f0eb03f32ee8c6a0aabdb8a7949659e3466561fc0adf54e26d88c5f4"
dependencies = [
"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
[[package]]
rust: Update deps ``` $ cargo upgrade $ cargo update ```
2020-10-19 17:58:26 +03:00
name = "terminal_size"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.1.16"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "86ca8ced750734db02076f44132d802af0b33b09942331f4459dde8636fd2406"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "1.0.23"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "76cc616c6abf8c8928e2fdcc0dbfab37175edd8fb49a4641066ad1364fdab146"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "1.0.23"
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "9be73a2caec27583d0046ef3796c3794f868a5bc813db689eed00c7631275cd1"
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
]
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "thread_local"
version = "1.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8018d24e04c95ac8790716a5987d0fec4f8b27249ffa0f7d33f1369bdfb88cbd"
dependencies = [
"once_cell",
]
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
]
build(deps): bump curl from 0.4.36 to 0.4.37 Bumps [curl](https://github.com/alexcrichton/curl-rust) from 0.4.36 to 0.4.37. - [Release notes](https://github.com/alexcrichton/curl-rust/releases) - [Commits](https://github.com/alexcrichton/curl-rust/compare/curl-sys-0.4.36...curl-sys-0.4.37) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 11:11:26 +03:00
[[package]]
name = "tokio"
version = "1.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bd3076b5c8cc18138b8f8814895c11eb4de37114a5d127bafdc5e55798ceef37"
dependencies = [
"autocfg",
"bytes",
"libc",
"memchr",
"mio",
"num_cpus",
"once_cell",
"parking_lot",
"pin-project-lite",
"signal-hook-registry",
"tokio-macros",
"winapi",
]
[[package]]
name = "tokio-macros"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c49e3df43841dafb86046472506755d8501c5615673955f6aa17181125d13c37"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
[[package]]
name = "tokio-stream"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f8864d706fdb3cc0843a49647ac892720dac98a6eeb818b77190592cf4994066"
dependencies = [
"futures-core",
"pin-project-lite",
"tokio",
]
[[package]]
name = "tokio-util"
version = "0.6.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1caa0b0c8d94a049db56b5acf8cba99dc0623aab1b26d5b5f5e2d945846b3592"
dependencies = [
"bytes",
"futures-core",
"futures-sink",
"log",
"pin-project-lite",
"tokio",
]
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.5.8"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "a31142970826733df8241ef35dc040ef98c679ab14d7c3e54d827099b3acecaa"
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 Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
[[package]]
name = "tracing"
build(deps): bump tracing from 0.1.25 to 0.1.26 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.25 to 0.1.26. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.25...tracing-0.1.26) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 15:55:18 +03:00
version = "0.1.26"
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump tracing from 0.1.25 to 0.1.26 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.25 to 0.1.26. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.25...tracing-0.1.26) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 15:55:18 +03:00
checksum = "09adeb8c97449311ccd28a427f96fb563e7fd31aabf994189879d9da2394b89d"
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
dependencies = [
"cfg-if 1.0.0",
"pin-project-lite",
"tracing-attributes",
"tracing-core",
]
[[package]]
name = "tracing-attributes"
version = "0.1.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c42e6fa53307c8a17e4ccd4dc81cf5ec38db9209f59b222210375b54ee40d1e2"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
[[package]]
name = "tracing-core"
build(deps): bump tracing from 0.1.25 to 0.1.26 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.25 to 0.1.26. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.25...tracing-0.1.26) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 15:55:18 +03:00
version = "0.1.18"
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump tracing from 0.1.25 to 0.1.26 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.25 to 0.1.26. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.25...tracing-0.1.26) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 15:55:18 +03:00
checksum = "a9ff14f98b1a4b289c6248a023c1c2fa1491062964e9fed67ab29c4e4da4a052"
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
dependencies = [
"lazy_static",
]
[[package]]
name = "tracing-log"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a6923477a48e41c1951f1999ef8bb5a3023eb723ceadafe78ffb65dc366761e3"
dependencies = [
"lazy_static",
"log",
"tracing-core",
]
[[package]]
name = "tracing-serde"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fb65ea441fbb84f9f6748fd496cf7f63ec9af5bca94dd86456978d055e8eb28b"
dependencies = [
"serde",
"tracing-core",
]
[[package]]
name = "tracing-subscriber"
build(deps): bump tracing-subscriber from 0.2.17 to 0.2.18 Bumps [tracing-subscriber](https://github.com/tokio-rs/tracing) from 0.2.17 to 0.2.18. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.2.17...tracing-subscriber-0.2.18) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 13:54:53 +03:00
version = "0.2.18"
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump tracing-subscriber from 0.2.17 to 0.2.18 Bumps [tracing-subscriber](https://github.com/tokio-rs/tracing) from 0.2.17 to 0.2.18. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.2.17...tracing-subscriber-0.2.18) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-06 13:54:53 +03:00
checksum = "aa5553bf0883ba7c9cbe493b085c29926bd41b66afc31ff72cf17ff4fb60dcd5"
Add Rust tracing crate usage Related to https://github.com/ostreedev/ostree-rs-ext/pull/21 And inspired by seeing some discussion around the https://crates.io/crates/tracing crate.
2021-04-27 21:48:25 +03:00
dependencies = [
"ansi_term 0.12.1",
"chrono",
"lazy_static",
"matchers",
"regex",
"serde",
"serde_json",
"sharded-slab",
"smallvec",
"thread_local",
"tracing",
"tracing-core",
"tracing-log",
"tracing-serde",
]
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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "1.7.1"
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 rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "bb0d2e7be6ae3a5fa87eed5fb451aff96f2573d2694942e40543ae0bbe19c796"
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
rust: Use indoc crate I came across this crate the other day randomly - yet *another* dtolnay dependency. We have a bunch of these inline multi-line strings that are just much nicer to read this way. I only converted this one use, if this merges I'll do more over time.
2021-03-27 22:51:59 +03:00
[[package]]
name = "unindent"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f14ee04d9415b52b3aeab06258a3f07093182b88ba0f9b8d203f211a7a7d41c7"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
version = "0.2.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"
build(deps): bump rand from 0.7.3 to 0.8.2 Bumps [rand](https://github.com/rust-random/rand) from 0.7.3 to 0.8.2. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.7.3...0.8.2) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-20 17:33:07 +03:00
checksum = "b00bca6106a5e23f3eee943593759b7fcddb00554332e856d990c893966879fb"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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: Link to our C/C++ dependencies and internal library This allows us to fully use cxx-rs with `extern "C++"`. Now we do call back into the C/C++ today, but it only works outside of cargo/Rust's knowledge. Most notably, it means we can't use our C code in `cargo test`. And that's a problem for moving some C/C++ code to Rust, because we want to port the unit tests too. For now, re-declare our dependencies and part of the build system inside the Cargo build. However, this is also an important step towards using Cargo as our *sole* build system. We don't add build dependencies too often, so the short term duplication should be OK. However, a major unfortunate side effect of this is that we now need to serialize the build process; almost all the C/C++ comes first (`librpmostreeinternals.la`) and then the Rust build, then we finally generate the executable with both. The only way out of this really is to move more of the C/C++ build into Cargo, and we probably want to refactor into internal crates.
2021-01-23 18:32:05 +03:00
[[package]]
name = "version-compare"
version = "0.0.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1c18c859eead79d8b95d09e4678566e8d70105c4e7b251f707a03df32442661b"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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
libdnf-sys: Drop C API, replace with cxx.rs bridge Right now, we're using libdnf APIs from Rust via hand-crafted `extern C` interfaces, which is extra dangerous because there is no signature checking that happens at compile-time. Until either we can automate libdnf bindings or use its C++ API directly via cxx.rs, let's do some basic wrapping in C++ ourselves and use libdnf through that API only instead. That gives us a lot more confidence and makes the libdnf API feel more natural to use in Rust.
2021-02-10 02:07:37 +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
Require ostree v2021.2, use ostree-ext crate This uses the ostree and ostree-ext crates from git as a demo/WIP for https://mail.gnome.org/archives/ostree-list/2021-April/msg00000.html
2021-04-05 23:15:54 +03:00
[[package]]
name = "xattr"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "244c3741f4240ef46274860397c7c74e50eb23624996930e484c16679633a54c"
dependencies = [
"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
[[package]]
name = "yaml-rust"
build(deps): bump serde_yaml from 0.8.14 to 0.8.15 Bumps [serde_yaml](https://github.com/dtolnay/serde-yaml) from 0.8.14 to 0.8.15. - [Release notes](https://github.com/dtolnay/serde-yaml/releases) - [Commits](https://github.com/dtolnay/serde-yaml/compare/0.8.14...0.8.15) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 14:42:13 +03:00
version = "0.4.5"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package bump conflicts vs. just trying to get a small patch in. Closes: #1719 Approved by: cgwalters
2018-12-19 18:48:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump serde_yaml from 0.8.14 to 0.8.15 Bumps [serde_yaml](https://github.com/dtolnay/serde-yaml) from 0.8.14 to 0.8.15. - [Release notes](https://github.com/dtolnay/serde-yaml/releases) - [Commits](https://github.com/dtolnay/serde-yaml/compare/0.8.14...0.8.15) Signed-off-by: dependabot[bot] <support@github.com>
2021-01-25 14:42:13 +03:00
checksum = "56c1936c4cc7a1c9ab21a1ebb602eb942ba868cbd44a99cb7cdc5892335e1c85"
rust: Add Cargo.lock We've been seeing more breakage recently due to much of the Rust ecosystem sticking to minimum rustc versions more recent than ours. A lockfile now means we have to periodically update it, but at least we have much better control over our CI system and when we want to spend time resolving package 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