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:
matej@mitmanek: ~$ gdbus-codegen --help
Traceback (most recent call last):
  File "/bin/gdbus-codegen", line 41, in <module>
    from codegen import codegen_main
ImportError: No module named codegen
matej@mitmanek: ~$

Version-Release number of selected component (if applicable):
glib2-devel-2.54.0-1.el7_4.x86_64

How reproducible:
100%

Additional info:
The problem lies in the /bin/gdbus-codegen script itself:

elif os.path.basename(filedir) == 'bin':
    # Make the prefix containing gdbus-codegen 'relocatable' at runtime by
    # adding /some/prefix/bin/../share/glib-2.0 to the python path
    path = os.path.join(filedir, '..', 'share', 'glib-2.0')

must fail to do The Right Thing™ when it is in /bin/ instead of /usr/bin/ as apparently expected.

Created attachment 1345637 [details]
proposed patch

Thanks for the bug report and patch!  I did a quick annotate on git upstream and
saw:

https://git.gnome.org/browse/glib/commit/?id=b9f2ea423526735f7fe7371fb1339eae91a618c2

Let's backport that instead?

(In reply to Colin Walters from comment #3)
> Thanks for the bug report and patch!  I did a quick annotate on git upstream
> and saw:
> 
> https://git.gnome.org/browse/glib/commit/
> ?id=b9f2ea423526735f7fe7371fb1339eae91a618c2
> 
> Let's backport that instead?

Sounds a way better. That algorithm of looking for the proper dir with libraries is in my opinion too brittle, and after all when building the package we know where all those files will go.

We actually need https://bugzilla.gnome.org/show_bug.cgi?id=789723 too.

Not going to go through the hoops to get a pm_ack for this, it should be fixed in the current build, please reopen/comment/send smoke signal it still doesn't work or there are any other issues.  Thanks!

Note the same issue appeared in bug 1485853 on the Fedora side.

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-2018:0770