Exact crate version requirement for quote in c2rust-bitfields-derive prevents update

[mtnking]

cargo update -p tun --precise 0.8.8 --verbose
Updating crates.io index
error: failed to select a version for quote.
... required by package zerovec-derive v0.11.3
... which satisfies dependency zerovec-derive = "^0.11.3" (locked to 0.11.3) of package zerovec v0.11.6
... which satisfies dependency zerovec = "^0.11.6" (locked to 0.11.6) of package icu_normalizer v2.2.0
... which satisfies dependency icu_normalizer = "^2.2" (locked to 2.2.0) of package idna_adapter v1.2.2
... which satisfies dependency idna_adapter = "^1" (locked to 1.2.2) of package idna v1.1.0
... which satisfies dependency idna = "^1.0.3" (locked to 1.1.0) of package hickory-net v0.26.1
... which satisfies dependency hickory-net = "^0.26.0" (locked to 0.26.1) of package hickory-resolver v0.26.1
... which satisfies dependency hickory-resolver = "^0.26" (locked to 0.26.1) of package redwood v3.0.0-dev10 (C:\Users\User\Documents\MSF\WW_RC\redwood)
versions that meet the requirements ^1.0.44 are: 1.0.45, 1.0.44

all possible versions conflict with previously selected packages.

previously selected package quote v1.0.40
... which satisfies dependency quote = "=1.0.40" of package c2rust-bitfields-derive v0.22.1
... which satisfies dependency c2rust-bitfields-derive = "^0.22.1" of package c2rust-bitfields v0.22.1
... which satisfies dependency c2rust-bitfields = "^0.22.1" of package wintun-bindings v0.7.35
... which satisfies dependency wintun-bindings = "^0.7.35" of package tun v0.8.8
... which satisfies dependency tun = "^0.8" of package redwood v3.0.0-dev10 (C:\Users\User\Documents\MSF\WW_RC\redwood)

failed to select a version for quote which could resolve this conflict

[ahomescu]

That crate needs to be pinned to that exact version that matches the Rust toolchain release for the transpiled code. We unfortunately can't change the crate version without bumping the toolchain.

Where is tun even coming from?

[mtnking]

tun/hickory are my dependencies, the pin causes a conflict between them (well, their deps, but yeah)

[mtnking]

My dep chain removed you as deps which sorts the issue for me, closing as OBE