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.

Created attachment 1196083 [details]
Example program

Description of problem:
When trying to link a program against ostree-devel, this is impossible because the libgsystem in the atomic host repository is missing various symbols.

Version-Release number of selected component (if applicable):
ostree-2016.7-2.atomic.el7.x86_64
ostree-devel-2016.7-2.atomic.el7.x86_64
libgsystem-2015.1-1.atomic.el7.x86_64

How reproducible:
Consistent

Steps to Reproduce:
1. Grab the source code attached
2. Run gcc `pkg-config --libs --cflags ostree-1` input.c

Actual results:
/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/libostree-1.so: undefined reference to `g_file_enumerator_iterate'
collect2: error: ld returned 1 exit status

Expected results:
Compiled a.out.

Additional info:

The symbol is be in glib2.
Glib2 version:
glib2-2.42.2-5.el7.x86_64

Sorry, wrong glib2 version.
This issue is fixed in 2.46.

So, this is an actual bug, in that rpm allowed me to install this set.
I guess that the ostree spec is missing a version specification for the glib2 dependency.

I was surprised to see that glib doesn't use versioned symbols, which lead me to: <https://mail.gnome.org/archives/desktop-devel-list/2010-May/msg00075.html>.

Anyway, specifically for this, it seems like we should just hard require whatever version we were compiled against since the backports are determined at compile time. Though that would be really annoying to maintain in the dist-gits since different Fedora/RHEL releases have different glib2 versions. Not sure if there's an RPM spec trick we can use here to avoid this.

*** Bug 1458819 has been marked as a duplicate of this bug. ***

Created attachment 1285131 [details]
Add versioned runtime req on glib2

Should be fixed in 7.4.