public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michael Catanzaro <mcatanzaro@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Correction: "Stop manually disabling glib_debug" enabled glib_debug!
Date: Tue, 11 Aug 2026 10:38:18 GMT	[thread overview]
Message-ID: <178644469806.1.2957964169977866126.rpms-glib2-6660a292f4a6@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/glib2
            Branch : cve-2026-58016-f44
            Commit : 6660a292f4a69066150359860dac0a80bcc4963b
            Author : Michael Catanzaro <mcatanzaro@redhat.com>
            Date   : 2024-07-10T08:57:32-05:00
            Stats  : +0/-0 in 0 file(s)
            URL    : https://src.fedoraproject.org/rpms/glib2/c/6660a292f4a69066150359860dac0a80bcc4963b?branch=cve-2026-58016-f44

            Log:
            Correction: "Stop manually disabling glib_debug" enabled glib_debug!

In the commit message for 4a5ba3dfb0c1d05f02724fd23115462a12f81f5 I
claimed that removing -Dglib_debug=disabled from the spec file would not
change anything because it defaults to disabled already. But it is an
auto feature, and we use -Dauto_features=enabled, so it really does get
enabled now. This commit switched us from non-debug to debug GLib.

I have decided to leave this be, though. The most notable change is it
enables cast checks in GLib itself, which has already surfaced a serious
bug in Contacts. I'm inclined to stick with fewer build options and let
upstream decide whether it likes this or not via upstream build system
changes.

For discussion, see:
https://gitlab.gnome.org/GNOME/glib/-/issues/3380#note_2163045

                 reply	other threads:[~2026-08-11 10:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178644469806.1.2957964169977866126.rpms-glib2-6660a292f4a6@fedoraproject.org \
    --to=mcatanzaro@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox