+++ This bug was initially created as a clone of Bug #1533176 +++ Description of problem: - recent gdbm update to 1.14 seems to be incompatible with the current build of python in fedora Version-Release number of selected component (if applicable): this applies both to python2 and python3 How reproducible: # rpm -q gdbm python3 python2 gdbm-1.14-1.fc27.x86_64 python3-3.6.2-13.fc27.x86_64 python2-2.7.14-4.fc27.x86_64 # python2 -c 'import gdbm' Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: /usr/lib64/python2.7/lib-dynload/gdbmmodule.so: undefined symbol: gdbm_errno # python3 -c 'import dbm.gnu' Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib64/python3.6/dbm/gnu.py", line 3, in <module> from _gdbm import * ImportError: /usr/lib64/python3.6/lib-dynload/_gdbm.cpython-36m-x86_64-linux-gnu.so: undefined symbol: gdbm_errno --- Additional comment from Fedora Update System on 2018-01-15 08:19:24 EST --- gdbm-1.13-5.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ec4df5a741
What is the purpose of this cloned bug?
I thought original bug was for F27, so I wanted to have this bug for Rawhide too to remind me to contact packagers to rebuild dependent packages. No need for this bug more. gdbm 1.14 stays in Rawhide, packagers were contacted by email to rebuild their packages. If not, packages will be rebuilt on Mass Rebuild.