Update Glib to 2.83.2

[snoweuph]

There is a new Glib version with Bugfixes

Specifically: https://gitlab.gnome.org/GNOME/glib/-/issues/3568 is fixed

I suggest either upgrading Brews Glib, or backporting the Fix: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4448 till the next stable release is out

[snoweuph]

@ZhongRuoyu could you give an explanation?

I was still editing it, because theres sadly no template for suggesting a backport/upgrade of a package

[snoweuph]

as long as https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4448 is not fixed, links in gtk / libadwaita apps build on a machine with brew will crash the app when clicked

[ZhongRuoyu]

If you have read the issue template you would have noticed this:

Please note we will close your issue without comment if you do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

This issue tracker is not used for this purpose as the number of issues would otherwise easily grow beyond our control. If you would like the formula patched, please submit a pull request. More info that you'll find useful:

• https://docs.brew.sh/Updating-Software-in-Homebrew
• https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request

[snoweuph]

I don't feel comfortable doing a PR to brew and was thinking that the core packages like glib would be handled by maintainers

[snoweuph]

Is there a tracker where such things can be reported, for people not feeling comfortable doing a pr?

[gromgit]

Note the final statement: The 2.82.x stable series were never affected, so this bug has only affected unstable (development) releases. Glib on Homebrew is currently from the 2.82.x series, and has never done unstable releases.

[snoweuph]

It Effects the Development libs though, so building from source and running on brew has the bug when not in release mode

[snoweuph]

The Report there was made after the bug happened during trying out with the newest brew on a lended macBook, so yea, its "only" developers who are affected

[ZhongRuoyu]

building from source and running on brew has the bug when not in release mode

To be clear: if you rely solely on the official taps (i.e., are not installing packages provided by third parties) it's not possible for you to install Glib 2.83.x through Homebrew, because it's never an available option regardless of whether you are building glib the Homebrew package from source or not. If you somehow have it installed it's likely through some other means beyond Homebrew's control.

[gromgit]

If you somehow have it installed it's likely through some other means beyond Homebrew's control.

But if you can confirm that you built and ran your test against Homebrew's Glib (2.82.4 as of this writing), then the correct thing to do is to alert the Glib developers that they should reinvestigate the issue, since they clearly feel that stable releases aren't affected.