-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Multiple crates can't find pkg_config in 1.17 #40183
Comments
This has been fixed in later releases of rusqlite (specifically >= 0.9.0). Is proper crates.io hygiene to go back and publish point releases that fix this for older versions? If so, how far back should I go? |
@jgallagher what was the problem exactly? And, I would say it is very kind of you to upgrade your point releases, definitely! The question of how far back to go is a good one. In this case, the problem is that some dependency likes 0.7.3, which is something you can't easily control... |
@nikomatsakis No problem exactly - there was just a leftover If https://crates.io/crates/rusqlite/reverse_dependencies is the right picture, looks like I should update back to 0.6.x? |
@brson I pushed rusqlite 0.6.1, 0.7.4, and 0.8.1 which should fix this. 0.9 and up was already fixed. |
Hello, am author of sphinxad. I (and not just me) have made something and this is fixed in new version(0.1.2). But where are examples. Each is cargo project.
Why cargo do it? How to fix it? |
Seems like this is expected breakage and we just need to help people adapt. |
I'll look at sending PRs to these crates. |
So for these four crates:
|
@TrionProg sorry for the slow response! It looks like you've already taken care of this and it looks like you've also published, so I don't think there's anything left to be done! @TrionProg if you're still having trouble locally, could you gist the full error you're seeing and I'll help you debug? |
This cargo was uninstalable since rust 1.17, due to rust-lang/rust#40183 . This patch bumps the dependencies just enough to be able to avoid this issue.
due to: rust-lang/cargo#3361
cc @jgallagher @TrionProg
The text was updated successfully, but these errors were encountered: