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: Fix#2 /usr/share/gdb/system-gdbinit/ timestamps causing non-matching *.py[oc].
Date: Sat, 27 Jun 2026 23:56:37 GMT	[thread overview]
Message-ID: <178260459742.1.3709901235060437245.rpms-gdb-b472cbae9c15@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : b472cbae9c15ec178cb3e768392246635b749403
Author : Jan Kratochvil <jan.kratochvil@redhat.com>
Date   : 2014-06-03T20:57:43+02:00
Stats  : +8/-7 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/gdb/c/b472cbae9c15ec178cb3e768392246635b749403?branch=gdb-17.2-rebase-f44

Log:
Fix#2 /usr/share/gdb/system-gdbinit/ timestamps causing non-matching *.py[oc].

---
diff --git a/gdb.spec b/gdb.spec
index 7a5982b..cea807f 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -27,7 +27,7 @@ Version: 7.7.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: 19%{?dist}
+Release: 20%{?dist}
 
 License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ and GPLv2+ with exceptions and GPL+ and LGPLv2+ and BSD and Public Domain and GFDL
 Group: Development/Debuggers
@@ -1154,14 +1154,8 @@ done
 test ! -e $RPM_BUILD_ROOT%{_datadir}/gdb/python/libstdcxx
 cp -a $RPM_BUILD_DIR/%{gdb_src}/%{libstdcxxpython}/libstdcxx	\
       $RPM_BUILD_ROOT%{_datadir}/gdb/python/libstdcxx
-for i in `find $RPM_BUILD_ROOT%{_datadir}/gdb -name "*.py"`; do
-  # Files come from gdb-archer.patch and can be also further patched.
-  # They are also installed by install(1) not preserving the timestamps.
-  touch -r $RPM_BUILD_DIR/%{gdb_src}/gdb/ChangeLog $i
-done
 %else # 0%{!?rhel:1} || 0%{?rhel} > 6
 # BZ 999645: /usr/share/gdb/auto-load/ needs filesystem symlinks
-mkdir -p $RPM_BUILD_ROOT%{_datadir}/gdb/auto-load
 for i in $(echo bin lib $(basename %{_libdir}) sbin|tr ' ' '\n'|sort -u);do
   # mkdir to satisfy dangling symlinks build check.
   mkdir -p $RPM_BUILD_ROOT%{_datadir}/gdb/auto-load/%{_root_prefix}/$i
@@ -1169,6 +1163,10 @@ for i in $(echo bin lib $(basename %{_libdir}) sbin|tr ' ' '\n'|sort -u);do
         $RPM_BUILD_ROOT%{_datadir}/gdb/auto-load/$i
 done
 %endif # 0%{!?rhel:1} || 0%{?rhel} > 6
+for i in `find $RPM_BUILD_ROOT%{_datadir}/gdb -name "*.py"`; do
+  # Files are installed by install(1) not preserving the timestamps.
+  touch -r $RPM_BUILD_DIR/%{gdb_src}/gdb/ChangeLog $i
+done
 %endif # 0%{!?_without_python:1}
 
 # gdb-add-index cannot be run even for SCL package on RHEL<=6.
@@ -1310,6 +1308,9 @@ then
 fi
 
 %changelog
+* Tue Jun  3 2014 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.7.1-20.fc21
+- Fix#2 /usr/share/gdb/system-gdbinit/ timestamps causing non-matching *.py[oc].
+
 * Tue Jun  3 2014 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.7.1-19.fc21
 - Fix /usr/share/gdb/auto-load/ (safely) dangling symlinks.
 - Fix /usr/share/gdb/system-gdbinit/ timestamps causing non-matching *.py[oc].

                 reply	other threads:[~2026-06-27 23:56 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=178260459742.1.3709901235060437245.rpms-gdb-b472cbae9c15@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