Log message:
Recursive revbump from lang/perl5 5.26.0

Log message:
Updated security/p5-pcsc to 1.4.14
----------------------------------
2015-11-19  author  <author@debian>
        * README: Release 1.4.14

        * PCSC.xs: Update copyright date

        * PCSC.xs: _StringifyError(): cast Error in a (DWORD)

        On Mac OS X El Capitan (at least) the value is extended to 64 bits and
        is then wrong.

        We get 0xFFFFFFFF80100068 instead of 0x80100068 and all the error codes
        are all converted to the default error: "Unknown (reader specific \ 
?) error..."

Log message:
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.

Log message:
Bump PKGREVISION for perl-5.24.

Log message:
Add SHA512 digests for distfiles for security category

Problems found locating distfiles:
	Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz
	Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz
	Package libidea: missing distfile libidea-0.8.2b.tar.gz
	Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2
	Package uvscan: missing distfile vlp4510e.tar.Z

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

Log message:
Make PKGNAME match directory name.

Log message:
Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.

Log message:
Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.

Log message:
1.4.13 - 1 April 2013, Ludovic ROUSSEAU
    - Fix a warning with Perl 5.16

Log message:
Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.