Hi, Frank Küster <[EMAIL PROTECTED]> (17/01/2007): > Thomas Huriaux <[EMAIL PROTECTED]> wrote: > > $ debconf-updatepo > > can't open ./../auctex/templates: No such file or directory at > > /usr/share/intltool-debian/intltool-extract line 204. > > /usr/bin/xgettext: error while opening "../auctex/templates.h" for > > reading: No such file or directory > > ERROR: xgettext failed to generate PO template file. Please consult > > error message above if there is any. > > > > > > I suggest you apply the attached patch. > > Or rather not: > > $ fakeroot debian/rules debian/po/templates.pot > eperl -d DEBIAN_DIR="/home/frank/src/Packages/auctex/auctex-11.83/debian/" \ > -I "/home/frank/src/Packages/auctex/auctex-11.83/debian/" -P -o > debian/auctex/templates debian/auctex/templates.in
You're no longer extracting strings from the source file but from a
generated file. I had not seen that yesterday, but I think you are
misusing the POTFILES.in file when you do:
DCSOURCES := $(shell cat debian/po/POTFILES.in \
| perl -pe 's|^\[[^]]+\] +(.*)$$|debian/$${1}|')
The main problem with this bug is that it forces translators to
understand your build system if they want to check their PO files. Of
course, it is not as problematic as I thought before.
The other minor problem is that it gives false-positives in our i18n
infrastructure :-)
(see http://www.debian.org/intl/l10n/po-debconf/errors-by-pkg)
> If there is a problem, it is rather that the file is not updated in any
> of the regular targets (clean, build, or binary). I think the clean
> target is the right thing?
Yes, the clean target is the right one, as it is the only one that
allows you to have an up-to-date source package in a standard build
process.
Cheers,
--
Thomas Huriaux
signature.asc
Description: Digital signature
