Log message:
PKGREVISION bump for anything using python without a PYPKGPREFIX.

This is a semi-manual PKGREVISION bump.

Log message:
revbump for boost 1.69.0

Log message:
sysutils/rsyslog*: Update to 8.38.0.

Version 8.38.0 [v8-stable] 2018-09-18
- AIX: make basic modules work again
- make rsyslog build on AIX again
- imfile: support for endmsg.regex
- imkafka: add parameter "parseHostName"
- im[p]tcp: improve error message on connect failure
- imkafka: implement multithreading support for kafka consumers.
- omelasticsearch: write all header metadata to $.omes for retries
- core: improve error message on module load fail
- core/queue: add error message if queue file cannot be accessed
- imtcp/imudp: new option preservecase for managing the case of
  FROMHOST value
- omprog: add feedback timeout and keep-alive feature
- omprog: fix forceSingleInstance configuration option
- imfile: implement file-id, used in state file
- imfile: experimental input throtteling feature
- core: emit TZ warning on startup not on Linux non-container
- omkafka:
  - better debug information
  - Fixed minor issue in omkafka producing wrong kafka timestamps when
    msgTimestamp was NULL.
  - Setting RD_KAFKA_V_KEY(NULL, 0) in rd_kafka_producev now when KEY
    is not configured.
  - Fixed minor issue when rsyslog is compiled with --enable-debug and
    librdkafka is too old.
- omfile bugfix: errant error message when dynafile param needed
- omhttp: new contribued module
- mmkubertnetes: action fails preparation cycle if kubernetes API
  destroys resource during bootup sequence
- bugfix pmnormalize/core: several memory leaks, invld property
  handling
- bugfix imptcp: fixed pointers for session counting
- bugfix omprog: invalid memory access on partial writes to pipe
- bugfix omprog: rsyslog's environment was not passed to script
- bugfix omprog: severity of some log messages in waitForChild
  corrected
- bugfix imfile: files which were loaded via symlink were not always
  followed
- bugfix imfile: potential misadressing when processing symlinks
- bugfix ommongodb: build issue if mongo-c-driver is not compiled with
  TLS

Log message:
revbump after boost-libs update

Log message:
sysutils/rsyslog*: Update to 8.35.0.

- imptcp: add ability to configure socket backlog
- omfile: do not permit filename that only consists of whitespace
- fmhash: new hash function module
- some better error messages
- imklog: add ratelimiting capability
- omkafka: added impstats counters for librdkafka returned statistics
- imudp
  * use rsyslog message rate-limiter instead of home-grown one
  * add stats counter "disallowed"
- imrelp: add parameter "oversizeMode"
- core: consistent handling of oversize input messages
- omfwd: add support for bind-to-address for UDP
- template systemd service file proposes higher permitted file handle
  limit
- imuxsock: replace select() call by poll()
- nsdsel_ptcp: replace select() by poll()
- omprog: refactor tests, fix child closing issues
- core: config optimizer did not handle call_indirect
- debug support: add capability to print testbench-specific timeout
  reports
- mmgrok: fix potential segfault
- imrelp bugfix: maxDataSize could be set lower than maxMessageSize
- build system bugfix: build broken if liblogging-stdlog installed in
  custom path
- core bugfix: segfault on queue shutdown
- imfile bugfix: statefiles contain invalid JSON
- omfile bugfix: segfault if empty filename was given
- fix build issues when atomic operations are not present
- lmsig_ksils12 bugfix: build and static analyzer issues
- impstats bugfix: segfault if bound to non-existing ruleset
- mmjsonparse bugfix: invalid container name was not detected
- mmkubernetes bugfixes: fix lnrules, add defaults, add test
- build system bugfix: --enable-atomic-operations did not work
- bugfix: rsyslog aborts on startup when specific config errors are
  made
- build system: remove no longer needed --enable-libcurl configure

Log message:
revbump for boost-libs update

Log message:
rsyslog-omprog: Import version 8.31.0 into pkgsrc.

This module permits to integrate arbitrary external programs into
rsyslog's logging.  It is similar to the "execute program (^)" action,
but offers better security and much higher performance. While "execute
program (^)" can be a useful tool for executing programs if rare events
occur, omprog can be used to provide massive amounts of log data to a
program.