Bug 1365486

Summary:	[RFE] Include support for C.UTF-8 locale in RHEL7
Product:	Red Hat Enterprise Linux 7	Reporter:	amit yadav <ayadav>
Component:	glibc	Assignee:	Carlos O'Donell <codonell>
Status:	CLOSED DUPLICATE	QA Contact:	qe-baseos-tools-bugs
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	ashankar, fweimer, mnewsome, pfrankli, sgehwolf
Target Milestone:	rc	Keywords:	FutureFeature, Patch
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-12 09:22:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	902094
Bug Blocks:

Description amit yadav 2016-08-09 11:28:58 UTC

Description of problem:
Please include support for C.UTF-8 locale in glibc-common available in RHEL7.

Version-Release number of selected component (if applicable):
glibc-common-2.17-106.el7_2.4

Actual results:
Unable to set C.UTF-8 locale in RHEL7

Expected results:
Should be able to set C.UTF-8 locale in RHEL7

Additional info:
Support for  C.UTF-8 locale was included in glibc-common:

$ cat /etc/redhat-release 
Fedora release 23 (Twenty Three)

$ locate C.utf8/usr/lib/locale/C.utf8
/usr/lib/locale/C.utf8/LC_ADDRESS
/usr/lib/locale/C.utf8/LC_COLLATE
/usr/lib/locale/C.utf8/LC_CTYPE
/usr/lib/locale/C.utf8/LC_IDENTIFICATION
/usr/lib/locale/C.utf8/LC_MEASUREMENT
/usr/lib/locale/C.utf8/LC_MESSAGES
/usr/lib/locale/C.utf8/LC_MONETARY
/usr/lib/locale/C.utf8/LC_NAME
/usr/lib/locale/C.utf8/LC_NUMERIC
/usr/lib/locale/C.utf8/LC_PAPER
/usr/lib/locale/C.utf8/LC_TELEPHONE
/usr/lib/locale/C.utf8/LC_TIME
/usr/lib/locale/C.utf8/LC_MESSAGES/SYS_LC_MESSAGES

$ rpm -qf /usr/lib/locale/C.utf8
glibc-common-2.22-17.fc23.x86_64

Reference bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=902094

Comment 3 Florian Weimer 2016-09-12 09:22:59 UTC


*** This bug has been marked as a duplicate of bug 1361965 ***