Bug 1459341 - Atomic Host images omit many common locales that all other flavors include
Summary: Atomic Host images omit many common locales that all other flavors include
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm-ostree
Version: 26
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-06 21:05 UTC by Adam Williamson
Modified: 2017-06-06 22:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-06 22:11:56 UTC
Type: Bug


Attachments (Terms of Use)

Description Adam Williamson 2017-06-06 21:05:41 UTC
Apparently, it was decided that Fedora Atomic Host images should include only the locales 'officially supported' by RHEL 7 - see https://bugzilla.redhat.com/show_bug.cgi?id=1430182 , jlebon says it was decided to apply the same choice to Fedora as to RHEL.

This is entirely out of step with all other Fedora flavors, though, I believe. These include far, far more locales. The 'RHEL supported' list doesn't include such obvious and widely-used locales as en_CA and en_AU. I'm not sure it makes sense to just decide the RHEL 'supported locales' list is an appropriate basis for the list of locales to include in Fedora images.

(not sure which component is best for this, picking rpm-ostree to get the appropriate people's attention).

Comment 1 Matthew Miller 2017-06-06 21:29:49 UTC
Hmmmm. We did something similar with the cloud image, but in that case, it was fairly easy to add back. Also, that was based on size not RHEL parity.

> (not sure which component is best for this, picking rpm-ostree to get the appropriate people's attention).

Probably https://pagure.io/atomic-wg/issues since it's a policy decision and since it's general rather than a specific component.

Comment 2 Colin Walters 2017-06-06 21:35:12 UTC
Yeah, I'd say we should track this as a WG issue indeed.

Comment 3 Adam Williamson 2017-06-06 22:11:56 UTC
https://pagure.io/atomic-wg/issue/282


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