Repository navigation
Conversation
ucrt64 shipped glibmm 2.90.0 and gtkmm 4.24.0 on 2026-10-03, built against glib 2.90. The new gtkmm requires gio >= 2.89.4 and gtk4 >= 4.23.4, so holding glib2 2.88.3 and gtk4 4.22.4 now fails configure instead of keeping the build working.
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.
Windows configure now fails on every branch:
ucrt64 published glibmm 2.90.0 and gtkmm 4.24.0 today (2026-10-03, ~17:10 UTC), both built against glib 2.90. The hold step existed because the previous giomm/gdkmm didn't compile against glib 2.90 and gtk4 4.24. Its own comment said to drop it once the packages caught up, and now it is what blocks the build.
This removes the step from
ci.ymland fromrelease.yml, which had the same pin. The cairo hold is a separate issue and stays.