Tarsnap 1.0.38 is now available. This version brings several new features
compared to tarsnap 1.0.37:
* Tarsnap now supports OpenSSL 1.1.
* tarsnap accepts an --iso-dates option, which causes times to be printed in
YYYY-MM-DD HH:MM:SS format rather than the traditional unix "ls -l" style.
* tarsnap accepts a --force-resources option to proceed with decryption of a
passphrase-encrypted key file even if it is anticipated to use an excessive
amount of memory or CPU time. (This may be useful if tarsnap inaccurately
estimates the amount of memory your system has available.)
* tarsnap accepts an --archive-names <file> option, which reads a list of
archive names to operate on when operating in -d and --print-stats modes.
(This should make some scripts simpler; no more need to construct a command
line which has '-f' inserted before each archive name.)
Potentially (but unlikely) breaking changes in this code compared to tarsnap
1.0.37:
* tarsnap now applies the --humanize-numbers option to the "progress" output
printed by SIGINFO / SIGUSR1. If you have scripts which send signals to
tarsnap and parse its output, they may need to be updated.
* tarsnap -v now prints 'Deleting archive "foo"' even if only one archive is
being deleted. If you have scripts which parse the output of tarsnap -v,
they may need to be updated.
* tarsnap now prints a warning if you pass '--configfile /nosuchfile'. If you
have scripts which rely on being able to specify nonexistent configuration
files and not get any warnings from tarsnap, they may need to be updated.
(Also, if you were doing that, I *really* want to know why.)
There are also two changes which most users should not encounter:
* tarsnap now has an --initialize-cachedir mode; this is intended for use by
the GUI. (The cache directory will be initialized automatically in normal
usage of the tarsnap command-line utility.)
* tarsnap's configure script takes a --with-conf-no-sample option which
results in the sample tarsnap configuration file being installed as
"tarsnap.conf" rather than "tarsnap.conf.sample". This is intended for use in
some packaging systems which have mechanisms for managing configuration files,
and should probably not be used by hand (since it will overwrite your existing
tarsnap.conf).
3.5.1 - 15 June 2017
- Doc fix: Missed a curly brace in an example. (#412)
- Feature: Dynamic metadata functions (#392) - It is now possible to
dynamically add metadata to lager messages. See the "dynamic
metadata" section above for more information.
- Doc fix: Add information about the "application" placeholder. (#414)
3.5.0 - 28 May 2017
- Bugfix: Support OTP 20 gen_event messages (#410)
- Feature: Enable console output to standard_error.
Convert to proplist configuration style (like file handler)
Deprecate previous configuration directives (#409)
- Bugfix: Enable the event shaper to filter messages before they're
counted; do not count application/supervisor start/stops
toward high water mark. (#411)
- Docs: Add PR guidelines; add info about the #lager chat room on freenode.
3.4.2 - 26 April 2017
- Docs: Document how to make lager use UTC timestamps (#405)
- Docs: Add a note about our triage cadence.
- Docs: Update lager_syslog URL
- Docs: Document placeholders for error_logger integration (#404)
- Feature: Add hex.pm metadata and full rebar3 support.
3.4.1 - 28 March 2017
- Docs: Added documentation around using lager in the context of elixir applications (#398)
- Bugfix: Properly expand paths when log_root is set. (#386)
- Policy: Removed R15 from Travis configuration
3.4.0 - 16 March 2017
- Policy: Adopt official OTP support policy. (This is the **last** lager 3.x release
that will support R15.)
- Test: Fix timeouts, R15 missing functions on possibly long-running tests in Travis. (#394, #395)
- Feature: capture and log metadata from error_logger messages (#397)
- Feature: Expose new trace filters and enable filter composition (#389)
- Feature: Log crashes from gen_fsm and gen_statem correctly (#391)
- Docs: Typo in badge URL (#390)
3.3.0 - 16 February 2017
- Docs: Fix documentation to make 'it' unambiguous when discussing asychronous
operation. (#387)
- Test: Fix test flappiness due to insufficient sanitation between test runs (#384, #385)
- Feature: Allow metadata only logging. (#380)
- Feature: Add an upper case severity formatter (#372)
- Feature: Add support for suppressing start/stop messages from supervisors (#368)
- Bugfix: Fix ranch crash messages (#366)
- Test: Update Travis config for 18.3 and 19.0 (#365)
3.2.4 - 11 October 2016
- Test: Fix dialyzer warnings.
3.2.3 - 29 September 2016
- Dependency: Update to goldrush 0.19
3.2.2 - 22 September 2016
- Bugfix: Backwards-compatibility fix for `{crash_log, undefined}` (#371)
- Fix documentation/README to reflect the preference for using `false`
as the `crash_log` setting value rather than `undefined` to indicate
that the crash log should not be written (#364)
- Bugfix: Backwards-compatibility fix for `lager_file_backend` "legacy"
configuration format (#374)
2017-07-05 Martin Mares <mj@ucw.cz>
* Released as 3.5.5.
* Better decoding of AER capability.
* "Slot Implemented" flag is decoded for PCI/PCI-X to PCIe bridges.
* Minor fixes of decoding other capabilities.
* As usually, updated pci.ids to the current snapshot of the database.
- omfwd: add parameter "tcp_frameDelimiter"
- omkafka: large refactor of kafka subsystem
- imfile: improved handling of atomically renamed file (w/ wildcards)
- imfile: add capability to truncate oversize messages or split into
multiple
- mmdblookup
* upgraded from "contrib" to "fully supported" state
* refactored and simplified code
* added ability to specify custom names for extracted fields
* bugfix: fixed multiple memory leaks
- imptcp: add new parameter "flowControl"
- imrelp: add "maxDataSize" config parameter
- multiple modules: gtls: improve error if certificate file can't be
opened
- omsnare: allow different tab escapes
- omelasticsearch: converted to use libfastjson instead of json-c
- imjournal: _PID fallback
- multiple modules: add better error messages when regcomp is failing
- omhiredis: fix build warnings
- imfile bugfix: files mv-ed in into directory were not handled
- omprog bugfix: execve() incorrectly called
- imfile bugfix: multiline timeout did not work if state file exists
- lmsig_ksi-ls12 bugfix: build problems on some platforms
- core bugfix: invalid object type assertion
- regression fix: local hostname was not always detected properly on
early start (w/o network).
- bugfix: format security issues in zmq3 modules
- bugfix build system: add libksi only to those binaries that need it
- bugfix KSI ls12 components: invalid tree height calculation
- testbench/CI enhancements
D-Bus 1.10.20 (2017-06-29)
==
The “suggesting a delivery gone horribly wrong” release.
Fixes:
• Fix a reference leak when blocking on a pending call on a connection
that has been disconnected (fd.o #101481, Shin-ichi MORITA)
• Don't put timestamps in the Doxygen-generated documentation, for
closer-to-reproducible builds (fd.o #100692, Simon McVittie)
• Avoid an assertion failure when connecting to a semicolon-separated
series of addresses, one of which fails (fd.o #101257, Simon McVittie)
Documentation:
• Update git URIs in HACKING document to sync up with cgit.freedesktop.org
(fd.o #100715, Simon McVittie)
BREAKING CHANGES:
- agent: Parse values given to `?passing` for health endpoints.
- agent: The default value of `-disable-host-node-id` has been changed
from false to true.
IMPROVEMENTS:
- agent: Added a `-disable-keyring-file` option to prevent writing
keyring data to disk.
- agent: Added automatic notify to systemd on Linux after LAN join is
complete, which makes it easier to order services that depend on
Consul being available.
- agent: The `http_api_response_headers` config has been moved into a
new `http_config` struct, so the old form is still supported but is
deprecated.
- dns: Added support for EDNS(0) size adjustments if set in the
request frame.
- server: Added a startup warning for servers when expecting to
bootstrap with an even number of nodes.
- agent: (Consul Enterprise) Added support for non rotating,
statically named snapshots for S3 snapshots using the snapshot
agent.
BUG FIXES:
- agent: Fixed a regression where configuring -1 for the port was no
longer disabling the DNS server.
- agent: Fix `consul leave` shutdown race.
- agent: Show a better error message than 'EOF' when attempting to
join with the wrong gossip key.
- agent: Fixed an issue where the `Method` and `Header` features of
HTTP health checks were not being applied.
- agent: Fixed an issue where internally-configured watches were not
working because of an incorrect protocol error, and unified internal
watch handling during reloads of the Consul agent.
- server: Fixed an issue where the leader could return stale data
duing queries as it is starting up.
From DESCR:
Monitoring::Plugin and its associated Monitoring::Plugin::* modules are
a family of perl modules to streamline writing Monitoring plugins. The
main end user modules are Monitoring::Plugin, providing an
object-oriented interface to the entire Monitoring::Plugin::*
collection, and Monitoring::Plugin::Functions, providing a simpler
functional interface to a useful subset of the available functionality.
recommends using `etckeeper unclean` to determine if there are any
changes in need of committing, which works with every VCS that
etckeeper supports. Bump PKGREVISION.
