Bug 1480527 - [initial-setup] Tier 0 Localization
[initial-setup] Tier 0 Localization
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initial-setup (Show other bugs)
Unspecified Unspecified
high Severity unspecified
: rc
: ---
Assigned To: Martin Kolman
Engineering Localization bugs mailing list
: Translation
Depends On:
Blocks: 1473148
  Show dependency treegraph
Reported: 2017-08-11 06:20 EDT by Ludek Janda
Modified: 2018-03-12 08:50 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-19 03:44:11 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ludek Janda 2017-08-11 06:20:07 EDT
Description of problem:

This package is going to be localized in RHEL 7.5 as a part of the Tier 0 localization effort: 


The extent of this localization is going to be specified by RHEL 7 pm. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 7 sandeep shedmake 2017-12-19 03:44:11 EST
As per Comment 2 through Comment 6,

There is no change in message catalogs since RHEL-7.5-Alpha-1.0 compose (30 Nov. 2017), L10n: String Freeze (12 Dec. 2017) and RHEL-7.5-Beta-1.0 compose (15 Dec. 2017).

$ brew latest-build rhel-7.5-alpha-1.0-set initial-setup
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
initial-setup-              rhel-7.5-alpha-1.0-set  mkolman
$ brew latest-build rhel-7.5-beta-1.0-set initial-setup
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
initial-setup-              rhel-7.5-beta-1.0-set  mkolman

Thereby, closing this bug as NOTABUG at the moment.

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