Created attachment 58097 [details] [review] add missing POTFILES entries uim unable to build with intltool 0.50.x. reported by Felix Geyer <debfx-pkg@fobos.de>. uim: FTBFS: missing POTFILES http://bugs.debian.org/662795 i made fix patch and attached it. - added into po/POTFILES.in scm/annotation-filter.scm scm/annotation.scm scm/generic-predict.scm scm/ng-action.scm - added into po/POTFILES.skip test/test-custom.scm would you please check this? Regards, dai -- > INTLTOOL_EXTRACT=/usr/bin/intltool-extract srcdir=. /usr/bin/intltool-update --gettext-package > uim --pot > rm -f missing notexist > srcdir=. /usr/bin/intltool-update -m > The following files contain translations and are currently not in use. Please > consider adding these to the POTFILES.in file, located in the po/ directory. > > scm/annotation-filter.scm > scm/annotation.scm > scm/generic-predict.scm > scm/ng-action.scm > test/test-custom.scm > > If some of these files are left out on purpose then please add them to > POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list > of left out files has been written in the current directory. > Please report to uim-en@googlegroups.com > if [ -r missing -o -r notexist ]; then \ > exit 1; \ > fi > make[2]: *** [check] Error 1 > make[2]: Leaving directory `/tmp/buildd/uim-1.7.3/po' > make[1]: *** [check-recursive] Error 1 > make[1]: Leaving directory `/tmp/buildd/uim-1.7.3' > dh_auto_test: make -j1 check returned exit code 2
Committed to the master (d9711fcbe700) and the 1.7 (1bb9041dd106) branch. Thanks.
Created attachment 58636 [details] [review] add missing POTFILES entries (2) please re-update POTFILES entries. scm/baidu-olime-jp-custom.scm scm/baidu-olime-jp-key-custom.scm are missing. -- Regards, dai
Your patch was applied to the master and the 1.8 branch, thanks. http://code.google.com/p/uim/source/detail?r=6437b95be6a1e46ecc2cee7079dea7c2e1395a2f http://code.google.com/p/uim/source/detail?r=c73adeedda6ac170958d9d9859829567a0ac4271
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.