Skip to content

Remove (yank?) entire libraries from Crates.io #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
frewsxcv opened this issue Jan 21, 2015 · 3 comments
Closed

Remove (yank?) entire libraries from Crates.io #118

frewsxcv opened this issue Jan 21, 2015 · 3 comments

Comments

@frewsxcv
Copy link
Member

I accidentally uploaded a library with the wrong name (accidentally prefixed 'rust-' in the crate name).

https://crates.io/crates/rust-gpx instead of https://crates.io/crates/gpx

I'd like to delete rust-gpx from the registry. I tried to yank its only version and got this:

~/D/r/rust-gpx (master|✔) $ cargo yank --vers 0.0.1 rust-gpx
    Updating registry `https://github.com/rust-lang/crates.io-index`
Press ENTER or type command to continue
        Yank rust-gpx:0.0.1
failed to yank: failed to get a 200 OK response: Response {502, via: 1.1 vegur, content-type: text/html, content-length: 166, date: Wed, 21 Jan 2015 01:29:35 GMT, connection: keep-alive, server: nginx, <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
]
@alexcrichton
Copy link
Member

I think the error you're seeing is #76, and in general we don't want to promote deletion of crates after they've been uploaded (as it would break any dependencies). In this case though I've deleted the rust-gpx crate for you.

@frewsxcv
Copy link
Member Author

Thanks @alexcrichton

@kirillkh
Copy link

I have the same problem with monitor_rs. I want to publish it as just "monitor". Yanking produces the same 502 error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants