Bug 12505 - [Tracker] for Mageia 4 urgent updates of translations changed or broken just before the release but after translation freeze
Summary: [Tracker] for Mageia 4 urgent updates of translations changed or broken just ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: High major
Target Milestone: Mageia 4
Assignee: Colin Guthrie
QA Contact: Internationalisation Team
URL:
Whiteboard:
Keywords:
Depends on: 12497 12498 12667
Blocks:
  Show dependency tree / graph
 
Reported: 2014-02-01 20:35 CET by Filip Komar
Modified: 2014-03-18 10:23 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Filip Komar 2014-02-01 20:35:09 CET 
Tracker bug for Mageia 4 urgent updates of translations.


See previous discussion in dev:
https://ml.mageia.org/l/arc/dev/2014-01/msg01253.html
https://ml.mageia.org/l/arc/dev/2014-02/msg00008.html

or i18n-discuss ML:
https://ml.mageia.org/l/arc/i18n-discuss/2014-01/msg00188.html
https://ml.mageia.org/l/arc/i18n-discuss/2014-02/msg00001.html


Let's add such "l10n broken" Mageia packages we discover here.

Reproducible: 

Steps to Reproduce:
Filip Komar 2014-02-01 20:44:53 CET

Priority: Normal => High
CC: sysadmin-bugs => filip.komar
Target Milestone: --- => Mageia 4

Alex Loginov 2014-02-01 22:23:14 CET

CC: (none) => loginov_alex

Manuel Hiebel 2014-02-01 22:41:42 CET

Depends on: (none) => 12498, 12497
QA Contact: (none) => i18n-bugs

Comment 1 Filip Komar 2014-02-01 23:24:09 CET 
@Alex

Did you already opened a bug report for the translation error you noticed?

QA Contact: i18n-bugs => (none)

Filip Komar 2014-02-01 23:25:03 CET

QA Contact: (none) => i18n-bugs

Manuel Hiebel 2014-02-09 20:01:02 CET

Depends on: (none) => 12667

Comment 2 Alex Loginov 2014-03-18 09:57:15 CET 
Maybe all were fixed and it's time to close bug?
Comment 3 Filip Komar 2014-03-18 10:23:57 CET 
(In reply to Alex Loginov from comment #2)
> Maybe all were fixed and it's time to close bug?

Indeed. Thanks Alex. We can still reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.