-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pod/buildtoc: generates warnings and errors in pod/perltoc.pod #16595
Comments
From @jkeenanThe program 'pod/buildtoc' is nearly the last step run by 'make'. It ##### $ podchecker `perldoc -l perltoc` I get what is effectively the same in perl-5.28.0 (so, not a regression): ##### 1. The unresolved link 'Other Properties' has its origin in ##### 2. The unresolved links 'runtests' and 'summary' come from ##### When I run pod/perlunicode.pod and cpan/Test-Harness/lib/TAP/Harness.pm Thank you very much. |
From @jkeenanSummary of my perl5 (revision 5 version 28 subversion 0) configuration: Characteristics of this binary (from libperl): |
From @xsawyerxYup. This was caused by my release. I'm working on it and will push On 06/23/2018 04:53 AM, James E Keenan (via RT) wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Sat, 23 Jun 2018 15:22:31 GMT, xsawyerx@gmail.com wrote:
Well, not entirely your fault. The errors processing TAP::Harness can be found in perl-5.24.1. See below.
##### -- |
From @xsawyerxI've finished all the steps for fixing the perltoc and preparing blead Could you please confirm it is resolved, Jim? On 06/23/2018 07:16 PM, James E Keenan via RT wrote:
|
From @jkeenanOn Sun, 24 Jun 2018 08:22:54 GMT, xsawyerx@gmail.com wrote:
I don't see any change in the status of pod/perltoc.pod. ##### But I don't think that's due to anything you have or have not done. I think it's probably a long-standing implementation defect in pod/buildtoc. So this is not an impediment to perl-5.29.0. Were you getting errors different from these? |
Is this still a problem? |
The last two POD-formatting errors reported by running
These can be averted by using C<> rather than L</>. I have filed this patch upstream: (However, given that on CPAN the TAP-Harness distribution is in |
In blead (v5.37.1-51-g6e37db9b2e), we are now getting 7 instances of this kind of warning when running
All but the first are situations where we have two
Examining
|
Addressed by @khwilliamson in e91f88a.
Since this is not unreasonable coding, I think we can live with these 6 flaws.
And, as noted in #16595 (comment), a patch has been submitted upstream for the two So there's nothing more that P5P can practically do here. Closing ticket. |
Migrated from rt.perl.org#133296 (status was 'open')
Searchable as RT133296$
The text was updated successfully, but these errors were encountered: