Suppress experimental warning for my $_ in Devel::PPPort's tests.

This warning was missed by commit dcd695b6ec3bf411. The patch is effectively
an update of commit 0d7b125b0c3d6ada. It requires hoop jumping with if,
because the "experimental::lexical_topic" warnings category is unrecognised
and hence a fatal error on earlier perls.
Update podlators to CPAN version 2.5.1

  [DELTA]

  2013-02-27  Russ Allbery  <rra@stanford.edu>

    * VERSION: podlators 2.5.1 released.

    * t/color.t: Add Z<> to tag width test to avoid triggering the new
    Pod::Parser warning about numeric items in description lists.
    * t/overstrike.t: Likewise.
    * t/termcap.t: Likewise.
    * t/man.t: Remove the test for proper handling of lists that start
    with a non-bullet and then have an item that looks like a bullet.
    This now triggers a warning in Pod::Simple.  Move it to...
    * t/man-options.t: ...here, where we can configure the parser to
    ignore errors and test that the output is correct.
Forgot to update Maintainers.pl for podlators update
Update Text-ParseWords to CPAN version 3.28

  [DELTA]

  3.28
  Better diag information in pod.t
  More metadata in META.yml
correct Pod-Html tests for new Pod-Simple output

Okay, look, I know we should really fix the tests to be more
generic, but that's just not going to happen right now.  Hopefully,
we can ditch Pod-Html before this comes up again.  Maintaining it
as is is sort of a drag.
Bump Pod::Html to 1.19
Update Pod-Simple to CPAN version 3.26

  [DELTA]

  2013-02-27   David E. Wheeler <david@justatheory.org>
    * Release 3.26

    Fixed another test script to skip all tests when Encode is not
    installed.

    Added 'encoding()' and 'detected_encoding()' to return the current
    encoding and the encoding actually to decode the input file. The
    value from "=encoding" is also now kept in the output tree. Patch
    from Patrice Dumas (RT #74390).

  2013-02-16   David E. Wheeler <david@justatheory.org>
    * Release 3.25

    Improved the warning when "=item" types mismatch within one
    "=over"/"=back" block.

  2013-02-14   David E. Wheeler <david@justatheory.org>
    * Release 3.24

    Fixed corner case bug for unlikely scenario in which non-UTF-8
    text could be parsed as UTF-8. Grant McLean.

    XHTML IDs can no longer end with punctuation. Thanks to Smylers
    for the patch.

    Fixed test failure on Perl 5.6.2.

    Changed the default installation location from "perl" to "site" on
    5.12 and higher, since as of that version of Perl, dual-life
    modules no longer need to be installed in "perl" to replace
    in-core versions. Patch from tzccinct.

    Fixed hash order dependency test failures on Perl 5.17. Thanks to
    Yves Orton for the patch.

    Inlined the code that tries to guess a Pod file's encoding. This
    reduces the time Pod::Simple takes to build the core Perl
    documentation by 15-20%. Thanks to Dagfinn Ilmari Mannsåker for
    the patch!

    Added a warning when "=item" types mismatch within one
    "=over"/"=back" block. Marc Green/Google Summer of Code, with
    assist from RJBS.

    Fixed regression introduced in 3.22 in which "C< >" tags were
    incorrectly treated as verbatim text in table of contents items
    emitted by Pod::Simple::XHTML. Thanks to Randy Stauner for the
    report and to Thomas Sibley for the fix!

    Loosened up the matching of "L< >" tags for man pages so that they
    allow names with dots, underscores, and any other chararacters
    other than "/", just so long as they end in '[(][-a-zA-Z0-9]+[)]'.
    Thanks to Dave Rolsky and Kevin Ryde for the reports (RT #82975 &
    RT #82972).

    Fixed inverted mapping of "keyboard" to "kbd" in
    Pod::Simple::HTML. Thanks to Robert Boisvert for the bug report
    (RT #79201).

    Added two new Tagmap entries to Pod::Simple::HTML: "preformat"
    maps to "pre", and "teletype" maps to "tt". Suggested by Robert
    Boisvert (RT #79201).

    "X< >" tags are now ignored by the pull parser when it searches
    for titles, as is any trailing whitespace. Thanks to Patrice Dumas
    for the report (RT #74389).
Revert "Bump Pod::Html to 1.19"

This reverts commit 46b428ce5128df764ce460c744a3c4f0f9727b5b.
[PATCH] Bump Locale-Codes from 3.24 to 3.25

Signed-off-by: Chris 'BinGOs' Williams <chris@bingosnet.co.uk>
perldtrace.pod: fix example code
Add Anton Nikishaev to AUTHORS: RT #116959.
Skip tests in File::Copy tests on DragonflyBSD too

Setting 0100, 0300 and 0500 on files is totally non-reversable
Skip chflags tests in filetests.t on dragonflybsd

DragonflyBSD's file tests don't seem to be chflags-aware:

  $ touch foo
  $ if [ -w foo ]; then echo "Yes"; fi
  Yes
  $ chflags uchg foo
  $ if [ -w foo ]; then echo "Yes"; fi
  Yes

versus FreeBSD:

  $ touch foo
  $ if [ -w foo ]; then echo "Yes"; fi
  Yes
  $ chflags uchg foo
  $ if [ -w foo ]; then echo "Yes"; fi
  $
revert: Benchmark iteration warnings should warn

This commit reverts:

    commit a820780c62918236069b3b55502640c99a9e812a
    Author:     David Golden <dagolden@cpan.org>
    AuthorDate: Tue Feb 5 22:23:37 2013 -0500
    Commit:     David Golden <dagolden@cpan.org>
    CommitDate: Tue Feb 5 22:49:36 2013 -0500

        Benchmark iteration warnings should warn, not print

because the warnings appearing on STDERR weren't being trapped by
Benchmark.t (see [perl #116831]). Revert for now, and re-address after
5.18.
Add void casts to VMS-specific bail-out macro.

The macro used in vms/vms.c for errors from native calls deemed
too severe to handle was calling fprintf without checking return
values, which caused a huge pile of warnings when compiling with
/WARN=ENABLE=LEVEL5. So suppress those warnings with a void cast.
Fix signed/unsigned mismatch in vms/vms.c.
Synchronise VERSIONs of all bignum modules
Synchronise bignum with CPAN
Synchronise Env with CPAN
Disable by default the new Copy-on-Write for 5.18

It was felt that the new COW feature wasn't ready to be enabled be default
in 5.18: principally because too much XS code will assume it can just
manipulate the PVX buffer of an SVf_POK SV.

See RT #116569 for the discussion.