-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
v0.25/v0.25.1 does not build with cargo-1.70.0 (feature/dependency problem with env_logger and/or clap_builder) #2094
Comments
its interesting. my first thought: impossible we build with our MSRV on CI, only to find out no, I forgot to update that. |
damn maybe its just the same as #2090 - can you try building with |
I did try both variants, but neither worked. Both resulted in exactly the same error message as before. I also tried cleaning out the package/crate cache in |
Update: just tried 0.25.1 to see if this happens to fix my problem as well. Still the same error, though. However, when I tried to
Does this help to clear things up a bit, or does it make matters even more "WTF?" than before? 🤔 🤷♂️ 😇 |
Just for the record:
|
I got the same issue with cargo 1.66.0-nightly (9210810d1 2022-10-25). |
You can try modifying it to the following code:
|
@wugeer where would one make that change (what file)? Would that be in the config file for the package or env_logger, etc. and what would we be replacing with that? I am having a similar issue with another cargo package. |
@MetaMan2023 You can check all the |
Describe the bug
Out of old habit, I'm usually "rolling my own" instead of downloading binaries. The latest
gitui-v0.25
does not build withcargo-1.70.0
for me, although this version should be fine according to the published build requirements.To Reproduce
gitui-0.25.0
make build-release
Expected behavior
Should either build fine as usual, or the build requirements should be updated (in case my
rust/cargo
is too old).Context (please complete the following information):
Slackware64 15.0
0.25
1.70.0
The text was updated successfully, but these errors were encountered: