public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: * Mon May  5 2014 Sergio Durigan Junior <sergiodj@redhat.com> - 7.7-9.fc21
Date: Sat, 27 Jun 2026 23:56:32 GMT	[thread overview]
Message-ID: <178260459204.1.15167666411457762011.rpms-gdb-0a42762f26f5@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/gdb
            Branch : gdb-17.2-rebase-f44
            Commit : 0a42762f26f5fa905ba98cc55b64b0cd39df4ddf
            Author : Sergio Durigan Junior <sergiodj@redhat.com>
            Date   : 2014-05-05T18:44:10-03:00
            Stats  : +23/-16 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/gdb/c/0a42762f26f5fa905ba98cc55b64b0cd39df4ddf?branch=gdb-17.2-rebase-f44

            Log:
            * Mon May  5 2014 Sergio Durigan Junior <sergiodj@redhat.com> - 7.7-9.fc21
- Improve testcase message for RH BZ 981154.

---
diff --git a/gdb-6.6-buildid-locate-misleading-warning-missing-debuginfo-rhbz981154.patch b/gdb-6.6-buildid-locate-misleading-warning-missing-debuginfo-rhbz981154.patch
index b7c47e3..044a408 100644
--- a/gdb-6.6-buildid-locate-misleading-warning-missing-debuginfo-rhbz981154.patch
+++ b/gdb-6.6-buildid-locate-misleading-warning-missing-debuginfo-rhbz981154.patch
@@ -19,7 +19,7 @@ Index: gdb-7.7/gdb/testsuite/gdb.base/rhbz981154-misleading-yum-install-warning.
 ===================================================================
 --- /dev/null
 +++ gdb-7.7/gdb/testsuite/gdb.base/rhbz981154-misleading-yum-install-warning.exp
-@@ -0,0 +1,93 @@
+@@ -0,0 +1,97 @@
 +#   Copyright (C) 2014  Free Software Foundation, Inc.
 +
 +# This program is free software; you can redistribute it and/or modify
@@ -80,15 +80,17 @@ Index: gdb-7.7/gdb/testsuite/gdb.base/rhbz981154-misleading-yum-install-warning.
 +gdb_start
 +gdb_reinitialize_dir $srcdir/$subdir
 +
-+gdb_test "set build-id-verbose 1" "" \
-+    "set build-id-verbose"
++with_test_prefix "first run:" {
++    gdb_test "set build-id-verbose 1" "" \
++	"set build-id-verbose"
 +
-+gdb_test "set debug-file-directory ${objdir}/${subdir}" "" \
-+    "set debug-file-directory to ${objdir}/${subdir}"
++    gdb_test "set debug-file-directory ${objdir}/${subdir}" "" \
++	"set debug-file-directory"
 +
-+gdb_test "core-file ${objdir}/${subdir}/gcore.test" \
-+    "Missing separate debuginfo for the main executable file\r\nTry: yum --enablerepo='\\*debug\\*' install $objdir/$subdir/$build_id_without_debug\r\n.*" \
-+    "test first yum warning to install $objdir/$subdir/$build_id_without_debug"
++    gdb_test "core-file ${objdir}/${subdir}/gcore.test" \
++	"Missing separate debuginfo for the main executable file\r\nTry: yum --enablerepo='\\*debug\\*' install $objdir/$subdir/$build_id_without_debug\r\n.*" \
++	"test first yum warning"
++}
 +
 +# Now we define and create our .build-id
 +file mkdir [file dirname ${objdir}/${subdir}/${build_id_without_debug}]
@@ -101,15 +103,17 @@ Index: gdb-7.7/gdb/testsuite/gdb.base/rhbz981154-misleading-yum-install-warning.
 +gdb_start
 +gdb_reinitialize_dir $srcdir/$subdir
 +
-+gdb_test "set build-id-verbose 1" "" \
-+    "set build-id-verbose"
++with_test_prefix "second run:" {
++    gdb_test "set build-id-verbose 1" "" \
++	"set build-id-verbose"
 +
-+gdb_test "set debug-file-directory ${objdir}/${subdir}" "" \
-+    "set debug-file-directory to ${objdir}/${subdir}"
++    gdb_test "set debug-file-directory ${objdir}/${subdir}" "" \
++	"set debug-file-directory"
 +
-+gdb_test "core-file ${objdir}/${subdir}/gcore.test" \
-+    "Missing separate debuginfo for the main executable file\r\nTry: yum --enablerepo='\\*debug\\*' install $binfile\r\n.*" \
-+    "test second yum warning to install $binfile"
++    gdb_test "core-file ${objdir}/${subdir}/gcore.test" \
++	"Missing separate debuginfo for the main executable file\r\nTry: yum --enablerepo='\\*debug\\*' install $binfile\r\n.*" \
++	"test second yum warning"
++}
 +
 +# Leaving the link there will cause breakage in the next run.
 +remote_exec build "rm -f ${objdir}/${subdir}/${build_id_without_debug}"

diff --git a/gdb.spec b/gdb.spec
index 6ae8c63..6d27e79 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -39,7 +39,7 @@ Version: 7.7
 
 # 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: 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
@@ -1382,6 +1382,9 @@ fi
 %endif # 0%{!?el5:1} || "%{_target_cpu}" == "noarch"
 
 %changelog
+* Mon May  5 2014 Sergio Durigan Junior <sergiodj@redhat.com> - 7.7-9.fc21
+- Improve testcase message for RH BZ 981154.
+
 * Mon May  5 2014 Jan Kratochvil <jan.kratochvil@redhat.com> - 7.7-8.fc21
 - Fix TLS access for -static -pthread (BZ 1080660).
 

                 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=178260459204.1.15167666411457762011.rpms-gdb-0a42762f26f5@fedoraproject.org \
    --to=sergiodj@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