Update known POD issues database

[jkeenan]

... by running:

cd t; ./perl -I../lib porting/podcheck.t --regen; cd -

This step apparently was missed during recent maintenance and dev releases.

---

• This set of changes does not require a perldelta entry.

[karenetheridge]

Something else is going on because make test_porting passes for me and definitely was passing when I released 5.41.11 and 5.41.12.

[jkeenan]

Something else is going on because make test_porting passes for me and definitely was passing when I released 5.41.11 and 5.41.12.

Agreed. Nonetheless, when I checkout either tag v5.41.12 or HEAD (v5.41.12-22-g9f37e119ab), do my regular configuration and call make test_porting, everything PASSes -- but then when I call cd t; ./perl -I../lib porting/podcheck.t --regen; cd - I get 6 +/- change lines in the diff for t/porting/known_pod_issues.dat.

[khwilliamson]

This is wrong; I hadn't been paying enough attention to this or to my commit that ended up adding the perldelta entries.

It should not be necessary to regen this data file each release, unless new pod problems get introduced. But that is the point of this test, to alert one to new pod issues, which should be corrected if at all possible. I'll look at podcheck.t and fix it. But this PR should be closed, and I'll revert 1fb05c6

[jkeenan]

Something else is going on because make test_porting passes for me and definitely was passing when I released 5.41.11 and 5.41.12.

Agreed. Nonetheless, when I checkout either tag v5.41.12 or HEAD (v5.41.12-22-g9f37e119ab), do my regular configuration and call make test_porting, everything PASSes -- but then when I call cd t; ./perl -I../lib porting/podcheck.t --regen; cd - I get 6 +/- change lines in the diff for t/porting/known_pod_issues.dat.

Per further investigation on 5.41.12: This problem occurs both in the repository (tag v5.41.12) and when building from a download tarball.

We get different differences with tag v5.41.10.

[khwilliamson]

Replaced by #23245