Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2041
Michal Kolar spotted that gdb-7.6.1-94.el7.src.rpm doesn't rebuild when all the devtoolset-6 RPMs are installed. The failure looks like this: ======= + echo 'Patch #836 (gdb-upstream-framefilters-1of2.patch):' Patch #836 (gdb-upstream-framefilters-1of2.patch): + /usr/bin/cat /root/rpmbuild/SOURCES/gdb-upstream-framefilters-1of2.patch + /usr/bin/patch -p1 --fuzz=0 -R patching file gdb/Makefile.in Hunk #3 succeeded at 2179 (offset 5 lines). patching file gdb/NEWS Hunk #1 FAILED at 4. 1 out of 1 hunk FAILED -- saving rejects to file gdb/NEWS.rej patching file gdb/stack.c Hunk #2 succeeded at 1676 (offset 21 lines). Hunk #3 succeeded at 1701 (offset 21 lines). Hunk #4 succeeded at 1722 (offset 21 lines). Hunk #5 succeeded at 1744 (offset 21 lines). Hunk #6 succeeded at 1769 (offset 21 lines). Hunk #7 succeeded at 1794 (offset 21 lines). Hunk #8 succeeded at 1811 (offset 21 lines). Hunk #9 succeeded at 1841 (offset 21 lines). Hunk #10 succeeded at 1849 (offset 21 lines). Hunk #11 succeeded at 2583 (offset 21 lines). patching file gdb/data-directory/Makefile.in patching file gdb/doc/gdb.texinfo Hunk #5 succeeded at 23135 (offset 35 lines). Hunk #6 succeeded at 24485 (offset 35 lines). Hunk #7 succeeded at 25315 (offset 35 lines). Hunk #8 succeeded at 25365 (offset 35 lines). Hunk #9 succeeded at 26383 (offset 35 lines). Hunk #10 succeeded at 30260 (offset 41 lines). Hunk #11 succeeded at 30327 (offset 41 lines). Hunk #12 succeeded at 30350 (offset 41 lines). Hunk #13 succeeded at 30421 (offset 41 lines). Hunk #14 succeeded at 30457 (offset 41 lines). Hunk #15 succeeded at 30527 (offset 41 lines). Hunk #16 succeeded at 30542 (offset 41 lines). Hunk #17 succeeded at 30567 (offset 41 lines). Hunk #18 succeeded at 30581 (offset 41 lines). patching file gdb/mi/mi-cmd-stack.c patching file gdb/mi/mi-cmds.c patching file gdb/mi/mi-cmds.h patching file gdb/python/py-framefilter.c Unreversed patch detected! Ignore -R? [n] ======= Closer look shows that the culprit is devtoolset-6-build that, when installed, defines the %{scl} rpm macro: ======= 7.4 Server x86_64 # rpm --eval '%{scl}' devtoolset-6 7.4 Server x86_64 # ======= ... which drives following specfile condition: ======= %if 0%{?scl:1} %patch836 -p1 -R %patch837 -p1 -R %patch998 -p1 -R %endif ======= Apparently, when %{scl} is defined, then patch 836 (gdb-upstream-framefilters-1of2.patch) collides with patch 1017 (gdb-rhbz1105165-ibm-tdb-support-system-z-3of9.patch). Both of them are trying to modify the NEWS file. IOW, after applying 836 and 1017 on top of it, patch 863 can't be reverted (-R) any more: ======= 7.4 Server x86_64 # cat gdb.spec | egrep '%patch(836|1017)' %patch836 -p1 %patch1017 -p1 %patch836 -p1 -R 7.4 Server x86_64 # ======= Observed with gdb-7.6.1-94.el7.src.rpm.