public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: [RHEL] Fix librpm Recommends compatibility.
Date: Sat, 27 Jun 2026 23:57:11 GMT [thread overview]
Message-ID: <178260463105.1.10970284896834392428.rpms-gdb-2f1c4cf20089@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : 2f1c4cf20089774735e89b8a945157f2fe1de082
Author : Jan Kratochvil <jan.kratochvil@redhat.com>
Date : 2015-09-01T17:44:10+02:00
Stats : +6/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/gdb/c/2f1c4cf20089774735e89b8a945157f2fe1de082?branch=gdb-17.2-rebase-f44
Log:
[RHEL] Fix librpm Recommends compatibility.
---
diff --git a/gdb.spec b/gdb.spec
index ac13bc6..1bcbc63 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -26,7 +26,7 @@ Version: 7.10
# 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: 15%{?dist}
+Release: 16%{?dist}
License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ and GPLv2+ with exceptions and GPL+ and LGPLv2+ and BSD and Public Domain and GFDL
Group: Development/Debuggers
@@ -91,7 +91,9 @@ Recommends: default-yama-scope
%global librpmname librpm.so.%{librpmver}
%endif
BuildRequires: %{librpmname}
+%if 0%{!?rhel:1} || 0%{?rhel} > 7
Recommends: %{librpmname}
+%endif
# GDB patches have the format `gdb-<version>-bz<red-hat-bz-#>-<desc>.patch'.
# They should be created using patch level 1: diff -up ./gdb (or gdb-6.3/gdb).
@@ -1323,6 +1325,9 @@ then
fi
%changelog
+* Tue Sep 1 2015 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.10-16.fc23
+- [RHEL] Fix librpm Recommends compatibility.
+
* Sat Aug 29 2015 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.10-15.fc23
- Rebase to FSF GDB 7.10 final.
reply other threads:[~2026-06-27 23:57 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=178260463105.1.10970284896834392428.rpms-gdb-2f1c4cf20089@fedoraproject.org \
--to=jan.kratochvil@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