Bug 568361
Summary: | Additional langpacks are not installed when language changed | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> |
Component: | yum-langpacks | Assignee: | Jens Petersen <petersen> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | i18n-bugs, petersen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-10-27 09:25:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kamil Páral
2010-02-25 14:58:45 UTC
The same problem for PackageKit integration, I don't know how to have pl translation automatically installed. I tried installing other packages, I tried to display the list of available updates - no eclipse-nls-pl there. yum-langpacks only kicks in when there is a package update available I think. This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I think this is basically a limitation of yum. At least the plugin currently will only see langpacks for a new language when there is base package update. But if you have a example or counterexample for a different plugin say I can try to look more into how this might be done. I think there might also be a lot of yum overhead if we have to check for langpacks for any installed package in every yum transaction. So may be the current way is a reasonable compromise if not perfect. I understand. So what's the proposed solution - you close this bug as WONTFIX and I'll update the test case instructions and put a note there about this use case (saying it's not supported)? (In reply to comment #5) > I understand. So what's the proposed solution - you close this bug as WONTFIX > and I'll update the test case instructions and put a note there about this use > case (saying it's not supported)? Yes, thank you - sounds good to me. If later we find a better way to handle this case perhaps we can reopen and revisit. |