public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Kalev Lember <klember@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Don't number sources and patches
Date: Tue, 11 Aug 2026 10:38:02 GMT [thread overview]
Message-ID: <178644468269.1.4915466093520082528.rpms-glib2-6995c02c209d@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 6995c02c209df4fe8f42e0fe862f23aaae6c2b9f
Author : Kalev Lember <klember@redhat.com>
Date : 2023-09-16T21:35:06+02:00
Stats : +4/-4 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/glib2/c/6995c02c209df4fe8f42e0fe862f23aaae6c2b9f?branch=cve-2026-58016-f44
Log:
Don't number sources and patches
We can now have multiple Patch: lines that are all applied correctly by
autosetup.
---
diff --git a/glib2.spec b/glib2.spec
index 9cfc809..375d3c3 100644
--- a/glib2.spec
+++ b/glib2.spec
@@ -5,19 +5,19 @@ Summary: A library of handy utility functions
License: LGPL-2.1-or-later
URL: https://www.gtk.org
-Source0: https://download.gnome.org/sources/glib/2.77/glib-%{version}.tar.xz
+Source: https://download.gnome.org/sources/glib/2.77/glib-%{version}.tar.xz
# Required for RHEL core crypto components policy. Good for Fedora too.
# https://bugzilla.redhat.com/show_bug.cgi?id=1630260
# https://gitlab.gnome.org/GNOME/glib/-/merge_requests/903
-Patch0: gnutls-hmac.patch
+Patch: gnutls-hmac.patch
# recent close_range() changes break CircleCI and GitHub actions -- we can remove this when
# the baremetal Docker is updated there i.e. lets be a little bit pragmatic...
-Patch2: gspawn-eperm.patch
+Patch: gspawn-eperm.patch
# https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3565
-Patch3: 3565.patch
+Patch: 3565.patch
BuildRequires: gcc
BuildRequires: gcc-c++
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=178644468269.1.4915466093520082528.rpms-glib2-6995c02c209d@fedoraproject.org \
--to=klember@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