public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: Update libipt to v2.0.5.
Date: Sun, 28 Jun 2026 00:00:33 GMT	[thread overview]
Message-ID: <178260483392.1.14339799968090579206.rpms-gdb-994c1c4b6911@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : 994c1c4b6911e6081ad11f4d513ddb8126488768
Author : Keith Seitz <keiths@redhat.com>
Date   : 2022-01-31T10:12:12-08:00
Stats  : +5/-4 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/gdb/c/994c1c4b6911e6081ad11f4d513ddb8126488768?branch=gdb-17.2-rebase-f44

Log:
Update libipt to v2.0.5.

---
diff --git a/.gitignore b/.gitignore
index e8a3ba8..1fee4b5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,4 @@
 /new-fedora-release
 /gdb-libstdc++-v3-python-8.1.1-20180626.tar.xz
-/v2.0.4.tar.gz
 /gdb-11.1.tar.xz
+/v2.0.5.tar.gz

diff --git a/gdb.spec b/gdb.spec
index 10cf38e..6c8de94 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -187,7 +187,7 @@ Source5: %{libstdcxxpython}.tar.xz
 Source6: gdbtui
 
 # libipt: Intel Processor Trace Decoder Library
-%global libipt_version 2.0.4
+%global libipt_version 2.0.5
 #=fedora
 Source7: v%{libipt_version}.tar.gz
 #=fedora
@@ -1144,8 +1144,9 @@ fi
 %endif
 
 %changelog
-* Wed Jan 26 2022 Keith Seitz <keiths@redhat.com> - 11.1-11
+* Mon Jan 31 2022 Keith Seitz <keiths@redhat.com> - 11.1-11
 - Fix buld issues. (RHBZ 2042257, Keith Seitz, Andrew Burgess)
+- Update libipt to 2.0.5.
 
 * Thu Jan 20 2022 Fedora Release Engineering <releng@fedoraproject.org>
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild

diff --git a/sources b/sources
index 47a02e5..1643e01 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
 SHA512 (gdb-libstdc++-v3-python-8.1.1-20180626.tar.xz) = a8b1c54dd348cfeb37da73f968742896be3dd13a4215f8d8519870c2abea915f5176c3fa6989ddd10f20020a16f0fab20cbae68ee8d58a82234d8778023520f8
-SHA512 (v2.0.4.tar.gz) = 596d2dac25fdbd3e5660d7e1feeb7e8d5d359d1d0e19b62ef593449037df236db1d4d98820f0031061b5573ed67797a85a77fb9991e215abaabc4bfe16ceaec8
 SHA512 (gdb-11.1.tar.xz) = c40bf970e2f7c2107b29c5aa6a7150daa709d75ddadb73ac20742419d4637d158e3063a4c6ff6e47fae8ca8e1d36253973f85ea15445d004be6d5d7a2dd9bd46
+SHA512 (v2.0.5.tar.gz) = 2e7ac2aede84671b15597d9c56dbe077a81357bbf44b6684802592246fb7729b4a5743238ddf02f6ea143b4d29872f581408135f9c1ea1ccc99dab905916d98d

                 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=178260483392.1.14339799968090579206.rpms-gdb-994c1c4b6911@fedoraproject.org \
    --to=keiths@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