This is automatically generated email about problems in a man page for which you appear to be responsible. If you are not the right person or list, tell me and I will attempt to correct my database.
In the last mailing (20 Nov 2004) of these reminders, a bug in my script suppressed the sending of second and subsequent patches associated with a maintainer. This resend is going only to maintainers with multiple patches; the first one may be one you have already processed. I apologize for any inconvenience this may cause. See http://catb.org/~esr/doclifter/problems.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the mod date of any manual page. You may wish to do that by hand. Problems with AnyDBM_File.3pm: (May reflect bugs in POD). 1. There are multiple name lines. This makes it impossible to translate the page to DocBook. It may also confuse some implementations of man -k. --- AnyDBM_File.3pm-orig 2004-11-17 23:10:32.174714560 -0500 +++ AnyDBM_File.3pm 2004-11-17 23:11:46.801369584 -0500 @@ -131,9 +131,7 @@ .IX Title "AnyDBM_File 3pm" .TH AnyDBM_File 3pm "2001-09-21" "perl v5.8.5" "Perl Programmers Reference Guide" .SH "NAME" -AnyDBM_File \- provide framework for multiple DBMs -.PP -NDBM_File, DB_File, GDBM_File, SDBM_File, ODBM_File \- various DBM implementations +AnyDBM_File, NDBM_File, DB_File, GDBM_File, SDBM_File, ODBM_File \- framework for multiple DBMs, and the implementations thereof .SH "SYNOPSIS" .IX Header "SYNOPSIS" .Vb 1 ----------------------------- Problems with Apache::TestConfig.3pm: (May reflect bugs in POD). 1. There are multiple name lines. This makes it impossible to translate the page to DocBook. It may also confuse some implementations of man -k. --- Apache::TestConfig.3pm-orig 2004-11-19 06:09:08.950587752 -0500 +++ Apache::TestConfig.3pm 2004-11-19 06:10:20.157762616 -0500 @@ -131,9 +131,7 @@ .IX Title "Apache::TestConfig 3" .TH Apache::TestConfig 3 "2004-08-06" "perl v5.8.5" "User Contributed Perl Documentation" .SH "NAME" -Apache::TestConfigData \- Configuration file for Apache::Test -.SH "NAME" -Apache::TestConfig \-\- Test Configuration setup module +Apache::TestConfig, Apache::TestConfigData \- Test Configuration setup module snd configuration file .SH "SYNOPSIS" .IX Header "SYNOPSIS" .Vb 1 ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::Config.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::Config.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::H2Z.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::Config.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::H2Z.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::JIS7.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::Config.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::H2Z.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::JIS7.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with KR::2022_KR.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::Config.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::H2Z.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::JIS7.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with KR::2022_KR.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::Plugin::Hashcash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::Config.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::H2Z.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::JIS7.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with KR::2022_KR.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::Plugin::Hashcash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::Plugin::SPF.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::Config.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::H2Z.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::JIS7.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with KR::2022_KR.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::Plugin::Hashcash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::Plugin::SPF.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::PluginHandler.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with B::Stash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp::Heavy.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CJKConstants.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::CN::HZ.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::Config.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::H2Z.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Encode::JP::JIS7.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with KR::2022_KR.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::Plugin::Hashcash.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::Plugin::SPF.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Mail::SpamAssassin::PluginHandler.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with NetSNMP::netsnmp_request_infoPtr.3pm: (May reflect bugs in POD). 1. Page is empty. This probably means there is some sort of glitch in your build machinery. (No patch.) ----------------------------- Problems with Carp.3pm: (May reflect bugs in POD). 1. There are multiple name lines. This makes it impossible to translate the page to DocBook. It may also confuse some implementations of man -k. --- Carp.3pm-orig 2003-12-15 09:23:36.000000000 -0500 +++ Carp.3pm 2003-12-15 09:25:06.000000000 -0500 @@ -131,18 +131,7 @@ .IX Title "Carp 3pm" .TH Carp 3pm "2002-06-01" "perl v5.8.0" "Perl Programmers Reference Guide" .SH "NAME" -carp \- warn of errors (from perspective of caller) -.PP -cluck \- warn of errors with stack backtrace - (not exported by default) -.PP -croak \- die of errors (from perspective of caller) -.PP -confess \- die of errors with stack backtrace -.PP -shortmess \- return the message that carp and croak produce -.PP -longmess \- return the message that cluck and confess produce +carp, cluck, croak, shortmess, longmess \- error-warning and exit facilities .SH "SYNOPSIS" .IX Header "SYNOPSIS" .Vb 2 ----------------------------- Problems with File::Basename.3pm: (May reflect bugs in POD). 1. There are multiple name lines. This makes it impossible to translate the page to DocBook. It may also confuse some implementations of man -k. --- File::Basename.3pm-orig 2003-12-15 09:45:12.000000000 -0500 +++ File::Basename.3pm 2003-12-15 09:46:35.000000000 -0500 @@ -131,11 +131,7 @@ .IX Title "File::Basename 3pm" .TH File::Basename 3pm "2002-06-01" "perl v5.8.0" "Perl Programmers Reference Guide" .SH "NAME" -fileparse \- split a pathname into pieces -.PP -basename \- extract just the filename from a path -.PP -dirname \- extract just the directory from a path +fileparse, basename, dirname \- extract segments, basename, or directory name from a filename .SH "SYNOPSIS" .IX Header "SYNOPSIS" .Vb 1 ----------------------------- Problems with Mail::SpamAssassin::Plugin.3pm: (May reflect bugs in POD). 1. List syntax error. This means .IP, .TP or .RS/.RE markup is garbled. This confuses doclifter, and may also mess up stricter troff interpreters like groffer and TkMan. --- Mail::SpamAssassin::Plugin.3pm-orig 2004-11-19 14:51:36.788991944 -0500 +++ Mail::SpamAssassin::Plugin.3pm 2004-11-19 14:52:27.907220792 -0500 @@ -523,7 +523,6 @@ .IP "any and all arguments as specified in the configuration file" 4 .IX Item "any and all arguments as specified in the configuration file" .RE -.RS 4 .PD .Sp In other words, the eval test method should look something like this: @@ -560,13 +559,10 @@ .IX Item "rawbody tests, fully decoded message as array reference" .IP "full tests, pristine message as scalar reference" 4 .IX Item "full tests, pristine message as scalar reference" -.RE -.RS 4 .PD .Sp The configuration file arguments will be passed in after the standard arguments. -.RE .IP "$plugin\->\fIinhibit_further_callbacks()\fR" 4 .IX Item "$plugin->inhibit_further_callbacks()" Tells the plugin handler to inhibit calling into other plugins in the plugin ----------------------------- Problems with ModPerl::Code.3pm: (May reflect bugs in POD). 1. Section or macro out of place; this confuses translators. --- ModPerl::Code.3pm-orig 2004-11-26 11:30:42.832668344 -0500 +++ ModPerl::Code.3pm 2004-11-26 11:31:50.518378552 -0500 @@ -130,8 +130,15 @@ .\" .IX Title "ModPerl::Code 3" .TH ModPerl::Code 3 "2004-08-20" "perl v5.8.5" "User Contributed Perl Documentation" +.SH "NAME" +ModPerl::Code \- Generate mod_perl glue code .SH "SYNOPSIS" .IX Header "SYNOPSIS" +.Vb 3 +\& use ModPerl::Code (); +\& my $code = ModPerl::Code->new; +\& $code->generate; +.Ve .SH "CONSTANTS" .IX Header "CONSTANTS" \&\s-1EOF\s0 @@ -263,15 +270,6 @@ .PP 1; _\|_END_\|_ -.SH "NAME" -ModPerl::Code \- Generate mod_perl glue code -.SH "SYNOPSIS" -.IX Header "SYNOPSIS" -.Vb 3 -\& use ModPerl::Code (); -\& my $code = ModPerl::Code->new; -\& $code->generate; -.Ve .SH "DESCRIPTION" .IX Header "DESCRIPTION" This module provides functionality for generating mod_perl glue code. ----------------------------- Problems with pcrepattern.3: 1. Ambiguous or invalid backslash. This doesn't cause groff a problem. but it confuses doclifter and may confuse older troff implementations. --- pcrepattern.3-orig 2004-02-16 02:34:32.000000000 -0500 +++ pcrepattern.3 2004-02-16 02:36:14.000000000 -0500 @@ -1212,7 +1212,7 @@ can put a number less than 256 after the letter C. The default value is zero. For example, this pattern has two callout points: - (?C1)\dabc(?C2)def + (?C1)abc(?C2)def During matching, when PCRE reaches a callout point (and \fIpcre_callout\fR is set), the external function is called. It is provided with the number of the ----------------------------- Problems with pcrepattern.3: 1. Ambiguous or invalid backslash. This doesn't cause groff a problem. but it confuses doclifter and may confuse older troff implementations. --- pcrepattern.3-orig 2004-02-16 02:34:32.000000000 -0500 +++ pcrepattern.3 2004-02-16 02:36:14.000000000 -0500 @@ -1212,7 +1212,7 @@ can put a number less than 256 after the letter C. The default value is zero. For example, this pattern has two callout points: - (?C1)\dabc(?C2)def + (?C1)abc(?C2)def During matching, when PCRE reaches a callout point (and \fIpcre_callout\fR is set), the external function is called. It is provided with the number of the ----------------------------- Problems with pcrecallout.3: 1. Ambiguous or invalid backslash. This doesn't cause groff a problem. but it confuses doclifter and may confuse older troff implementations. --- pcrecallout.3-orig 2004-02-16 02:41:26.000000000 -0500 +++ pcrecallout.3 2004-02-16 02:41:33.000000000 -0500 @@ -17,7 +17,7 @@ a number less than 256 after the letter C. The default value is zero. For example, this pattern has two callout points: - (?C1)\dabc(?C2)def + (?C1)abc(?C2)def During matching, when PCRE reaches a callout point (and \fIpcre_callout\fR is set), the external function is called. Its only argument is a pointer to a ----------------------------- Problems with XML::DOM::Element.3pm: (May reflect bugs in POD). 1. pod2man generates an unbalanced .RS tag. This is a bug. --- XML::DOM::Element.3pm-orig 2004-07-26 11:40:06.063084928 -0400 +++ XML::DOM::Element.3pm 2004-07-26 11:40:22.241625416 -0400 @@ -272,7 +272,6 @@ .IX Item "NOT_FOUND_ERR" Raised if oldAttr is not an attribute of the element. .RE -.RS 4 .Sh "Additional methods not in the \s-1DOM\s0 Spec" .IX Subsection "Additional methods not in the DOM Spec" .IP "setTagName (newTagName)" 4 ----------------------------- -- Eric S. Raymond
