invalid-lc-messages-dir and incorrect-fsf-address

[callkalpa]

I was trying to package Paths for fedora and got the following errors from rpmlint on the rpm file

sugar-paths.noarch: W: non-standard-group Sugar/Activities
sugar-paths.noarch: E: incorrect-fsf-address /usr/share/sugar/activities/Paths.activity/constants.py
sugar-paths.noarch: E: invalid-lc-messages-dir /usr/share/locale/cpp/LC_MESSAGES/org.sugarlabs.PathsActivity.mo
sugar-paths.noarch: E: invalid-lc-messages-dir /usr/share/locale/nah/LC_MESSAGES/org.sugarlabs.PathsActivity.mo
sugar-paths.noarch: E: invalid-lc-messages-dir /usr/share/locale/son/LC_MESSAGES/org.sugarlabs.PathsActivity.mo
sugar-paths.noarch: E: incorrect-locale-subdir /usr/share/locale/templates/LC_MESSAGES/org.sugarlabs.PathsActivity.mo
sugar-paths.noarch: E: invalid-lc-messages-dir /usr/share/locale/templates/LC_MESSAGES/org.sugarlabs.PathsActivity.mo
sugar-paths.noarch: E: invalid-lc-messages-dir /usr/share/locale/ton/LC_MESSAGES/org.sugarlabs.PathsActivity.mo

[walter]

Again, we have a situation where by there are languages which are not yet supported by Fedora. I think the short-term solution is to remove these languages.

[cjl]

I completely agree with that solution. It is unfortunate that there are not upstream efforts in all of our languages, but we are often trying to be the first native language computing experience in under-served areas, so we will run into that. I think handling it pragmatically is the best way to go. Sorry for the inconvenience to the packager and I greatly appreciate the packaging effort.

I suspect that in most of these cases there are no translated strings in the PO file anyway.

We are working to develop and upstream new glibc locales where there is an active effort, but I would not want to take down any languages from Pootle, I'd rather try to recruit localizers.

I would say, delete these PO files in the local environment prior to packaging and then close this ticket.

[callkalpa]

still

sugar-paths.noarch: E: incorrect-fsf-address /usr/share/sugar/activities/Paths.activity/constants.py

is there

[cjl]

Walter, I'm not sure I can explain the issue in callkalpa's last comment, do you have an answer?

[callkalpa]

cjl, it's nothing to do with localization. the fsf address is wrong in one of the files. walter will issue a patch or a new release with the issue fixed.

[cjl]

Ok, glad to hear it's not another L10n issue that's tripped you up

:-)

Thank you for the packaging you are doing. It is great that these activities will reach a wider audience through your efforts, it is much the same way I feel about what I try to do by working on L10n, it is all about reaching the largest possible audience and leveraging the existing work as much as possible.

[walter]

Since this is really not a bug specific to Paths, I will close the ticket.