Log message:
Remove obsolete packages.

Log message:
Fix the upper version limit for liblognorm<1.

Log message:
Update liblognorm to 0.3.7.

Version 0.3.7, 2013-07-17
* added support to load single samples

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

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
Mark packages that don't or might probably not have staged installation.

Log message:
Update to 0.3.4.

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

Log message:
MAKE_JOBS_SAFE=no

Log message:
Update to 0.3.3.

Changes since 0.3.1:
 * required header file was not installed, resulting in compile error
   closes: http://bugzilla.adiscon.com/show_bug.cgi?id=307

 * 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

Log message:
Update to version 0.3.1.

Changes:
 * 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

Log message:
Import liblognorm-0.3.0 as wip/liblognorm.

Briefly described, liblognorm is a tool to normalize log data.

People who need to take a look at logs often have a common problem.
Logs from different machines (from different vendors) usually have
different formats for their logs. Even if it is the same type of log
(e.g. from firewalls), the log entries are so different, that it is
pretty hard to read these. This is where liblognorm comes into the game.
With this tool you can normalize all your logs. All you need is liblognorm
and its dependencies and a sample database that fits the logs you want
to normalize.