Skip to content
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

Sync to cargo.io #29

Closed
jamperry opened this issue Apr 2, 2015 · 3 comments
Closed

Sync to cargo.io #29

jamperry opened this issue Apr 2, 2015 · 3 comments

Comments

@jamperry
Copy link

@jamperry jamperry commented Apr 2, 2015

Got another bincode build issue.

/home/pez/.cargo/registry/src/github.com-1ecc6299db9ec823/bincode-0.0.13/src/reader.rs:126            self.read += cast(count).unwrap();
                                                                                                            ^~~~~~~~~~~~~~~~~~~~
error: aborting due to previous error
Build failed, waiting for other jobs to finish...
Could not compile `bincode`.

Look at the current master, it seems you have fixed this but it's not sync up to Cargo.io

I would greatly appreciate if you would automate a sync between your master and Cargo.io so you don't forget. I'm running a startup and it causes productivity problems :(

@TyOverby
Copy link
Collaborator

@TyOverby TyOverby commented Apr 2, 2015

Can you depend on the git version instead of crates.io? I'm disconnected from the internet for most of the day and can't always compile and publish.

Right now I can't publish because byteorder is broken BurntSushi/byteorder#24 because rand is broken rust-random/rand#42

@TyOverby
Copy link
Collaborator

@TyOverby TyOverby commented Apr 2, 2015

Updated

@TyOverby TyOverby closed this Apr 2, 2015
@jamperry
Copy link
Author

@jamperry jamperry commented Apr 3, 2015

Thanks for the quick resolution. Yeah, I will depend on the git version now 👍

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.