Repository navigation
docs(linux): link the upstream issues behind two workarounds - #3457
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
Two workarounds wait on upstream fixes: the editor drops its input method on close because IBus keeps text views alive on GTK 4.24, and
deny.tomlallows the yanked zip 8.6.0 until rust_xlsxwriter releases zip 9 support. Neither said where to watch.Change
deny.tomlreason links Update zip to 9: every zip 8.x release is yanked jmcnamara/rust_xlsxwriter#205. Itsmainalready moves to zip 9, and our export tests pass on it with one change for the newResultfromadd_worksheet_with_constant_memory().Verified
Comment and reason text only.