public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Rebuild for Python 3.6
Date: Tue, 11 Aug 2026 10:36:13 GMT [thread overview]
Message-ID: <178644457346.1.547532238756097769.rpms-glib2-66ce32f8f6f9@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 66ce32f8f6f902ac6b91335ebce0a0ac59bbacd8
Author : Miro Hrončok <miro@hroncok.cz>
Date : 2016-12-19T18:20:36+01:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/glib2/c/66ce32f8f6f902ac6b91335ebce0a0ac59bbacd8?branch=cve-2026-58016-f44
Log:
Rebuild for Python 3.6
---
diff --git a/glib2.spec b/glib2.spec
index 1970bbf..29a8d5f 100644
--- a/glib2.spec
+++ b/glib2.spec
@@ -5,7 +5,7 @@
Name: glib2
Version: 2.51.0
-Release: 1%{?dist}
+Release: 2%{?dist}
Summary: A library of handy utility functions
License: LGPLv2+
@@ -227,6 +227,9 @@ chmod 644 $RPM_BUILD_ROOT%{_datadir}/bash-completion/completions/*
%{_datadir}/installed-tests
%changelog
+* Mon Dec 19 2016 Miro Hrončok <mhroncok@redhat.com> - 2.51.0-2
+- Rebuild for Python 3.6
+
* Sun Oct 30 2016 Kalev Lember <klember@redhat.com> - 2.51.0-1
- Update to 2.51.0
reply other threads:[~2026-08-11 10:36 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=178644457346.1.547532238756097769.rpms-glib2-66ce32f8f6f9@fedoraproject.org \
--to=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