Bug 953798 - perl-PDL seems unable to find its documentation
Summary: perl-PDL seems unable to find its documentation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-PDL
Version: 18
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-19 08:37 UTC by David Jansen
Modified: 2014-02-05 20:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 815398
Environment:
Last Closed: 2014-02-05 20:42:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Jansen 2013-04-19 08:37:34 UTC
+++ This bug was initially created as a clone of Bug #815398 +++

Description of problem:
When using the help command inside pdl, it reports that there is no documentation

Version-Release number of selected component (if applicable):
perl-PDL-2.4.10-4.fc18.x86_64

How reproducible:


Steps to Reproduce:
1. Start pdl
2. Type: help 'help' (as suggested on the page that is shown when using the help command)
  
Actual results:
perlDL shell v1.354_001
 PDL comes with ABSOLUTELY NO WARRANTY. For details, see the file
 'COPYING' in the PDL distribution. This is free software and you
 are welcome to redistribute it under certain conditions, see
 the same file for details.
ReadLines, NiceSlice, MultiLines  enabled
Reading PDL/default.perldlrc...
Found docs database /usr/lib64/perl5/vendor_perl/PDL/pdldoc.db
Type 'help' for online help
Type 'demo' for online demos
Loaded PDL v2.4.10 (supports bad values)

Note: AutoLoader not enabled ('use PDL::AutoLoader' recommended)

pdl> help 'help'
No PDL docs for 'PDL::Doc::Perldl'. Using 'whatis'. (Try 'apropos PDL::Doc::Perldl'?)

'PDL::Doc::Perldl'

pdl> 


Expected results:
The build-in help on the help system (or any other perldl topic for that matter)

Additional info:
Same result when the separate command 'pdldoc' is used from outside pdl.


Bug cloned and updated, as suggested after F16 end of life, since the bug is still present.

Comment 1 Fedora Admin XMLRPC Client 2013-08-12 13:03:54 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora End Of Life 2013-12-21 12:53:45 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2014-02-05 20:42:44 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.