Closed mihirn closed 3 months ago
Ugh, thanks. time
is pulled in from clocksource
so I'm guessing the better fix is to fix it upstream rather than having an explicit dependency here?
No. All you need to do is run cargo update --precise time
. This is not an issue with clocksource (although clocksource will probably run into a similar issue).
Ok, that worked, thanks!
Looks like you've got two issues that you need to address:
cargo build
and then committing the changes it makes to the lockfile should fix this.time
crate to the latest patch release to fix this.