public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Fedora Release Engineering <releng@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
Date: Sat, 27 Jun 2026 23:58:31 GMT [thread overview]
Message-ID: <178260471152.1.7085491199071858856.rpms-gdb-f9b3dfe2c998@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : f9b3dfe2c998cacf7d01ea8417719347f2645e34
Author : Fedora Release Engineering <releng@fedoraproject.org>
Date : 2018-02-07T10:44:34+00:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/gdb/c/f9b3dfe2c998cacf7d01ea8417719347f2645e34?branch=gdb-17.2-rebase-f44
Log:
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
Signed-off-by: Fedora Release Engineering <releng@fedoraproject.org>
---
diff --git a/gdb.spec b/gdb.spec
index a8e6128..1fe6ec1 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -26,7 +26,7 @@ Version: 8.1
# The release always contains a leading reserved number, start it at 1.
# `upstream' is not a part of `name' to stay fully rpm dependencies compatible for the testing.
-Release: 6%{?dist}
+Release: 7%{?dist}
License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ and GPLv2+ with exceptions and GPL+ and LGPLv2+ and LGPLv3+ and BSD and Public Domain and GFDL
Group: Development/Debuggers
@@ -1032,6 +1032,9 @@ then
fi
%changelog
+* Wed Feb 07 2018 Fedora Release Engineering <releng@fedoraproject.org>
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
+
* Tue Feb 6 2018 Jan Kratochvil <jan.kratochvil@redhat.com> - 8.1-6.fc28
- Fix .spec build compatibility with <=F-27 and <=RHEL-7.
- [testsuite] Temporarily disable BuildRequires: gcc-go (for RH BZ 1541639).
reply other threads:[~2026-06-27 23:58 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=178260471152.1.7085491199071858856.rpms-gdb-f9b3dfe2c998@fedoraproject.org \
--to=releng@fedoraproject.org \
--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