Red Hat Bugzilla – Bug 493563
rename kde-l10n-Bengali to kde-l10n-Bengali-India
Last modified: 2015-07-13 13:37:21 EDT
Description of problem:
Our release is missing various package, where upstream released those
I have list of few packages:
Bengali India (bn-IN)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. search for any of above lang pack on fedora rawhide
can be as upstream providing
Should be fixed in the next release, leaving this open for tracking
Has been fixed in 4.2.2
Bengali (India) Package is not available yet. All other available.
You have 4.2.1, I have stated it had been fixed in 4.2.2
Affirmative to #5. As per discussion with ltinkl on #fedora-kde this has been partially fixed for 4.2.2. The kde-10n-bengali package is the upstream Bengali(India) package and the name would be fixed by ltinkl shortly for 4.2.4. Retaining this bug as CLOSED. Apologies for the confusion.
Reopening this bug.
The latest build on koji (4.2.4-2) still mentiones this package as kde-l10n-Bengali. The information mentioned says that this package provides 'kde-l10n-Bengali' and 'kde-l10n-bn_IN'. Although the latter is correct but 'kde-l10n-Bengali' needs to be changed to 'kde-l10n-Bengali-India' (for instance, similar to 'kde-l10n-Chinese-Traditional').
This is to avoid confusion in future when the 'kde-l10n-bn' langpack lands up again upstream and would be the primary candidate for the 'kde-l10n-Bengali' name. The bn team missed the current release but are an existing team upstream.
ltinkl any updates?
Steven M. Parrish - KDE Triage Master
- PackageKit Triager
Fedora Bugzappers volunteer triage team
I'll make the change in rawhide for 4.3
Will land with KDE 4.3.0 (rawhide, F11, F10)
I'm taking the liberty of doing
in comps too. This affects the following comps lang-related groups:
Consistently setting the status of everything blocked by KDE 4.3.0 to ON_QA. I'll mass-change them to CLOSED ERRATA once the update hits stable.
This issue should be resolved in Fedora 10 and 11 with the KDE 4.3.0 update, which just got pushed to stable. If the issue persists after upgrading to KDE 4.3.0, please report that fact in this bug report.