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.
Description of problem:
error: Installed (but unpackaged) file(s) found:
/usr/share/systemtap/tapset/glib.stp
/usr/share/systemtap/tapset/gobject.stp
Version-Release number of selected component (if applicable):
glib2-2.26.0-3.el6
How reproducible:
100%
Steps to Reproduce:
1.
2.
3.
Actual results:
unpackaged files
Expected results:
there should be no unpackaget files
Additional info:
Hm; I'm guessing something pulled systemtap into the buildroot since Matthew did the rebase here? Regardless, the tap scrips to the best of my knowledge are not tested extensively in Fedora, so we should probably be conservative and not ship them in RHEL6.
(In reply to Colin Walters from comment #1)
> Hm; I'm guessing something pulled systemtap into the buildroot since Matthew
> did the rebase here? Regardless, the tap scrips to the best of my knowledge
> are not tested extensively in Fedora, so we should probably be conservative
> and not ship them in RHEL6.
So shouldn't we just remove them in post phase?
Tom
Colin one more thought.
Seems these files are going to be created only in case is it build on system with SystemTap. Without it I believe they will not appear. So the configure script may automatically expect system without SystemTap.
That might cause confusion.
Tom
(In reply to Tomas Pelka from comment #4)
> Colin one more thought.
>
> Seems these files are going to be created only in case is it build on system
> with SystemTap. Without it I believe they will not appear. So the configure
> script may automatically expect system without SystemTap.
The configure options should always win; if we say --disable-systemtap, it shouldn't complain at us if the buildroot happens to contain systemtap. And that is how the code works.
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.
http://rhn.redhat.com/errata/RHBA-2013-1545.html