regen podcheck after MPE port removed

Commit b5afd3466ff5e5b70ea2921169f138f02727183e removed the MPE/iX
port, which included a file that had known (to podcheck.t) pod errors
podcheck doesn't currently check if a pod has been removed, so its data
base still contained the offending entry, which would be removed the
next time it is regenerated for another unrelated reason.  This might
confuse spelunkers of perl history, so I'm regenerating it separately
now.

diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat
index b6073c3..259de18 100644 (file)
--- a/t/porting/known_pod_issues.dat
+++ b/t/porting/known_pod_issues.dat
@@ -252,7 +252,6 @@ pod/perlmacosx.pod  Verbatim line length including indents exceeds 79 by    3
 pod/perlmod.pod        Verbatim line length including indents exceeds 79 by    2
 pod/perlmodlib.pod     Verbatim line length including indents exceeds 79 by    3
 pod/perlmodstyle.pod   Verbatim line length including indents exceeds 79 by    2
-pod/perlmpeix.pod      Verbatim line length including indents exceeds 79 by    2
 pod/perlmroapi.pod     ? Should you be using L<...> instead of 1
 pod/perlnetware.pod    Verbatim line length including indents exceeds 79 by    4
 pod/perlnewmod.pod     Verbatim line length including indents exceeds 79 by    1