Downgrade win_flex_bison to 2.5.24. #43539
Merged
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
Attempts to workaround microsoft#29139 / lexxmark/winflexbison#86 It looks like others are pinning 1 version older and that seems to fix the problem for them. Related: m-kuhn/QGIS@23d6c2f Related: microsoft#23084
BillyONeal
added
info:internal
vicroms
approved these changes
Jan 30, 2025
dg0yt
reviewed
Jan 30, 2025
Yeah, this is a good idea. I'll wait for the PR run to finish and merge it with an additional comment. |
|
Actually everything is green except osx which this change does not affect, so I'm going to add a comment and land. |
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.
Attempts to workaround #29139 / lexxmark/winflexbison#86
It looks like others are pinning 1 version older and that seems to fix the problem for them.
Related: m-kuhn/QGIS@23d6c2f
Related: #23084
Related: lexxmark/winflexbison@2bfaf44 (appears to be a fix, but no release has happened yet)