Yanked crate affected by breakage - what now?


#1

The shared_library crate has been affected by this breakage - an interesting conundrum to be sure…


#2

Version 0.1.2 seems to compile, not sure what I’m missing. It’s finding versions 0.1.0, 0.1.1, 0.1.2 on crates.io


#3

Does it? I was talking about 0.1.0 specifically - that means I’d have to edit Cargo.toml and .lock manually as cargo update leads to complete dependency failure.


#4

This is the full crate’s history on crates.io, so the 0.1.2 version is very recent (and does in fact use libc 0.2).

commit 88959ce2e73124dd6d5cbebe95af5c4a445d10e4
Author: bors <bors@rust-lang.org>
Date:   Sat Nov 21 07:11:08 2015 +0000

    Updating crate `shared_library#0.1.2`

commit c8da271b042183aa26e73dbc40e979813305f833
Author: bors <bors@rust-lang.org>
Date:   Sat Nov 21 07:07:05 2015 +0000

    Yanking crate `shared_library#0.2.2`

commit 0a24e31affac2200e6c8b4a247bc582adccad712
Author: bors <bors@rust-lang.org>
Date:   Sat Nov 21 07:07:01 2015 +0000

    Yanking crate `shared_library#0.2.0`

commit ed6a09285b0a7dbe58bbfbf9eff6d67c74028b94
Author: bors <bors@rust-lang.org>
Date:   Fri Nov 20 20:27:16 2015 +0000

    Updating crate `shared_library#0.1.1`

commit 975d4a3e449d552221653489c989989cca234722
Author: bors <bors@rust-lang.org>
Date:   Fri Nov 20 20:24:45 2015 +0000

    Updating crate `shared_library#0.2.2`

commit d1419dc15f5b88e8746269b9913e86efc9409c03
Author: bors <bors@rust-lang.org>
Date:   Fri Nov 20 20:24:35 2015 +0000

    Yanking crate `shared_library#0.2.1`

commit dc4ba0b64383af03c506bc5051901aacff342351
Author: bors <bors@rust-lang.org>
Date:   Fri Nov 20 20:23:48 2015 +0000

    Updating crate `shared_library#0.2.1`

commit 9eabed975f31b94e575e30ad412f2a225cb8b89e
Author: bors <bors@rust-lang.org>
Date:   Fri Nov 20 20:20:26 2015 +0000

    Updating crate `shared_library#0.2.0`

commit 4aca47f70fd4a6a2329ecc25850d288a4fbb97e8
Author: bors <bors@rust-lang.org>
Date:   Mon Apr 27 12:19:24 2015 +0000

    Updating crate `shared_library#0.1.0`

#5

You were right - even though a full cargo update doesn’t work, cargo update -p shared_library solves the problem and the crate compiles.

Thx, the fact the crate’d been yanked threw me off the scent :slight_smile:


#6

The fact that the crate shows up entirely yanked on crates.io even though there are unyanked versions is a bug that can be fixed with some manual intervention - cc @alexcrichton


#7

Oh dear, looks like https://github.com/rust-lang/crates.io/issues/76 has struck again! I updated it manually and sorry for the confusion!