-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Broken .toml file #302
Comments
What version of rust/cargo do you have installed?
…On Jan 3, 2017 4:35 PM, "Matěj Cepl" ***@***.***> wrote:
***@***.***:~/Build/ripgrep$ cargo build --release
failed to parse manifest at `/home/matej/Build/ripgrep/Cargo.toml`
Caused by:
could not parse input as TOML
Cargo.toml:42:9 expected a key but found an empty string
Cargo.toml:42:9-42:10 expected `.`, but found `'`
***@***.***:~/Build/ripgrep$
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#302>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAb34n8MMcW3NOVrPAUNijugzG1NWg-eks5rOr83gaJpZM4LaDeO>
.
|
What's in Ubuntu 16.04, rustc 1.7.0 and cargo 0.8.0. |
OK, so rust is still too unstable for normal use. I'll get the staticly build file. |
That's wrong. Rust is quite stable. ripgrep simply requires a newer version of Rust than what you have installed. |
Sorry, I didn't mean to be rude. However, then probably it would be good to reconsider the required compatibility. I am not personally invested in Ubuntu (being the Red Hat employee, I use Fedora/RHEL for all my needs, and we have the latest rust even for RHEL-7/EPEL), but 16.04 is LTS, so I guess it could be wise to have it supported. |
No, it's not happening, sorry. I can't afford to do that kind of maintenance. We need to move forward. |
The text was updated successfully, but these errors were encountered: