Bugzilla – Bug 1020109
multimedia:color_management: Bug - 'zypper up' gives a warning
Last modified: 2018-03-15 11:27:21 UTC
I run 'zypper up' almost daily. This is the firs time I see a message like this one: (12/12) Installing: libelektra4-0.8.19-6.1.x86_64 ...........................................................................................[done] Additional rpm output: The command global-mount failed while accessing the key database with the info: Sorry, 1 warning was issued ;( Warning (#1): Description: could not load module, dlopen failed Ingroup: modules Module: dl At: /home/abuild/rpmbuild/BUILD/elektra-0.8.19/src/libs/loader/dl.c:88 Reason: of module: libelektra-resolver.so, because: libelektra-resolver.so: cannot open shared object file: No such file or directory Mountpoint: Configfile: Sorry, the error (#40) occurred ;( Description: failed to open default backend (see warnings for more information) Ingroup: kdb Module: At: /home/abuild/rpmbuild/BUILD/elektra-0.8.19/src/libs/elektra/kdb.c:287 Reason: could not open default backend Mountpoint: Configfile: There is no such thing as '/home/abuild' at all. There has never been, no such user whatsoever. Here is the full output: http://paste.opensuse.org/87e694b7 --- I have been advised to report as a bug in this forum thread: https://forums.opensuse.org/showthread.php/522352-zypper-up-gives-a-strange-warning Thanks.
Thanks for reporting. Meanwhile the package was updated some days ago. The following call is fine in Tumbleweed without errors: $ zypper install libelektra4 libelektra4-0.8.19-6.2.x86_64 gets installed. It looks like the error is already present in the build logs for 42.1. The change introducing to fix usage of libelektra4 is in rev6: https://build.opensuse.org/package/rdiff/multimedia:color_management/elektra?linkrev=base&rev=6 @@ -193,11 +193,13 @@ #rm $RPM_BUILD_ROOT%{_bindir}/kdb-static # not known by any package? rm -r $RPM_BUILD_ROOT%{_datadir}/zsh/vendor-completions/ +# add elektra modules paths +mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/ld.so.conf.d/ +echo "%{_libdir}/elektra%{api}" > $RPM_BUILD_ROOT%{_sysconfdir}/ld.so.conf.d/elektra.conf %post -n lib%{name}%{api} /sbin/ldconfig # activate dbus messages on db changes -export LD_LIBRARY_PATH=%{_libdir}/elektra%{api}/:$LD_LIBRARY_PATH %{_bindir}/kdb global-mount dbus || : %postun -n lib%{name}%{api} -p /sbin/ldconfig @@ -220,6 +222,7 @@ %{_libdir}/elektra%{api}/*elektra-[b-z]*.so %dir %{_datadir}/doc/elektra %{_datadir}/doc/elektra/* +%{_sysconfdir}/ld.so.conf.d/elektra.conf %if 0%{?use_qt5} > 0 %files -n %{name}-qt-gui %{_sysconfdir}/ld.so.conf.d/elektra.conf is considered to be loaded by ldconfig and make the libelektra-resolver.so module visible to the dynamic library loader for the kdb tool from the script. I have on glue why this scheme does not work.
package install appears to fail in 42.1. while it is fine in Tumbleweed
Thanks for the feedback. So is there anything to do on my end or should I simply wait that to be resolved? Thanks.
This should've been fixed on its own now. At least it does not error out when I test it on currently supported leap release.