When emerging k3b-0.11.6 k3b-i18n is not compiled. This happens because the ebuild checks for $WORKDIR/k3b-i18n-0.11.6 where i18n is extracted to $WORKDIR/k3b-i18n-0.11. The comment in the ebuild that k3b-i18n-0.11 would be unpacked as k3b-i18n-0.11.6 doesn't seem to be true anymore. Setting SI18N="${WORKDIR}/${PN}-i18n-${PV%.*}" fixes this bug. Reproducible: Always Steps to Reproduce: Actual Results:
Damn, they changed the tarball upstream.
when will this be fixed? seems to be easy.
Created attachment 27668 [details] Try this one now... Should hopefully compile i18n (have not tested, but if the problem is only what reported it should work). Please test and feedback!
please always post diffs
works for me (at least for german i18n ;-))
Created attachment 27709 [details, diff] Patch to apply on _portage_ ebuild Ok, there are news. The Italian and Brazilian-Portuguese documentations disappeared, and since I had a LINGUAS environment with "it" in it (pun not intended...), I got a build failure. Strangely the "pt_BR" and "it" folders are still there in the tarball, though they do not contain an index.docbook file. Well, I double-checked the po list as well, added a note to future ebuilders to check the included langs, took out a no-longer relevant comment, and kept the fixes from the previous proposal. This patch is meant to be applied =>on the portage ebuild<=, NOT on the previously submitted ebuild. The previously submitted ebuild will fail whenever LINGUAS contains either "it" or "pt_BR". Please test! Cheers, Federico
sorry for taking so long, forgot about that. applied :)
