| Summary: | `perldoc perldoc`: No documentation found for "perldoc". | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vadim Raskhozhev <iamdexpl> | |
| Component: | perl-Pod-Perldoc | Assignee: | Petr Pisar <ppisar> | |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 19 | CC: | gp, mmaslano, perl-devel, ppisar | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | perl-Pod-Perldoc-3.20-7.fc20 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1015993 (view as bug list) | Environment: | ||
| Last Closed: | 2013-11-10 06:16:59 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
|
Description
Vadim Raskhozhev
2013-09-19 20:15:41 UTC
You can use `perldoc Pod::perldoc'. This is upstream change since version 3.17. I raised a question if this is intended behaviour <https://rt.cpan.org/Public/Bug/Display.html?id=88898>. And of course the classic `man perldoc' works. > I raised a question if this is intended behaviour <https://rt.cpan.org/Public/Bug/Display.html?id=88898>.
Thanks. IMHO if this is intended then the line 'Also try "perldoc perldoc" to get acquainted with the system.' in output of `perldoc' should somehow point to `perldoc Pod::perldoc', `man perldoc' or so.
I configured the current stable perl source (5.18.1) with: ./configure.gnu --prefix=/home/blabla/install and installed it (make install). The following works: For command output: /home/blabla/install/bin/perldoc perldoc For Perl5 module output: /home/blabla/install/bin/perldoc Pod::Perldoc This doesn't work: /home/blabla/install/bin/perldoc Pod::Perldoc No documentation found for "Pod::perldoc". documentation as a Perl Utility perldoc: http://perldoc.perl.org/index-utilities.html <-> http://perldoc.perl.org/perldoc.html documentation as a Perl Module Pod::Perldoc: http://search.cpan.org/~mallen/Pod-Perldoc-3.20/lib/Pod/Perldoc.pm Sorry: This doesn't work: /home/blabla/install/bin/perldoc Pod::perldoc No documentation found for "Pod::perldoc". Upstream is not responsive. I will fix this issue by moving perldoc.pod to the root of Perl search path to make restore the `perldoc perldoc' command. F≥19 are affected. perl-Pod-Perldoc-3.20-7.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-Pod-Perldoc-3.20-7.fc20 perl-Pod-Perldoc-3.19.01-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/perl-Pod-Perldoc-3.19.01-2.fc19 Package perl-Pod-Perldoc-3.20-7.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-Pod-Perldoc-3.20-7.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18464/perl-Pod-Perldoc-3.20-7.fc20 then log in and leave karma (feedback). (In reply to Petr Pisar from comment #6) > Upstream is not responsive. I will fix this issue by moving perldoc.pod to > the root of Perl search path to make restore the `perldoc perldoc' command. > > F≥19 are affected. Thanks, with 3.19.01-2 perldoc perldoc works as expected. Should I close the bug now? Thank you for testing. This bug report gets closed automatically once the updated packages become into stable repository. There is not action needed from you. perl-Pod-Perldoc-3.19.01-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. perl-Pod-Perldoc-3.20-7.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |