Bug 723509 - tomcat5-webapps contains unreadable PDF documentation
Summary: tomcat5-webapps contains unreadable PDF documentation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: tomcat5
Version: 5.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Knox
QA Contact: tomcat-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-20 12:00 UTC by Radek Bíba
Modified: 2015-11-02 00:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-10 07:31:21 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Radek Bíba 2011-07-20 12:00:51 UTC 
Description of problem:
The package contains these files:

/var/lib/tomcat5/webapps/tomcat-docs/architecture/requestProcess/requestProcess.pdf
/var/lib/tomcat5/webapps/tomcat-docs/architecture/startup/serverStartup.pdf

Neither of them can be displayed, though. PDF viewers print lots of error messages to the terminal, and rendered pages are mostly blank.

Version-Release number of selected component (if applicable):
tomcat5-5.5.23-0jpp.19.el5_6, the -webapps subpackage
Comment 1 RHEL Program Management 2011-09-23 00:54:56 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 2 RHEL Program Management 2014-03-07 13:33:35 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 3 Radek Bíba 2014-03-10 07:31:21 UTC 
Let's not wait, then.
Note You need to log in before you can comment on or make changes to this bug.