Package: liblognorm2 Version: 1.1.1-1 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch
liblognorm2 is marked as "Multi-Arch: same", but the following file is architecture-dependent:
/usr/share/doc/liblognorm2/changelog.gz MD5 sums of the file are: 00f3991240b6970f0175eb13e10743ad on amd64; ea58d876f4362191c3f1c1152f86bbbd elsewhere. An example diff between i386 and amd64 (after ungzipping) is attached. -- Jakub Wilk
diff -ur liblognorm2_1.1.1-1_i386/usr/share/doc/liblognorm2/changelog liblognorm2_1.1.1-1_amd64/usr/share/doc/liblognorm2/changelog --- liblognorm2_1.1.1-1_i386/usr/share/doc/liblognorm2/changelog 2014-09-26 09:57:08.000000000 +0200 +++ liblognorm2_1.1.1-1_amd64/usr/share/doc/liblognorm2/changelog 2015-05-07 00:25:28.000000000 +0200 @@ -1,7 +1,108 @@ -ChangeLog -========= - -See below for a list of changes. - -.. literalinclude:: ../ChangeLog - +---------------------------------------------------------------------- +Version 1.1.1, 2015-03-09 +- fixed library version numbering + Thanks to Tomas Heinreich for reporting the problem. +- added new parser syntaxes + Thanks to Janmejay Singh for implementing most of them. +- bugfix: function ln_parseFieldDescr() returns state value + due to unitialized variable. This can also lead to invalid + returning no sample node where one would have to be created. +---------------------------------------------------------------------- +Version 1.1.0, 2015-01-08 +- added regular expression support + use this feature with great care, as it thrashes performance + Thanks to Janmejay Singh for implementing this feature. +- fix build problem when --enable-debug was set + closes: https://github.com/rsyslog/liblognorm/issues/5 +---------------------------------------------------------------------- +Version 1.0.1, 2014-04-11 +- improved doc (via RST/Sphinx) +- bugfix: unparsed fields were copied incorrectly from non-terminated + string. Thanks to Josh Blum for the fix. +- bugfix: mandatory tag did not work in lognormalizer +---------------------------------------------------------------------- +Version 1.0.0, 2013-11-28 +- WARNING: this version has incompatible interface and older programs + will not compile with it. + For details see http://www.liblognorm.com/news/on-liblognorm-1-0-0/ +- libestr is not used any more in interface functions. Traditional + C strings are used instead. Internally, libestr is still used, but + scheduled for removal. +- libee is not used any more. JSON-C is used for object handling + instead. Parsers and formatters are now part of liblognorm. +- added new field type "rest", which simply sinks all up to end of + the string. +- added support for glueing two fields together, without literal + between them. It allows for constructs like: + %volume:number%%unit:word% + which matches string "1000Kbps" +- Fix incorrect merging of trees with empty literal at end + Thanks to Pavel Levshin for the patch +- this version has survived many bugfixes +---------------------------------------------------------------------- +================================================================================ +The versions below is liblognorm0, which has a different API +================================================================================ +---------------------------------------------------------------------- +Version 0.3.7, 2013-07-17 +- added support to load single samples + Thanks to John Hopper for the patch +---------------------------------------------------------------------- +Version 0.3.6, 2013-03-22 +- bugfix: unitialized variable could lead to rulebase load error +---------------------------------------------------------------------- +Version 0.3.5 (rgerhards), 2012-09-18 +- renamed "normalizer" tool to "lognormalizer" to solve name clashes + Thanks to the Fedora folks for pointing this out. +---------------------------------------------------------------------- +Version 0.3.4 (rgerhards), 2012-04-16 +- bugfix: normalizer tool had a memory leak + Thanks to Brian Know for alerting me and helping to debug +---------------------------------------------------------------------- +Version 0.3.3 (rgerhards), 2012-02-06 +- required header file was not installed, resulting in compile error + closes: http://bugzilla.adiscon.com/show_bug.cgi?id=307 + Thanks to Andreis Vinogradovs for alerting us on this bug. +---------------------------------------------------------------------- +Version 0.3.2 (rgerhards), 2011-11-21 +- added rfc5424 parser (requires libee >= 0.3.2) +- added "-" to serve as name for filler fields. Value is extracted, + but no field is written +- special handling for iptables log via %iptables% parser added + (currently experimental pending practical verification) +- normalizer tool on its way to a full-blow stand-alone tool +- support for annotations added, for the time being see + http://blog.gerhards.net/2011/11/log-annotation-with-liblognorm.html +---------------------------------------------------------------------- +Version 0.3.1 (rgerhards), 2011-04-18 +- added -t option to normalizer so that only messages with a + specified tag will be output +- bugfix: abort if a tag was assigned to a message without any + fields parsed out (uncommon scenario) +- bugfix: mem leak on parse tree destruct -- associated tags were + not deleted +- bugfix: potential abort in normalizer due to misadressing in debug + message generation +---------------------------------------------------------------------- +Version 0.3.0 (rgerhards), 2011-04-06 +- support for message classification via tags added +- bugfix: partial messages were invalidly matched + closes: http://bugzilla.adiscon.com/show_bug.cgi?id=247 +---------------------------------------------------------------------- +Version 0.2.0 (rgerhards), 2011-04-01 +- added -E option to normalizer tool, permits to specify data for + encoders +- support for new libee parsers: + * Time12hr + * Time24hr + * ISODate + * QuotedString +- support for csv encoding added +- added -p option to normalizer tool (output only correctly parsed + entries) +- bugfix: segfault if a parse tree prefix had exactly buffer size, + in which case it was invalidly assumed that an external buffer had + been allocated +---------------------------------------------------------------------- +Version 0.1.0 (rgerhards), 2010-12-09 +Initial public release.
