public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Richard W.M. Jones <rjones@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: Bump and rebuild for riscv64
Date: Sun, 28 Jun 2026 00:01:31 GMT	[thread overview]
Message-ID: <178260489176.1.3126744545145655006.rpms-gdb-84b617d8edae@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : 84b617d8edae0cb768dc0027691cc9bf7bef3d3f
Author : Richard W.M. Jones <rjones@redhat.com>
Date   : 2024-02-21T10:10:35+00:00
Stats  : +4/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/gdb/c/84b617d8edae0cb768dc0027691cc9bf7bef3d3f?branch=gdb-17.2-rebase-f44

Log:
Bump and rebuild for riscv64

---
diff --git a/gdb.spec b/gdb.spec
index b6d6c00..21a3200 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -57,7 +57,7 @@ Version: 14.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: 8%{?dist}
+Release: 9%{?dist}
 
 License: GPL-3.0-or-later AND BSD-3-Clause AND FSFAP AND LGPL-2.1-or-later AND GPL-2.0-or-later AND LGPL-2.0-or-later AND LicenseRef-Fedora-Public-Domain AND GFDL-1.3-or-later AND LGPL-2.0-or-later WITH GCC-exception-2.0 AND GPL-3.0-or-later WITH GCC-exception-3.1 AND GPL-2.0-or-later WITH GNU-compiler-exception
 # Do not provide URL for snapshots as the file lasts there only for 2 days.
@@ -1250,6 +1250,9 @@ fi
 %endif
 
 %changelog
+* Wed Feb 21 2024 Richard W.M. Jones <rjones@redhat.com>
+- Bump and rebuild for riscv64
+
 * Mon Jan 29 2024 Kevin Buettner <kevinb@redhat.com> - 14.1-8
 - Backport upstream workaround for GCC 14 problem which is causing
   GDB internal errors (RHBZ 261580, Tom de Vries).

                 reply	other threads:[~2026-06-28  0:01 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=178260489176.1.3126744545145655006.rpms-gdb-84b617d8edae@fedoraproject.org \
    --to=rjones@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