Am Donnerstag, 9. Juli 2015, 20:59:14 schrieb Axel Braun:
>> > - Why are the .mo files compiled without error (of course, >> > this >> > should be the standard case...)? >> >> Does this step use msgfmt? > > the command 'compile_catalog' in > python setup.py compile_catalog > is imported from python-babel - I assume it uses something > similar, > or > even the python implementation of msgfmt. Sorry, I'm just > packing, > not > programming.>>
That may be the answer to your first question.
Which one does 'That' refer to? python-babel or not programming`? In fact only some language files are effected by this error message, not all.
If the python implementation is inferior then you have the answer.
I have my doubts....I checked the file with poedit and then run msgfmt on it, result:
docb@T520:~/tryton/tryton-3.6.1/b/share/locale/nl_NL/LC_MESSAGES> msgfmt -v -c tryton.po 278 übersetzte Meldungen, 61 ungenaue Übersetzungen, 63 unübersetzte Meldungen.
I use the .mo file generated by msgfmt, but still the error remains: [ 19s] + /usr/lib/rpm/find-lang.sh /home/abuild/rpmbuild/BUILDROOT/tryton-3.6.1-0.i386 tryton --without-C [ 19s] removing translation /usr/share/locale/nl_NL/LC_MESSAGES/tryton.mo: 278 translated messages.
There is no error in the above. The "removing translation" are informative.
Exactly! But my latest comment does not refer to the original message! I removed all languages in error from the tarball, just left one language in, and edited this with poedit, and generated an mo file with msgfmt. And the output of msgfmt -v -c tryton.po returned no errors
The error is this from your original log: "<stdin>:81: 'msgid' and 'msgstr' entries do not both end with '\n'" and that means that "msgunfmt $file | msgfmt --statistics -o /dev/null" is breaking, and that means that $file was incorrectly generated when the initial build didn't already complain.
docb@T520:~/tryton/tryton-3.6.1/share/locale/nl_NL/LC_MESSAGES> msgunfmt tryton.mo | msgfmt --statistics -o /dev/nul msgfmt: Eingabedatei fehlt »msgfmt --help« gibt weitere Informationen.
So yes, it's the python implementation of msgfmt that's broken.
Probably not. But bottom line is that msgfmt does not issue an error, while %find_lang removed the .mo file.... Strange
...and even more weird. If I run the find-lang script against the sources it works like charm: T520:/var/tmp/build-root/openSUSE_13.1- i586/home/abuild/rpmbuild/BUILD/tryton-3.6.1/share/locale/nl_NL # /usr/lib/rpm/find-lang.sh /var/tmp/build-root/openSUSE_13.1- i586/home/abuild/rpmbuild/BUILD/tryton-3.6.1 tryton find: ‘/var/tmp/build-root/openSUSE_13.1- i586/home/abuild/rpmbuild/BUILD/tryton-3.6.1/usr/share/locale/’: Datei oder Verzeichnis nicht gefunden find: ‘/var/tmp/build-root/openSUSE_13.1- i586/home/abuild/rpmbuild/BUILD/tryton-3.6.1/usr/share/help/’: Datei oder Verzeichnis nicht gefunden The tryton.lang file that was created: %defattr (644, root, root, 755) %lang(cs) /share/locale/cs_CZ/LC_MESSAGES/tryton.mo %lang(de) /share/locale/de_DE/LC_MESSAGES/tryton.mo %lang(es) /share/locale/es_AR/LC_MESSAGES/tryton.mo %lang(es) /share/locale/es_CO/LC_MESSAGES/tryton.mo %lang(es) /share/locale/es_EC/LC_MESSAGES/tryton.mo %lang(es) /share/locale/es_ES/LC_MESSAGES/tryton.mo %lang(fr) /share/locale/fr_FR/LC_MESSAGES/tryton.mo %lang(nl) /share/locale/nl_NL/LC_MESSAGES/tryton.mo %lang(ru) /share/locale/ru_RU/LC_MESSAGES/tryton.mo %lang(sl) /share/locale/sl_SI/LC_MESSAGES/tryton.mo -> contains the nl_NL entry that was causing the trouble. Is this an OBS error then? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org