Description of problem: The directory /usr/share/locale/be@latin/LC_MESSAGES is not owned by any package. It also looks to me whether "be@latin" is the same like "be" but not with same charset etc. thus not provided by filesystem. Version-Release number of selected component (if applicable): glib2-2.12.11-1 How reproducible: Everytime, see above. Actual results: /usr/share/locale/be@latin/LC_MESSAGES is not owned Expected results: Kill "be@latin" or clarify with Bill whether this directory should be added to the filesystem package. IMHO providing "be" and "be@latin" is unnecessary.
So, my question would be why we have: sr@Latn uz@Latn but: be@latin?
I'm guessing because there's no standard anywhere regarding this. So When I would put rsc@mY$World" into some upstream package, this would get accepted by downstream somehow surely, too.
glibc people prefer "latin" over "Latn".
Can we get these latin vs. Latn to one common style so that they can be owned by the filesystem package?
> IMHO providing "be" and "be@latin" is unnecessary. This is not true. One is Belarussian in Cyrillic (the default), the other is Belarus in Latin. Moving to filesystem.
Bill, ping?
We have an exception file for @modifier in filesystem; it would need to be added there. Whether we want to simultaneously beat upstream into using latin instead of Latn, I don't know.
Added be@latin to lang-exceptions for now. Read ya, Phil