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.2.
Date: Sun, 28 Jun 2026 00:00:03 GMT	[thread overview]
Message-ID: <178260480353.1.5785803636199988919.rpms-gdb-ab7962ace7dc@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : ab7962ace7dca1d6391b9c37bb59f64b48dd98c0
Author : Keith Seitz <keiths@redhat.com>
Date   : 2020-08-04T10:45:45-07:00
Stats  : +6/-3 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/gdb/c/ab7962ace7dca1d6391b9c37bb59f64b48dd98c0?branch=gdb-17.2-rebase-f44

Log:
Update libipt to v2.0.2.

---
diff --git a/.gitignore b/.gitignore
index 4661874..b83cfdf 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,4 @@
 /binutils-gdb
 /gdb-libstdc++-v3-python-8.1.1-20180626.tar.xz
-/v2.0.1.tar.gz
 /gdb-9.2.tar.xz
+/v2.0.2.tar.gz

diff --git a/gdb.spec b/gdb.spec
index 40199c2..98aa65b 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -186,7 +186,7 @@ Source5: %{libstdcxxpython}.tar.xz
 Source6: gdbtui
 
 # libipt: Intel Processor Trace Decoder Library
-%global libipt_version 2.0.1
+%global libipt_version 2.0.2
 #=fedora
 Source7: v%{libipt_version}.tar.gz
 #=fedora
@@ -1186,6 +1186,9 @@ fi
 %endif
 
 %changelog
+* Tue Aug 04 2020 Keith Seitz <keiths@redhat.com>
+- Update libipt to v2.0.2.
+
 * Sat Aug 01 2020 Fedora Release Engineering <releng@fedoraproject.org>
 - Second attempt - Rebuilt for
   https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild

diff --git a/sources b/sources
index 4c89a9f..2a3425d 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
 SHA512 (gdb-libstdc++-v3-python-8.1.1-20180626.tar.xz) = a8b1c54dd348cfeb37da73f968742896be3dd13a4215f8d8519870c2abea915f5176c3fa6989ddd10f20020a16f0fab20cbae68ee8d58a82234d8778023520f8
-SHA512 (v2.0.1.tar.gz) = e38e93908c3fbf1f2384cfca381eaf4bf667033de678041bd440adac8bbce4757b77304868896256ed72c202ee22ba1646aada90125029f14f5bffaf828a7df4
+SHA512 (v2.0.2.tar.gz) = bc256a57a8481e0be8220624da3ccf1fe4bf0ea83e9808fdf0aad6db865aee402a36e78285efb0316c016f57e0d6fc56b647ee8e9a2ad4b05bfc1ad68ddde535
 SHA512 (gdb-9.2.tar.xz) = 73635f00f343117aa5e2436f1e1597099e2bfb31ef7bb162b273fa1ea282c3fa9b0f52762e70bfc7ad0334addb8d159e9ac7cbe5998ca4f755ea8cf90714d274

                 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=178260480353.1.5785803636199988919.rpms-gdb-ab7962ace7dc@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