Hi Guys,
libfastjson is rsyslog specific library. So it should break anything else. I did a mistake because I didn't group updates for libfastjson and for rsyslog. Rsyslog was broken yesterday on fedora 26 but now it should be everything OK. I will be really careful with other branches and also with another updates in future.On Thu, Nov 2, 2017 at 4:36 AM Troy Curtis Jr <troycurtisjr@xxxxxxxxx> wrote:
On Wed, Nov 1, 2017 at 5:49 PM Dominik 'Rathann' Mierzejewski <dominik@xxxxxxxxxxxxxx> wrote:Dear Fedora,..snip..
This breaks, for example, rsyslog-8.30.0-3, which was compiled against
libfastjson-0.99.7, but didn't go out together with it, so when I ran
dnf update, the set contained only new rsyslog, which, when run with
libfastjson-0.99.6 (same SONAME!) simply dies:
# rsyslogd -n
rsyslogd: symbol lookup error: rsyslogd: undefined symbol: fjson_global_do_case_sensitive_comparison
Dear maintainers, please use abipkgdiff when doing library updates.
Upstreams do break ABI without bumping SONAME sometimes.
I'm not sure if it is a real issue or not. A user in #fedora got bit by this where his rsyslog was upgraded but not his libfastjson. Updating to libfastjson-0.99.7 allowed rsyslog to startup and begin logging. But it appeared to die quickly. This happened at least twice.There could be other things going on with his setup, but I thought I'd point out a potential issue to be on the lookout for even if the missing symbol has been resolved.Troy
--
--
---------------------------------------------------------
Radovan Sroka
Associate Software Engineer | Security Technologies | Red hat, Inc.
---------------------------------------------------------
Radovan Sroka
Associate Software Engineer | Security Technologies | Red hat, Inc.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
