Event JSON
{
"id": "fabb40136bd8955f1fe794f735ff725063f05f1beba7bfc16cd0044651c02a1e",
"pubkey": "36127c569b635ad5df03489b77eb4ef8c345bee0216c357b247aaea99590b286",
"created_at": 1714915289,
"kind": 1,
"tags": [
[
"proxy",
"https://social.treehouse.systems/@mgorny/112388688432186765",
"web"
],
[
"t",
"gentoo"
],
[
"t",
"rustlang"
],
[
"proxy",
"https://social.treehouse.systems/users/mgorny/statuses/112388688432186765",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://social.treehouse.systems/users/mgorny/statuses/112388688432186765",
"pink.momostr"
]
],
"content": "Am I missing something or is it basically impossible to have `cargo update` actually select dependencies that are acceptable for the specific minimal `rust-version`? Like, even if you install old #RustLang version, `cargo update` from this version will update `Cargo.lock` to dependencies that require a newer Rust version and render the package non-buildable?\n\nSo yeah, I suppose you either end up requiring newer Rust (but you don't really know which version, since you don't know what's the highest minimal requirement in your dependencies), or you update `Cargo.lock` by hand. Such a great tooling!\n\nhttps://github.com/samuelcolvin/watchfiles/pull/267#issuecomment-2094753389\n\n#Gentoo",
"sig": "9969591e38fd2827b03c2939b2cc291555b19afc86a7a8c6647b1aec2d7258599a3af0363030aa7aabf9564c4c492b50dfe06821849106580eac37615afb9c83"
}