John Soo <js...@asu.edu> writes: > I think the problem is that the version bound is too loose in > cargo.toml upstream. What does the cargo.lock say on the current > master? I am beginning to think we need to follow the cargo.lock to > resolve dependencies first if it exists.
It's 0.2.12 in Cargo.toml and 0.2.14 in Cargo.lock. See <https://github.com/BurntSushi/ripgrep/blob/master/Cargo.lock> Regards,
