Hi Cristian, On Sat, Nov 22, 2014 at 09:45:39PM -0300, Cristian Rodríguez wrote:
El 17/11/14 a las 18:39, Sid Boyce escribió:
tindog:~ # strace -s 256 -f systemctl status wickedd ioctl(1, TIOCGWINSZ, {ws_row=48, ws_col=271, ws_xpixel=0, ws_ypixel=0}) = 0 write(1, "Nov 17 21:02:43 tindog wickedd[655]: \33[1;31mlibgcrypt version mismatch\33[0m\n", 75Nov 17 21:02:43 tindog wickedd[655]: libgcrypt version mismatch ) = 75 munmap(0x7fe838da0000, 8388608) = 0 munmap(0x7fe83ad40000, 4096) = 0 close(6) = 0 close(3) = 0 exit_group(0) = ? +++ exited with 0 +++
This is in any case a bug.. why in hell is doing that ? it should either rely on the shared library symbol versioning being correct or require exactly the libgcrypt version used for build in the spec file.. attached there is a patch to avoid this issue in the future...
Thanks for the patch. We have the following in the pipeline to address this: https://github.com/openSUSE/wicked/pull/464 As it stands now, libgcrypt20-1.6.2 has been released as an update so the versioning should align without the need for any manual touch-ups. Regards, Karol