public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: nmontero <nmontero@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Update to 2.85.0
Date: Tue, 11 Aug 2026 10:38:30 GMT	[thread overview]
Message-ID: <178644471067.1.11037042799878739490.rpms-glib2-0c46f80f2061@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 0c46f80f2061f3f7c604b6b54d314f2f3046f4a9
Author : nmontero <nmontero@redhat.com>
Date   : 2025-05-21T10:14:41+02:00
Stats  : +3/-3 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/glib2/c/0c46f80f2061f3f7c604b6b54d314f2f3046f4a9?branch=cve-2026-58016-f44

Log:
Update to 2.85.0

---
diff --git a/glib2.spec b/glib2.spec
index bc98336..d1f885b 100644
--- a/glib2.spec
+++ b/glib2.spec
@@ -1,11 +1,11 @@
 Name:           glib2
-Version:        2.84.1
+Version:        2.85.0
 Release:        %autorelease
 Summary:        A library of handy utility functions
 
 License:        LGPL-2.1-or-later
 URL:            https://www.gtk.org
-Source:         https://download.gnome.org/sources/glib/2.84/glib-%{version}.tar.xz
+Source:         https://download.gnome.org/sources/glib/2.85/glib-%{version}.tar.xz
 
 # Required for RHEL core crypto components policy. Good for Fedora too.
 # https://bugzilla.redhat.com/show_bug.cgi?id=1630260

diff --git a/sources b/sources
index 5890cef..ef27d4f 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (glib-2.84.1.tar.xz) = ee7f38a4726fd72e41ddb75c4933c7b1bb30935bb2fddc84902d0627a836af512534195132cc02e3d15f168fefc816576181a8d6e436472b582191437b79a456
+SHA512 (glib-2.85.0.tar.xz) = c08dd4f8c87b4dde98a6529e136b935db459bcdf3be22ed76c6bcb6e93d374740c15899c0645cec363c72fb0d508b6365bb5f5aaa7b36b67f13748cfcd0b55ce

                 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=178644471067.1.11037042799878739490.rpms-glib2-0c46f80f2061@fedoraproject.org \
    --to=nmontero@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