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: [rhel5] Fix up the previous commit (BZ 799318).
Date: Sat, 27 Jun 2026 23:55:30 GMT [thread overview]
Message-ID: <178260453014.1.17062567337873770784.rpms-gdb-46d8530cd6c1@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : 46d8530cd6c11f2cd2a700b274433412b626b78a
Author : Jan Kratochvil <jan.kratochvil@redhat.com>
Date : 2012-03-04T18:52:21+01:00
Stats : +11/-5 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/gdb/c/46d8530cd6c11f2cd2a700b274433412b626b78a?branch=gdb-17.2-rebase-f44
Log:
[rhel5] Fix up the previous commit (BZ 799318).
---
diff --git a/gdb.spec b/gdb.spec
index dceecde..6422732 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -33,7 +33,7 @@ Version: 7.4.50.%{snap}
# 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: 26%{?dist}
+Release: 27%{?dist}
License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ and GPLv2+ with exceptions and GPL+ and LGPLv2+ and BSD and Public Domain
Group: Development/Debuggers
@@ -582,6 +582,11 @@ BuildRequires: libstdc++%{?_isa}
# gdb-doc in PDF:
BuildRequires: texinfo-tex
+# BuildArch would break RHEL-5 by overriding arch and not building noarch.
+%if 0%{?el5:1}
+ExclusiveArch: noarch i386 x86_64 ppc ppc64 ia64 s390 s390x
+%endif # 0%{?el5:1}
+
%if 0%{?_with_testsuite:1}
# Ensure the devel libraries are installed for both multilib arches.
@@ -684,11 +689,9 @@ Summary: Documentation for GDB (the GNU source-level debugger)
License: GFDL
Group: Documentation
# It would break RHEL-5 by overriding arch and not building noarch separately.
-%if 0%{?el5:1}
-ExclusiveArch: noarch i386 x86_64 ppc ppc64 ia64 s390 s390x
-%else # !0%{?el5:1}
+%if 0%{!?el5:1}
BuildArch: noarch
-%endif # !0%{?el5:1}
+%endif # 0%{!?el5:1}
%description doc
GDB, the GNU debugger, allows you to debug programs written in C, C++,
@@ -1293,6 +1296,9 @@ fi
%endif # 0%{!?el5:1} || "%{_target_cpu}" == "noarch"
%changelog
+* Sun Mar 4 2012 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.4.50.20120120-27.fc17
+- [rhel5] Fix up the previous commit (BZ 799318).
+
* Sun Mar 4 2012 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.4.50.20120120-26.fc17
- [rhel5] Fix up the previous commit (BZ 799318).
next reply other threads:[~2026-06-27 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 23:55 Jan Kratochvil [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-27 23:55 [rpms/gdb] gdb-17.2-rebase-f44: [rhel5] Fix up the previous commit (BZ 799318) Jan Kratochvil
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=178260453014.1.17062567337873770784.rpms-gdb-46d8530cd6c1@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