pod2man from perl 5.18 now exits with a non-zero exit code rather than
putting errors in the manpage (see [1]). Unfortunately. src/Makefile.am
assumes the latter behaviour, and masks non-zero exit codes:

.pod.1:
    pod2man --release=$(VERSION) --center=$(PACKAGE) $< \
        >.pod2man.tmp.$$$$ 2>/dev/null && mv -f .pod2man.tmp.$$$$ $@ || true
    @if grep '\<POD ERRORS\>' $@ >/dev/null 2>&1; \
    then \
        echo "$@ has some POD errors!"; false; \
    fi

Thie manifests in the current package as an odd missing manpage
(collectdctl.1) which doesn't get detected until the install phase of
the package build. Separate bug about that particular case to follow.

Patches along the attached lines should stop these errors from being
ignored, but they also reveal at least one more POD errors to be fixed
For this reason, I'm not tagging this but with 'patch' at the moment.
The patches are against 5.2.1-1 from experimental, as I assume that's
what you are considering your development head at the moment.

Note that I haven't verified the correctness of dh_autoreconf, nor
investigated whether there are any particular reasons to ignore the
exit code of pod2man, but I have verified that this patchset doesn't
break the build with perl 5.14 (sid).

[1] <https://rt.cpan.org/Public/Bug/Display.html?id=39007>

When I wrote this, I mistakenly thought that only some pod2man errors
would trigger this issue with perl 5.18, but that seems unlikely. I
was mislead by the fact that the manpages get installed in a different
order to the order they are generated. So all the POD fixes logically
sit in #708718, not this bug.