Cargo.toml: Avoid mixing old libc 0.2.172

[oech3]

uutils#8722 (comment)
At AUR/MSYS package with cargo update -p libc hack:

   Compiling libc v0.2.175
   Compiling libc v0.2.178 (/tmp/makepkg/uutils-coreutils-git/src/libc-0.2.178)

Not sure is it related with FreeBSD's err.

[cakebaker]

You opened your PR in the wrong repository ;-)

[oech3]

Because I did not want to override author of PR bumping crate ver.

[cakebaker]

Ah, now I see, this is a PR to my PR, and not to the repository. I'm sorry, I misinterpreted it :|

I don't understand what you are trying to accomplish with the change. The versions in Cargo.toml are often different from the ones we use in Cargo.lock.

[oech3]

AUR/uutils-coreutils-git builds 2 libc crates curreltly. Does not cause some internal breakage?

[oech3]

(FreeBSD is still broken with this)

[cakebaker]

Hm, I don't know why AUR/uutils-coreutils-git builds two libc crates. In Cargo.lock we have only one version of libc. In general it isn't a problem to use multiple versions of a crate.