RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 510258 - tiffcp options differ in program help and manual page
Summary: tiffcp options differ in program help and manual page
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libtiff
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: beta
: 7.0
Assignee: Jaromír Končický
QA Contact: Miroslav Vadkerti
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-08 14:04 UTC by Miroslav Vadkerti
Modified: 2014-06-18 08:46 UTC (History)
4 users (show)

Fixed In Version: libtiff-4.0.3-8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:12:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Miroslav Vadkerti 2009-07-08 14:04:14 UTC
Description of problem:
tiffcp's program help contains some options unexplained in manual page and some options in manual page are not present in program help. 
3 option(s) reported by the program ONLY:
	-a
	-i
	-o
5 option(s) reported by the man page ONLY:
	-1
	-B
	-C
	-L
	-M

Version-Release number of selected component (if applicable):
libtiff-3.8.2-7.el5_3.3
libtiff-3.6.1-12.el4_8.3
libtiff-3.5.7-32.el3


How reproducible:
always

Steps to Reproduce:
1. tiffcp -h
2. man tiffcp
3. compare options
  
Actual results:
There are differences between program help and manual pages.

Expected results:
No differences

Additional info:
This bug also appears in RHEL-3 and RHEL-4

Comment 1 Tom Lane 2013-03-06 03:39:25 UTC
I've fixed this upstream, so it should appear in RHEL7, but I don't think we will bother anymore to fix it in RHEL5.

Comment 2 Miroslav Vadkerti 2013-03-06 08:42:05 UTC
I think this bug could be moved to RHEL7 and should be tested by QE, reopenning.
Tom can we get a NVR of the fixed EL7 build please?

Comment 3 Miroslav Vadkerti 2013-08-12 08:28:57 UTC
Moving back to assigned. Still not fixed in current RHEL7 release libtiff-4.0.3-6.el7.

Comment 4 Miroslav Vadkerti 2013-08-12 08:33:39 UTC
I will test this bug. Testing is easy with options comparator. Cover in TCMS together with bug 510240.

Comment 6 Miroslav Vadkerti 2013-10-01 07:27:27 UTC
Thanks for the fixes, looks like the only one left missing is:

1 option(s) reported by the program ONLY:
        -8

I do not see this explained in the **man page**.

Comment 8 Petr Hracek 2013-10-08 08:26:58 UTC
cvs-commit (http://bulk-mail.corp.redhat.com/archives/cvs-commits-list/2013-October/msg02285.html) -> MODIFIED

Comment 11 Ludek Smid 2014-06-13 11:12:56 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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