Bug 510285 - tiffdiff has no manual page
Summary: tiffdiff has no manual page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lcms
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Richard Hughes
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-08 15:14 UTC by Miroslav Vadkerti
Modified: 2014-09-08 12:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:01:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Miroslav Vadkerti 2009-07-08 15:14:43 UTC 
Description of problem:
The tool tiffdiff has no manual page

Version-Release number of selected component (if applicable):
libtiff-3.8.2-7.el5_3.3

How reproducible:
always

Steps to Reproduce:
1. man tiffdiff
  
Actual results:
No manual page

Expected results:
Manual page for tiffdiff shown
Comment 1 Tom Lane 2010-07-14 18:59:11 UTC 
Uh, there's no tiffdiff tool in the libtiff packages, AFAICS.  Maybe this needs to be refiled against some other package?
Comment 2 Miroslav Vadkerti 2010-07-15 04:43:04 UTC 
sorry, it should be lcms, reassigning
Comment 4 RHEL Program Management 2014-03-07 13:32:41 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 5 RHEL Program Management 2014-06-02 13:01:25 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Note You need to log in before you can comment on or make changes to this bug.