* bug#36457: Guix does not match point-versions correctly @ 2019-07-01 9:11 swedebugia 2019-07-01 9:30 ` swedebugia 2019-07-01 9:58 ` Danny Milosavljevic 0 siblings, 2 replies; 3+ messages in thread From: swedebugia @ 2019-07-01 9:11 UTC (permalink / raw) To: 36457 Hi I'm doing the crate-adventure and stumbled on this: starting phase `build' error: failed to select a version for the requirement `clippy = "^0.0.41"` candidate versions found which didn't match: 0.0.302 location searched: directory source `/tmp/guix-build-rust-blake2-rfc-0.2.18.drv-0/blake2-rfc-0.2.18/guix-vendor` (which is replacing registry `https://github.com/rust-lang/crates.io-index`) required by package `blake2-rfc v0.2.18 (/tmp/guix-build-rust-blake2-rfc-0.2.18.drv-0/blake2-rfc-0.2.18)` But the version we got is way above .41. 0.0.302 > 0.0.41! WDYT? -- Cheers Swedebugia ^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#36457: Guix does not match point-versions correctly 2019-07-01 9:11 bug#36457: Guix does not match point-versions correctly swedebugia @ 2019-07-01 9:30 ` swedebugia 2019-07-01 9:58 ` Danny Milosavljevic 1 sibling, 0 replies; 3+ messages in thread From: swedebugia @ 2019-07-01 9:30 UTC (permalink / raw) To: 36457 On 2019-07-01 11:11, swedebugia wrote: > Hi > > I'm doing the crate-adventure and stumbled on this: > > starting phase `build' > error: failed to select a version for the requirement `clippy = "^0.0.41"` > candidate versions found which didn't match: 0.0.302 > location searched: directory source > `/tmp/guix-build-rust-blake2-rfc-0.2.18.drv-0/blake2-rfc-0.2.18/guix-vendor` > (which is replacing registry > `https://github.com/rust-lang/crates.io-index`) > required by package `blake2-rfc v0.2.18 > (/tmp/guix-build-rust-blake2-rfc-0.2.18.drv-0/blake2-rfc-0.2.18)` > > But the version we got is way above .41. > 0.0.302 > 0.0.41! > > WDYT? > Oops maybe this output is from cargo. According to https://semver.npmjs.com/ the ^ (hat) means: include everything greater than a particular version in the same major range. cargo should thus accept up to 0.0.999 in this case as valid but does not. Should I relax the version requirement? To what? -- Cheers Swedebugia ^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#36457: Guix does not match point-versions correctly 2019-07-01 9:11 bug#36457: Guix does not match point-versions correctly swedebugia 2019-07-01 9:30 ` swedebugia @ 2019-07-01 9:58 ` Danny Milosavljevic 1 sibling, 0 replies; 3+ messages in thread From: Danny Milosavljevic @ 2019-07-01 9:58 UTC (permalink / raw) To: swedebugia; +Cc: 36457 [-- Attachment #1: Type: text/plain, Size: 844 bytes --] On Mon, 1 Jul 2019 11:11:45 +0200 swedebugia <swedebugia@riseup.net> wrote: > I'm doing the crate-adventure and stumbled on this: > > starting phase `build' > error: failed to select a version for the requirement `clippy = "^0.0.41"` > candidate versions found which didn't match: 0.0.302 > location searched: directory source > `/tmp/guix-build-rust-blake2-rfc-0.2.18.drv-0/blake2-rfc-0.2.18/guix-vendor` > (which is replacing registry `https://github.com/rust-lang/crates.io-index`) > required by package `blake2-rfc v0.2.18 > (/tmp/guix-build-rust-blake2-rfc-0.2.18.drv-0/blake2-rfc-0.2.18)` > > But the version we got is way above .41. > 0.0.302 > 0.0.41! https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html says: > The version 0.0.x is not considered compatible with any other version. [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-07-01 9:59 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-07-01 9:11 bug#36457: Guix does not match point-versions correctly swedebugia 2019-07-01 9:30 ` swedebugia 2019-07-01 9:58 ` Danny Milosavljevic
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/guix.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).