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.

Bug 1139274

Summary: glib2 rebase leads to crashers after packages are rebuilt against it
Product: Red Hat Enterprise Linux 6 Reporter: Ray Strode [halfline] <rstrode>
Component: glib2Assignee: Matthew Barnes <mbarnes>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6CC: cfergeau, danw, desktop-qa-list, marcandre.lureau, mkasik, msimon, oholy, tlavigne, tpelka, walters
Target Milestone: betaKeywords: Rebase
Target Release: 6.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glib2-2.28.8-3.el6 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: 1101398 Environment:
Last Closed: 2014-10-14 07:29:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1101398    
Bug Blocks: 1033151, 1100886, 1101399, 1101418, 1113189, 1127304, 1641312    
Attachments:
Description Flags
Reverts all deprecations back to glib-2.22 walters: review+

Comment 1 Matthew Barnes 2014-09-08 14:10:14 UTC
Created attachment 935360 [details]
Reverts all deprecations back to glib-2.22

Comment 2 Colin Walters 2014-09-08 14:30:38 UTC
Comment on attachment 935360 [details]
Reverts all deprecations back to glib-2.22

I'm OK with this patch.

Comment 4 Colin Walters 2014-09-08 16:26:16 UTC
However, two things should happen for all client programs using glib2:

1) Stop using -DG_DISABLE_DEPRECATED.  See: https://bugzilla.redhat.com/show_bug.cgi?id=1104372#c6

2) Ensure they *do* use  -Werror=implicit-function-declaration.  Every C program should opt out of the completely braindead legacy default behavior.

Comment 6 Ray Strode [halfline] 2014-09-08 17:57:49 UTC
Note bug 1104372 comment 6 is a rhel7 bug, this is a rhel6 bug.

I agree with 1) though, within reason.  What I mean is, we can't fix customer programs, and we can't easily fix programs that aren't on the approved components list (since we don't have QA resources to test them).  In this case, the only known offender is devhelp, which has been fixed independently.

As for 2, I agree with that, too, though, from a rhel perspective, it should probably be added to the default CFLAGS.

Comment 7 errata-xmlrpc 2014-10-14 07:29:04 UTC
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-2014-1538.html