Bug 724962

Summary:	sed testsuite doesn't set up locales correctly
Product:	Red Hat Enterprise Linux 6	Reporter:	Marek Polacek <mpolacek>
Component:	sed	Assignee:	Vojtech Vitek <vvitek>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-tools-bugs
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.2	CC:	hripps, ovasik, pmuller
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 14:47:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Marek Polacek 2011-07-22 12:41:25 UTC

Description of problem:

When the testsuite is run with LC_* set up like this:

LC_CTYPE=C
LC_COLLATE=C 
LC_NUMERIC=C 
LC_MONETARY=C 
LC_MESSAGES=C 
LC_TIME=en_US 

we get 4 fails (utf8-[1234]).  This shouldn't happen, it e.g. breaks
rpmbuild.

Version-Release number of selected component (if applicable):
sed-4.2.1-6.el6

How reproducible:
Always.

Steps to Reproduce:
1. Run testsuite with the LC_* set up like above.
2.
3.
  
Actual results:
utf8-[1234] test cases fail.

Expected results:
utf8-[1234] all test cases pass.

Additional info:

Comment 2 RHEL Program Management 2011-07-22 12:58:19 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. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 11 errata-xmlrpc 2012-06-20 14:47:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0955.html