| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 10manpages.diff | Add MAN3PODS section to Makefile.PL | no | ||||
| 20do_one_loop.diff | Guard $caller for undefinedness | no | ||||
| 30irctest.diff | Add warning to potentially security compromising example script | no | ||||
| 40handler.diff | Guard calling $self->{_parent}->handler() with can() | no | ||||
| 50fix_next_outside_loop_with_return.diff | DCC.pm: Don't use next inside a function, use return instead. | no | ||||
| 60warnings_from_unknown_event.diff | Several guards around handling Net::IRC::Event objects | no | ||||
| 70interactive-makefile-pl.diff | Make Makefile.PL non-interactive =================================================================== |
no | ||||
| 80fix_pod_errors.diff | Fix (partially valid) POD syntax claimed to be erroneous by pod2man pod2man is known to issue "Expected text after =item, not a number" errors despite "perldoc perlpod" (as of Perl 5.26.1) clearly states 'use "=item 1.", "=item 2.", etc., to produce numbered lists'. . It seems that pod2man doesn't dislike numbers in general, but dislikes one specific number: Zero. So the fix is to change all cases of "=item 0." to "=item 1." and bump all further cases of "=item <some number>" by adding 1, too. . The remaining issue is a real error, a misbalance between "=over" and "=back". While the error messages states "You forgot a '=back' before '=head1'", it seems to me as if there's an "=over" too many. Removing that fixes the last issue, too. |
Axel Beckert <abe@debian.org> | no |