-
-
Notifications
You must be signed in to change notification settings - Fork 570
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
cargo install gitui
fails without --lock
or lockfile: gitui v0.25.1
#2098
Comments
|
still weird though i thought this was fixed by pinning the version in 5cff322 |
Compiling ratatui v0.26.1
Compiling ratatui v0.24.0 Seems there is some dep that is not complying to using v24... If you kill the lockfile and rebuild you see in lock:
|
ok i cant get it to work without though I fixed it as of #2090 |
https://github.com/rhysd/tui-textarea/blob/main/Cargo.toml#L45 Seems that this is the issue... but I would think that cargo would then resolve to the more strict requirement, that you set... IIUC textarea is less strict? Could be a cargo bug? 🤷 See also rhysd/tui-textarea#36 |
i mean there is no right or wrong I guess, in most cases cargo magically allowing two versions of the same dependency works fine, but I know of no way to control/configure that I want cargo to optimize for less duplication instead of most newest crates at expense of bloat and incompatibility like in this case. |
If I had to bet, I would think that it's a problem with features not matching up. But I see both here and in textarea IDK but maybe it has to do with resolving this nested crossterm feature for ratatui here? |
cargo install gitui
fails gitui v0.25.1cargo install gitui
fails without --lock
or lockfile: gitui v0.25.1
anyone coming across this: this is currently blocked by upstream work needed from ratatui. please see #2079 for more info |
Describe the bug
Install fails (expand for logs)
To Reproduce
Steps to reproduce the behavior:
Context (please complete the following information):
The text was updated successfully, but these errors were encountered: