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

error: function `create_schema_migrations_table_if_needed` is private #235

Closed
aeikenberry opened this Issue Mar 13, 2016 · 6 comments

Comments

Projects
None yet
4 participants
@aeikenberry

aeikenberry commented Mar 13, 2016

I'm new to Rust and Diesel, but when I try cargo install diesel_cli i get the following error:

   Compiling diesel_cli v0.5.1
.cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs:133:44: 133:96 error: function `create_schema_migrations_table_if_needed` is private
.cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs:133         try!(call_with_conn!(database_url, migrations::create_schema_migrations_table_if_needed));
                                                                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs:133:14: 133:97 note: in this expansion of call_with_conn! (defined in .cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs)
.cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs:133:9: 133:99 note: in this expansion of try! (defined in <std macros>)
.cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs:133:44: 133:96 error: function `create_schema_migrations_table_if_needed` is private
.cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs:133         try!(call_with_conn!(database_url, migrations::create_schema_migrations_table_if_needed));
                                                                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs:133:14: 133:97 note: in this expansion of call_with_conn! (defined in .cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs)
.cargo/registry/src/github.com-88ac128001ac3a9a/diesel_cli-0.5.1/src/database.rs:133:9: 133:99 note: in this expansion of try! (defined in <std macros>)
error: aborting due to 2 previous errors
failed to compile `diesel_cli v0.5.1`, intermediate artifacts can be found at `/Users/aaron/target-install`

Caused by:
  Could not compile `diesel_cli`.

Rust: rustc 1.7.0 (a5d1e7a59 2016-02-29)
Cargo: cargo 0.8.0-nightly (28a0cbb 2016-01-17)
Mac: 10.11.3

If I'm just being a noob, I apologize in advance. Thanks!

@mcasper

This comment has been minimized.

Collaborator

mcasper commented Mar 13, 2016

Hey @aeikenberry!

It looks like a PR got merged into the main Diesel crate recently (that diesel_cli depends on) that is causing this issue, I'll get this fixed real quick and investigate why our tests didn't catch this.

@mcasper

This comment has been minimized.

Collaborator

mcasper commented Mar 13, 2016

Ah, so it looks like this is being caused by the currently published version of diesel_cli compiling diesel 0.5.3, which it does not play nicely with. Once @sgrif publishes a new version of diesel_cli, this should be fixed

@sgrif

This comment has been minimized.

Member

sgrif commented Mar 13, 2016

Whoops, sorry about that. Publishing now

@sgrif

This comment has been minimized.

Member

sgrif commented Mar 13, 2016

Should be good now

@sgrif sgrif closed this Mar 13, 2016

@metmirr

This comment has been minimized.

metmirr commented Aug 14, 2016

I am getting same error:


failed to compile `diesel_cli v0.7.1`, intermediate artifacts can be found at `/home/user/target-install`

Caused by:
  Could not compile `diesel`.

@sgrif

This comment has been minimized.

Member

sgrif commented Aug 14, 2016

Can you open a new issue and provide the full error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment