| Summary: | Drakconf (and other tools) still in English after locale change in draklocale | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Arnaud Vacquier <arnaud> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | rverschelde, thierry.vignaud |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakxtools-16.26.7-1.mga4 | CVE: | |
| Status comment: | |||
|
Description
Arnaud Vacquier
2014-04-13 15:21:34 CEST
what was saying 'locale' ? Hi, It is Akien write this bug. We switch English LiveCD to France/french (country,keyboard...) system I was with Arnaud when we got the bug during an install party. I also got it on my laptop a year ago, but back then I did not take the time to try to understand it. IIRC, all locales were set correctly after French was chosen in draklocale. I think I have an idea about where the issue might come from: both rpmdrake and mageiawelcome translations are packaged using the %find_lang macro. IIUC, this macro does that only the translations corresponding to the installed locales are installed, when one installs rpmdrake or mageiawelcome. Therefore, when installing from the English LiveCD, rpmdrake and mageiawelcome (and probably others) come only with the English locale. Once the system locale has been changed to French, the corresponding LC_MESSAGES can't be found and it falls back to English. Reinstalling the faulty packages afterwards lets the %find_lang magic operate again, and pulls in the correct translations. I'm not sure my understanding of translation packaging is accurate though. On my current system, I see that I have e.g. rpmdrake.mo in da/LC_MESSAGES and es/LC_MESSAGES even though I haven't installed those locales. Maybe only the rpmdrake and mageiawelcome packages from the LiveCD lack the translations? CC:
(none) =>
remi Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED |