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.

We are planning a desktop rebase to GNOME 3.14.x in 7.2. libgsystem should be rebased to the release that is used with that gnome release, 2014.2

libgsystem isn't in RHEL right now (but it is in the Atomic content set).

What about backporting the patches to drop the dependency?

Alternatively, are there any other new packages that need to be pulled in for the 7.2 desktop rebase?  Is there a tracker bug for that?  What's the process?

(In reply to Colin Walters from comment #3)
> libgsystem isn't in RHEL right now (but it is in the Atomic content set).
> 
> What about backporting the patches to drop the dependency?
> 
> Alternatively, are there any other new packages that need to be pulled in
> for the 7.2 desktop rebase?  Is there a tracker bug for that?  What's the
> process?

I'm in favor of backporting the patches. Thanks for pointing this out.

What are the packages that pull it in, just gnome-desktop3 ?

I've added a note to bug 1174445 and bug 1174538

Upstream link to deprecation: https://mail.gnome.org/archives/desktop-devel-list/2015-February/msg00120.html