Closed sourcefrog closed 1 year ago
I wonder if this is somehow connected to changes in the version resolver in recent releases?
Oh... I wondered why all crate resolutions were giving unexpected results... Now I understand.
And so I have a lot of work to fix that in two dozen programs...
@sourcefrog Can you try with
cargo install --locked lfs
?
(edit replaced broot with lfs)
I actually installed broot
on this machine the other day without --locked
and it worked.
I tried --locked
on lfs and I do get this warning:
Installing lfs v2.5.0
warning: package `crossbeam-channel v0.5.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
but aside from that it does work.
Thanks. Please don't close this issue. We'll let it open so that people having the same problem see the solution.
I'll upgrade dependencies when coming back from holidays, I think.
Have a good holiday!
this is solved by bumping crossterm to the same version termimad depends on.
I have a tarball of the build directory if you want it.
I wonder if this is somehow connected to changes in the version resolver in recent releases?
It also fails under the nightly of 2022-07-24.
I also get a similar error on 1.59. I tried 1.56 but it does not yet have the
strip
feature stabilized.