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

Log message:
Add option for rabbitmq support. Build jsonparse unconditionally (we're
depending on json-c anyway. Bump PKGREVISION.

Log message:
Fix BUILDLINK_ABI_DEPENDS

Log message:
Fix undefined symbol reference in imuxsock on SunOS. Add SMF manifest.
Bump PKGREVISION.

Log message:
Version 7.6.3 [v7.6-stable] 2014-03-27
- add capability to override GnuTLS path in build process
  Thanks to Clayton Shotwell for the patch
- support for librelp 1.2.5
  Support new return states of librelp 1.2.5 to emit better error messages
  For obvious reasons, librelp 1.2.5 is now required.
- bugfix: ompipe used invalid default template
  This is a regression from an old change (didn't track it down precisely,
  but over a year ago). It used the Forwarding template instead of
  the file template (so we have a full syslog header). This fix corrects
  it back to previous behaviour, but new scripts that used the wrong
  format may now need to have the RSYSLOG_ForwardingFormat template
  explicitely be applied.
  closes: https://github.com/rsyslog/rsyslog/issues/50
- bugfix: ompipe did emit many suspension messages for /dev/xconsole
  (hopefully now) closes: https://github.com/rsyslog/rsyslog/issues/35
  When it was present, but nobody reading from it. The problem
  is the way the rsyslog v7 engine tries to resolve failures in outputs.
  It does some retries, and along those lines some state information gets
  lost and it is close to impossible to retain it. However, the actual
  root problem is that ompipe does not reliably detect if it is able to
  recover. The problem here is that it actually does not know this
  before it does an actual write. These two things together mess up the
  logic that suppresses invalid resumption/suspension messages
  (actually, the plugin switches state really that often).
  Nevertheless, the prime problem with /dev/xconsole (and probably
  most other pipes as well) is that it gets full. So I have now added
  code that checks, during resume processing, if the pipe is writable.
  If it is not, resume is deferred. That should address the case.

Version 7.6.2 [v7.6-stable] 2014-03-17
- support for librelp 1.2.4
  This was necessary due to the problems with librelp 1.2.3 API stability.
  We now use the new native 1.2.4 APIs to learn about the state of
  librelp's TLS support.
  For obvious reasons, librelp 1.2.4 is now required.

Version 7.6.1 [v7.6-stable] 2014-03-13
- added "action.reportSuspension" action parameter
  This now permits to control handling on a per-action basis rather to
  the previous "global setting only".
- "action resumed" message now also specifies module type
  which makes troubleshooting a bit easier. Note that we cannot output all
  the config details (like destination etc) as this would require much more
  elaborate code changes, which we at least do not like to do in the
  stable version.
- better and more consistent action naming, action queues now always
  contain the word "queue" after the action name
- add support for "tls-less" librelp
  we now require librelp 1.2.3, as we need the new error code definition
  See also: https://github.com/rsyslog/librelp/issues/1
- build system improvements
  * autoconf subdir option
  * support for newer json-c packages
  Thanks to Michael Biebl for the patches.
- imjournal enhancements:
  * log entries with empty message field are no longer ignored
  * invalid facility and severity values are replaced by defaults
  * new config parameters to set default facility and severity
  Thanks to Tomas Heinrich for implementing this
- bugfix: ompipe did resume itself even when it was still in error
  See: https://github.com/rsyslog/rsyslog/issues/35
  Thanks to github user schplat for reporting
- bugfix: "action xxx suspended" did report incorrect error code
- bugfix: ommongodb's template parameter was mandatory but should have
  been optional
  Thanks to Alain for the analysis and the patch.
- bugfix: only partial doc was put into distribution tarball
  Thanks to Michael Biebl for alerting us.
  see also: https://github.com/rsyslog/rsyslog/issues/31
- bugfix: async ruleset did process already-deleted messages
  Thanks to John Novotny for the patch.

Version 7.6.0 [v7.6-stable] 2014-02-12
This starts a new stable branch based on 7.5.8 plus the following changes:
- bugfix: imuxsock input parameters were not accepted
  due to copy&paste error. Thanks to Andy Goldstein for the fix.
- added ProcessInternalMessages global system parameter
  This permits to inject rsyslog status messages into *another* main
  syslogd or the journal.
- new dependency: liblogging-stdlog (for submitting to external logger)
- bugfix: json templates are improperly created
  Strings miss the terminating NUL character, which obviously can lead
  to all sorts of problems.
  See also: https://github.com/rsyslog/rsyslog/issues/27
  Thanks to Alain for the analysis and the patch.
- ompgsql bugfix: improper handling of auto-backgrounding mode
  If rsyslog was set to auto-background itself (default code behaviour, but
  many distros now turn it off for good reason), ompgsql could not
  properly connect. This could even lead to a segfault. The core reason
  was that a PG session handle was kept open over a fork, something that
  is explicitely forbidden in the PG API.
  Thanks to Alain for the analysis and the patch.

Version 7.4.11  [v7.4-stable] *never released*
- imjournal enhancements:
  * log entries with empty message field are no longer ignored
  * invalid facility and severity values are replaced by defaults
  * new config parameters to set default facility and severity
  Thanks to Tomas Heinrich for implementing this

Version 7.4.10  [v7.4-stable] 2014-02-12
- bugfix: json templates are improperly created
  Strings miss the terminating NUL character, which obviously can lead
  to all sorts of problems.
  See also: https://github.com/rsyslog/rsyslog/issues/27
  Thanks to Alain for the analysis and the patch.
- ompgsql bugfix: improper handling of auto-backgrounding mode
  If rsyslog was set to auto-background itself (default code behaviour, but
  many distros now turn it off for good reason), ompgsql could not
  properly connect. This could even lead to a segfault. The core reason
  was that a PG session handle was kept open over a fork, something that
  is explicitely forbidden in the PG API.
  Thanks to Alain for the analysis and the patch.

Version 7.4.9  [v7.4-stable] 2014-01-22
- added ProcessInternalMessages global system parameter
  This permits to inject rsyslog status messages into *another* main
  syslogd or the journal.
- new dependency: liblogging-stdlog (for submitting to external logger)
- bugfix: imuxsock input parameters were not accepted
  due to copy&paste error. Thanks to Andy Goldstein for the fix.
- bugfix: potential double-free in RainerScript equal comparison
  happens if the left-hand operand is JSON object and the right-hand
  operand is a non-string that does not convert to a number (for
  example, it can be another JSON object, probably the only case that
  could happen in practice). This is very unlikely to be triggered.
- bugfix: some RainerScript Json(Variable)/string comparisons were wrong

Version 7.4.8  [v7.4-stable] 2014-01-08
- rsgtutil provides better error messages on unfinished signature blocks
- bugfix: guard against control characters in internal (error) messages
  Thanks to Ahto Truu for alerting us.
- bugfix: immark did emit messages under kern.=info instead of syslog.=info
  Note that his can potentially break exisiting configurations that
  rely on immark sending as kern.=info. Unfortunately, we cannot leave
  this unfixed as we never should emit messages under the kern facility.

Log message:
Update rsyslog7 to 7.4.7.

Many bugfixes since 7.4.4, see release notes:

http://www.rsyslog.com/changelog-for-7-4-7-v7-stable/
http://www.rsyslog.com/changelog-for-7-4-6-v7-stable/
http://www.rsyslog.com/changelog-for-7-4-5-v7-stable/

Log message:
Remove entirely redundant and annoying CONFLICTS

Log message:
Enable diag and user tools by default. Bump PKGREVISION.

Log message:
flex is needed of course

Log message:
Fix build on *BSD. Fix PLIST issue by always building in imdiag.