On Thu, Nov 02, 2017 at 07:52:25AM +, Radovan Sroka wrote:
> 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
On Thursday, 02 November 2017 at 08:52, Radovan Sroka wrote:
[...]
> libfastjson is rsyslog specific library. So it shouldn't break anything else.
A quick repoquery reveals one more consumer at least on F26:
# dnf repoquery --whatrequires "libfastjson.so.4()(64bit)"
On Thursday, 02 November 2017 at 04:36, Troy Curtis Jr wrote:
[...]
> 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
>
"So it shouldn't break anything else."
On Thu, Nov 2, 2017 at 8:52 AM Radovan Sroka wrote:
> 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
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
On Wed, Nov 1, 2017 at 5:49 PM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> 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
Dear Fedora,
it looks like the libfastjson-0.99.7 update that was submitted as an
update for all branches contained an unannounced ABI break:
$ abipkgdiff --d1 libfastjson-debuginfo-0.99.6-1.fc26.x86_64.rpm --d2
libfastjson-debuginfo-0.99.7-1.fc26.x86_64.rpm --devel1