Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#3178 closed defect (fixed)


Reported by: callkalpa Owned by: walter
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Portfolio Version: Unspecified
Severity: Unspecified Keywords: Portfolio, packaging,
Cc: walter, cjl Distribution/OS: OLPC
Bug Status: Unconfirmed


I was trying to package portfolio and I got the following error when I run rpmlint over the srpm

sugar-portfolio.noarch: E: invalid-lc-messages-dir /usr/share/locale/son/LC_MESSAGES/

Change History (4)

comment:1 Changed 12 years ago by walter

  • Cc walter cjl added; walter@… removed

As I recall there is an issue with some mismatch between the list of locales we maintain and those maintained by Fedora? CJL, can you please chime in?

comment:2 Changed 12 years ago by cjl

Sounds very possible, we are in the process of trying to get some glibc locales upstreamed.

If the language is not listed here:

I would skip it when packaging for Fedora.

comment:3 Changed 12 years ago by callkalpa

  • Resolution set to fixed
  • Status changed from new to closed

skipped that locale

comment:4 Changed 12 years ago by cjl

You have arrived at the proper resolution for the packaging issue.

The Songhay languages:

were established on our Pootle server when we took on hosting of AbiWord, including those languages previously hosted by the African Localization project (AnLoc).

We have been fortunate that the Songhay localizer has done some additional work on Sugar L10n besides AbiWord. Given the distribution of this language group (Mali, Niger, Benin, Burkina Faso, Nigeria) it is certainly of interest, but it can be expected that it will be slow to develop to completion. Upstreaming a glibc locale will eventually be needed, but in the meantime, it is another situation where our L10n efforts lead the upstream in minority languages.

This is both good news in that we are creating an entry point for native language computing in this language and bad news in that it's upstream support has not caught up with these embryonic efforts.

I completely agree with your pragmatic approach and appreciate your understanding of why these situations occur.

Note: See TracTickets for help on using tickets.