|
From: | Maxime Devos |
Subject: | [bug#56298] [PATCH 5/7] gnu: rust-anyhow-1: Update to 1.0.58. |
Date: | Fri, 29 Jul 2022 21:26:43 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 |
I assume you updated rust-rustversion to update rust-anyhow? If so, I have looked at the Cargo.toml of anyhow. It is very picky in the version of dependents, so if in the future we update rust-rustversion again, rust-anyhow will fail to build. To be robust to that, the Cargo.toml needs to be patched to be less picky, or alternatively you could wait for antioxidant which ignores the version specifications entirely.
Nevermind, from <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html>:
The string
"0.1.12"
is a version requirement. Although it looks like a specific version of thetime
crate, it actually specifies a range of versions and allows SemVer compatible updates. An update is allowed if the new version number does not modify the left-most non-zero digit in the major, minor, patch grouping. In this case, if we rancargo update -p time
, cargo should update us to version0.1.13
if it is the latest0.1.z
release, but would not update us to0.2.0
. If instead we had specified the version string as1.0
, cargo should update to1.1
if it is the latest1.y
release, but not2.0
. The version0.0.x
is not considered compatible with any other version.
(if it used = or <=, that would be a different manner)
Greetings,
Maxime.
OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
[Prev in Thread] | Current Thread | [Next in Thread] |