public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Python Maint <python-maint@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: Bootstrap for Python 3.11
Date: Sun, 28 Jun 2026 00:00:40 GMT	[thread overview]
Message-ID: <178260484062.1.512354711500752976.rpms-gdb-e0417821a6a6@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : e0417821a6a61359c14a13200e084762a78b9659
Author : Python Maint <python-maint@redhat.com>
Date   : 2022-06-13T12:33:21+02:00
Stats  : +5/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/gdb/c/e0417821a6a61359c14a13200e084762a78b9659?branch=gdb-17.2-rebase-f44

Log:
Bootstrap for Python 3.11

---
diff --git a/gdb.spec b/gdb.spec
index cfdcf30..6aa8278 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -1,3 +1,4 @@
+%global _without_python 1
 # rpmbuild parameters:
 # --with testsuite: Run the testsuite (biarch if possible).  Default is without.
 # --with buildisa: Use %%{?_isa} for BuildRequires
@@ -49,7 +50,7 @@ Version: 12.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: 1%{?dist}
+Release: 2%{?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
 # Do not provide URL for snapshots as the file lasts there only for 2 days.
@@ -1185,6 +1186,9 @@ fi
 %endif
 
 %changelog
+* Mon Jun 13 2022 Python Maint <python-maint@redhat.com> - 12.1-2
+- Bootstrap for Python 3.11
+
 * Thu May 12 2022 Kevin Buettner - 12.1-1
 - Rebase to FSF GDB 12.1.
 - Update gdb-6.6-buildid-locate.patch.

                 reply	other threads:[~2026-06-28  0:00 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=178260484062.1.512354711500752976.rpms-gdb-e0417821a6a6@fedoraproject.org \
    --to=python-maint@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