Require glib2 version with g_once_init_enter_pointer symbol #1645
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
glib2-2.79.0-2.fc40 added g_once_init_enter_pointer symbol and started
to implant a reference on the symbol into applications via
macros/in-lined functions included from glib2 header files. As
a result, people upgrading to libdnf built against new glib2 but
not upgrading glib2 at the same time will break dynamic linking of
libdnf:
Traceback (most recent call last):
File "/usr/bin/dnf-3", line 61, in <module>
from dnf.cli import main
File "/usr/lib/python3.12/site-packages/dnf/__init__.py", line 30, in <module>
import dnf.base
File "/usr/lib/python3.12/site-packages/dnf/base.py", line 29, in <module>
import libdnf.transaction
File "/usr/lib64/python3.12/site-packages/libdnf/__init__.py", line 14, in <module>
from . import conf
File "/usr/lib64/python3.12/site-packages/libdnf/conf.py", line 10, in <module>
from . import _conf
ImportError: /lib64/libdnf.so.2: undefined symbol: g_once_init_enter_pointer
If glib2 versioned its symbols, rpm-build would inject an RPM
dependency on the new glib2 versioned SONAME. However, this is not
true, so we need to add a dependency on a minimal glib2 version
manually.
This issue is specific to not fully upgraded Fedora 40--41.
This issue materializes in real life when mock installs a new libdnf into a
bootstrap image based on a container image created before glib2-2.79.0-2.fc40
https://bugzilla.redhat.com/show_bug.cgi?id=2265336
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
glib2-2.79.0-2.fc40 added g_once_init_enter_pointer symbol and started to implant a reference on the symbol into applications via macros/in-lined functions included from glib2 header files. As a result, people upgrading to libdnf built against new glib2 but not upgrading glib2 at the same time will break dynamic linking of libdnf:
If glib2 versioned its symbols, rpm-build would inject an RPM dependency on the new glib2 versioned SONAME. However, this is not true, so we need to add a dependency on a minimal glib2 version manually.
This issue is specific to not fully upgraded Fedora 40--41. This issue materializes in real life when mock installs a new libdnf into a bootstrap image based on a container image created before glib2-2.79.0-2.fc40
https://bugzilla.redhat.com/show_bug.cgi?id=2265336