Update autodie to CPAN version 2.19

  [DELTA]

2.19      2013-05-13 10:02:15 Australia/Melbourne

        * BUGFIX: Loading a file that does not change packages while
          autodie in effect no longer causes weird behaviour when
          slurpy built-ins (like open() and unlink()) are called. GH #22
          Thanks to Niels Thykier.

        * TEST: Tests for leak guard failures for slurpy core functions.

2.18      2013-05-12 18:12:14 Australia/Melbourne

        * TEST: More testing in scope_leak.t.

        * TEST: More testing around packages in truncate.t.

        * SPEED / INTERNAL: Significant improvements in load time,
          especially when autodie is used across multiple files,
          by caching reuseable subroutines and reducing calls to eval "".
          Huge thanks to Niels Thykier, who is a hero of the
          free people, and completely and utterly awesome.
          (RT #46984)

        * DOCUMENTATION: Spelling and correction fixes,
          courtesy David Steinbrunner.

        * DEVEL: Faster and more robust testing with travis-ci.

        * DEVEL: Some simple benchmarks bundled in the benchmarks/ directory.

2.17      2013-04-29 01:03:50 Australia/Melbourne

        * DOCS: Spelling fixes thanks to dsteinbrunner! (RT #84897)

        * DOCS: Fixed github links to point to 'pjf' rather than
          'pfenwick' (GH #18, thanks to Lx!)

        * INTERNAL: Silence warnings about experimental smart-match on
          5.17.11+ (via Brian Fraser and p5p)

        * TEST / BUILD: Generate .travis.yml files for CI testing via
          dzil.

2.16      2013-02-23 01:49:16 Australia/Melbourne

        * BUGFIX: Fix breakages under 5.8.x related to the new
          autodie::skip feature.

        * BUILD / BUGFIX: Remove dependency on parent.pm.

2.15      2013-02-22 23:55:22 Australia/Melbourne

        * BUILD / BUGFIX: Correct meta-info that wanted at least Perl
          v5.8.40, rather than v5.8.4.  Giant thanks to Paul Howarth
          for spotting this!

2.14      2013-02-22 15:43:33 Australia/Melbourne

        * FEATURE: Classes which claim they ->DOES('autodie::skip') are now
          skipped when generating exceptions.  This is mainly of use to
          utility classes. See `perldoc autodie::skip` for more details.
          (GH Issue #15)

        * FEATURE / BUGFIX / INCOMPAT: 'chmod' is now in the ':filesys'
          category (was in ':file').

        * BUGFIX: Added support for 'chown' and 'utime', that was
          previously overlooked. Mad props to RsrchBoy for spotting this.
          These are all in the ':filesys' category.
          (GH Pull #13)

        * BUGFIX: Added support for 'kill'. This is part of the
          ':ipc' category.

        * BUGFIX: Fixed bug whereby chmod, chown, kill, unlink and
          utime would not throw an exception when they didn't
          change all their files or signal all their processes.

        * TEST: truncate.t is now skipped on systems that don't have a
          working File::Temp.

        * TEST: open.t has a few more tests for exotic modes.

        * TEST: chown() tests are skipped on Win32, as chown on Windows
          is a no-op. (Thanks to Mithaldu for spotting this!)

        * TEST: Author tests now look for the AUTHOR_TESTING env
          variable (for dzil compliance).

        * TEST: Better testing for chown, chmod, and unlink.

        * TEST: Better testing for utime.

        * TEST: kwalitee.t is now only run when $ENV{RELEASE_TESTING} is set.

        * BUGFIX: Removed executable bits from some bundled text files.

        * BUILD: We now use dzil to manage autodie.

        * BUILD: Only Perl 5.8.4 and above is supported by autodie.
          Please upgrade your Perl distro if you're using 5.8.3 or
          below.
Update DB_File to CPAN version 1.828

  [DELTA]

  1.828 7 May 2013

   * Minor change to build with Berkeley DB 6.x
Update Sys-Syslog to CPAN version 0.33

  [DELTA]

  0.33 -- 2013.05.24 -- Sebastien Aperghis-Tramoni (SAPER)
        [BUGFIX] CPAN-RT#82531: Invalid usage of POSIX::_exit (Alexander Berger).
        [OPTIM] No longer inherit from Exporter.
        [OPTIM] Load Fcntl only when necessary.
        [DOC] Add links to other logging modules.
        [DOC] CPAN-RT#80398: Typo spotted by alfirth@gmail.com
        [DOC] Typo spotted by David Steinbrunner.
        [TEST] CPAN-RT#79683: Added delays in t/facilities-routing.t
typo fixes for Unicode UCD
re-enable Copy-on-Write by default.

COW was first introduced (and enabled by default) in 5.17.7.
It was disabled by default in 5.17.10, because it was though to have too
many rough edges for the 5.18.0 release.

By re-enabling it now, early in the 5.19.x release cycle, hopefully it
will be ready for production use by 5.20.

This commit mainly reverts 9f351b45f4 and e1fd41328c (with modifications),
then updates perldelta.
perl -V displayed PERL_NEW_COPY_ON_WRITE twice

I didn't realise that the perl -V list of defines is now split between
perl.h and perl.c and so added it to one (thinking it was missing) when it
was already in the other).
Net::Ping: wrap long pod lines
POSIX.pod: wrap/shorten long lines
regen pod issues
Increase $Net::Ping::VERSION to 2.42
perldiag: miscellaneous clean-up

•‘Corrupted regexp opcode’ is a ‘can’t happen’ error, so it belongs
  in the P category.
• Two spaces after dots for consistency
• Rewrap for slightly better splain output
• The description usually begins on the same line as the category, so
  do so consistently
• Reorder alphabetically
• Missing category
• Single, not double, backslash
• Squash two adjacent (due to reordering) entries with identical
  descriptions
• ‘given’ does not depend on lexical $_ any more
• Remove duplicate entries (and placate diag.t with diag_listed_as)
do not wrap long non-verbatim lines in perldiag.pod

This is an unfortunate situation.  diagnostics.pm gets its
explanation of an error or warning from perldiag.pod and (basically)
strips out Pod formatting sequences.  That means that if a line is
long because of a Pod sequence, it may be the "right" length for an
80 column terminal with the Pod stripped, even though the source
document will be "too long."  There isn't much of a presentation
layer here, because diagnostics.pm will not attempt to reflow text.

Adding such a layer may be better later, and the benefit to this
reversion is low, but the benefit of the commit itself was also low.
(In fact, this change may have had no value: the long lines about
which our Pod checker complains are in verbatim paragraphs, and this
line is not a verbatim paragraph.)

This regression was reported by Father Chrysostomos:

After 1dcc3c19f1c0:

  $ ./perl -Ilib -Mdiagnostics -e 'warn "Lexing code attempted to stuff non-Latin-1 character into Latin-1 input"'
  Lexing code attempted to stuff non-Latin-1 character into Latin-1 input at -e
    line 1 (#1)
      (F) An extension is attempting to insert text into the current parse (using
      lex_stuff_pvn or similar), but tried to insert a
      character that couldn't be part of the current input.  This is an inherent
      pitfall of the stuffing mechanism, and one of the reasons to avoid it.  Where
      it is necessary to stuff, stuffing only plain ASCII is recommended.

Note the awkward line break.

This commit reverts a change made in 1dcc3c19f1c0.
perldiag: more alphabetisation
[perl #64126] ./Configure -de -Dusevendorprefix didn't default
perldiag: wrap an entry for better splain output
perldiag: mark two deprecated entries with D
Make ‘Escape literal pattern white space’ a default warning

All deprecated warnings are supposed to be default warnings.
Turn \N{  } deprecation warnings on by default

All deprecation warnings are supposed to be on by default, but
these two were not.
Make \N{  } deprecation warnings fatalizable

What drew my attention to this was the missing category in
perldiag.pod.  I tried adding it, but diag.t complained that it should
be absent.

It thinks it should be absent, because Perl_warn (when used correctly)
does not put the warning in any category, and does not allow it to be
suppressed except via $SIG{__WARN__}.

Use of if(ckWARN) followed by Perl_warn is not correct.  ckWARN checks
to see whether the category is enabled, and then Perl_warn warns with-
out reference to the category at all, so whether it is fatal cannot
be looked up.

The result is that these warnings do not die under ‘use warnings
FATAL => 'deprecated'’.
perldiag: reflow another entry for nice splain output