[Koha-bugs] [Bug 2400] New: fix POD bugs reported by xt/author/podcorrectness.t

[bugzilla-daemon at pippin.metavore.com]

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2400

           Summary: fix POD bugs reported by xt/author/podcorrectness.t
           Product: Koha
           Version: HEAD
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Command-line Utilities
        AssignedTo: Andrew.moore at liblime.com
        ReportedBy: galen.charlton at liblime.com
         QAContact: koha-bugs at lists.koha.org


To make the POD test more useful, clean up in one swell foop the errors it
currently reports, e.g.:

xt/author/podcorrectness......1/119 
#   Failed test 'C4/Acquisition.pm'
#   at /usr/local/share/perl/5.8.8/Test/Pod.pm line 159.
# C4/Acquisition.pm (67): You forgot a '=back' before '=head2'
# C4/Acquisition.pm (71): You forgot a '=back' before '=head3'
# C4/Acquisition.pm (84): =back without =over
# C4/Acquisition.pm (165): =back without =over
# C4/Acquisition.pm (175): You forgot a '=back' before '=head3'
# C4/Acquisition.pm (299): You can't have =items (as at line 307) unless the
first thing after the =over is an =item
# C4/Acquisition.pm (795): =back without =over
# C4/Acquisition.pm (805): You forgot a '=back' before '=head3'
# C4/Acquisition.pm (879): You can't have =items (as at line 886) unless the
first thing after the =over is an =item
# C4/Acquisition.pm (1211): =back without =over

#   Failed test 'C4/Scheduler.pm'
#   at /usr/local/share/perl/5.8.8/Test/Pod.pm line 159.
# C4/Scheduler.pm (139): You forgot a '=back' before '=head1'

#   Failed test 'C4/Log.pm'
#   at /usr/local/share/perl/5.8.8/Test/Pod.pm line 159.
# C4/Log.pm (183): You forgot a '=back' before '=head2'
# C4/Log.pm (232): =back without =over

#   Failed test 'C4/Reports.pm'
#   at /usr/local/share/perl/5.8.8/Test/Pod.pm line 159.
# C4/Reports.pm (654): You forgot a '=back' before '=head1'




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.