Yank versions <=0.18.4 to fix funty breakage

[durch]

trafficstars

As 0.18 versions prior to 0.18.5 have a lock on the major version on funty they cannot be in the same project as versions depending on funty ~1.2, as funty ~1.2 is not compatible with 0.18 versions.

To resolve the issues versions <=0.18.4 should be yanked from crates.io. This would force proper dependency resolution and 0.18.5 could coexist with 0.22.* for example.

At the moment if both 0.18 and 0.22 versions are in the dependency chain Cargo.lock resolves to 0.18.4 and 0.22.3 both of which pull in funty 1.2.0 as a dependency and this in turn breaks compliation of 0.18.4

[nappa85]

As far as I can see, the only difference between versions 0.19.4 and 0.19.5, published the same day, is the funty version accepted. 0.19.4 has funty = "1" 0.19.5 has funty = "~1.1"

This creates false positives, for example when trying to build a project with both lapin and mysql_async between the deps, it selects bitvec 0.19.4 because of that "hole" (mysql_async needs funty 1.2 while lapin funty 1.1) and then fails to build.

So, version 0.19.4 should be yanked too

[McFranko]

I also have this issue when trying to build my project, it seems like there is a conflicting definition of const BITS