Bug 1310137 - Wrong exit status from rgb2ycbcr on error output
Summary: Wrong exit status from rgb2ycbcr on error output
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libtiff
Version: 6.7
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Nikola Forró
QA Contact: Miroslav Hradílek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 14:58 UTC by Miroslav Hradílek
Modified: 2017-12-06 10:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:17:25 UTC
Target Upstream Version:


Attachments (Terms of Use)
Return non-zero exit code from rgb2ycbcr and tiffinfo in case of an error (2.73 KB, patch)
2016-08-31 13:12 UTC, Nikola Forró
no flags Details | Diff

Description Miroslav Hradílek 2016-02-19 14:58:28 UTC
Description of problem:
rgb2ycbcr utility is exiting with status 0 even though it is reading incorrect data and reflecting this in errors. This causes false failures of several regression tests as status 1 is expected.

Version-Release number of selected component (if applicable):
libtiff-4.0.3-14.el7.x86_64
libtiff-tools-4.0.3-14.el7.x86_64

Comment 4 Nikola Forró 2016-08-31 13:12:10 UTC
Created attachment 1196362 [details]
Return non-zero exit code from rgb2ycbcr and tiffinfo in case of an error

Backport of this upstream commit: https://github.com/vadz/libtiff/commit/e8a47d4de54a5400c15a884094ae696195af5eb0

Comment 5 Jan Kurik 2017-12-06 10:17:25 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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