Pin exact wayland-client versions. #79
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The wayland feature seems to be broken currently anyway, see #76 |
|
Ah, indeed! I guess the versions will still need to be pinned after that's sorted out, though. |
|
They will, we are waiting for a 0.30 stable release first before merging than and backporting the fixes to 0.2 |
|
Sounds good! I'll go ahead and close this, then. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently tried to use the wayland feature, but it failed because it was pulling in incompatible versions of the various wayland packages. I think the underlying issue is that "0.3.0-beta.3" is not semver compatible with "0.3.0-beta.8", but cargo thinks it is. The fix is to pin the exact versions, and I also had to add an explicit dependency on
wayland-scannerbecause otherwise it pulls inwayland-scanner-0.3.0-beta.8.