Changelog for liblognorm5-2.0.6-3.1.x86_64.rpm :

* Mon Aug 20 2018 jgerhardsAATTadiscon.com- liblognorm 2.0.4:
* bugfix: es_str2cstr leak in string-to v1 parser Thanks to Harshvardhan Shrivastava for the patch.
* make \"make check\" \"succeed\" on solaris 10 actually, we just ignore the CI failures so that OpenCSW can build new packages. The problems actually exist on that platform, but testing has shown they always existed. We currently run out of time to really fixing this, plus we never had any bug report on Solaris (I assme nobody uses it on Solaris 10). However, that issues is a blocker to make new rsyslog versions available on OpenCSW for Solaris 10, so we go the dirty way of pretenting there is no problem. Note: the issues was orignally not seen, as the failing tests have been added later on. So the problem was always there, just not visible.
* some mostly cosmetic fixes detected by Coverity Scan e. g. memory leak if and only if system was completely out of memory- remove liblognorm-2.0.4-no-return-in-nonvoid-function.patch fixed upstream.
* Tue Nov 14 2017 astiegerAATTsuse.com- liblognorm 2.0.4:
* added support for native JSON number formats supported by parsers: number, float, hex
* added support for creating unix timestamps supported by parsers: date-rfc3164, date-rfc5424- add liblognorm-2.0.4-no-return-in-nonvoid-function.patch
* Fri May 05 2017 jmatejekAATTsuse.com- drop HTML docs and python-Sphinx dependency- use pkgconfig always
* Tue Apr 04 2017 astiegerAATTsuse.com- liblognorm 2.0.3:
* add ability to load rulebase from a string
* string parser did not correctly parse word at end of line
* literal parser did not always store value if name is specified
* Mon Jan 30 2017 ndasAATTsuse.com- This updated library is needed for latest rsyslog(fate#320546)
* Sun Dec 04 2016 astiegerAATTsuse.com- liblognorm 2.0.2:
* bugfix: no error was emitted on invalid \"annotate\" line
* \"annnotate\": permit inline comments
* bugfix: abort in literal path compaction when using \"alternative\" parser
* bugfix: lognormalizer could loop