Re: Errors in website build logs for the release notes
On Fri, Apr 06, 2007 at 08:24:37PM +0200, Frans Pop wrote:
> In the log for the official builds [1] I see errors like the ones marked
> below:
> make -C pt
> make[2]: Entering directory `/org/www.debian.org/release-notes/etch/pt'
> rm -f ../dynamic.ent
> ln -s dynamic_alpha.ent ../dynamic.ent
> po4a-translate -k 0 -f sgml -m ../en/release-notes.en.sgml \
> -p release-notes.pt.po -l release-notes.pt.sgml \
> -o ignore-inclusion="dynamicdata shareddata"
> !! po4a::sgml: Unknown option: ignore-inclusion
> make[2]: [release-notes.pt.sgml] Error 9 (ignored)
> !! iconv: illegal input sequence at position 356
>
> I don't see those same errors for my local builds.
>
> The po4a error I could understand as an outdated version and probably
> means that the sgml file does not get regenerated.
Right.
> This could also explain the iconv error as because of that it will be
> trying to convert a file that is already in legacy encoding (the file
> that was committed) from UTF-8 to legacy encoding .
Yes, that's the right explanation.
On systems with a new po4a happens the following:
* po4a-translate updates release-notes.pt.sgml in the encoding of the
PO-file (UTF-8)
* Since debiandoc-sgml expects latin1 iconv is started to convert from
UTF-8 to latin1
On the build host with outdated po4a:
* po4a-translate fails to update release-notes.pt.sgml and doesn't
touch this file. Instead the committed version (probably encoded in latin1
as it results from the step above is used)
* iconv is called bogusly again (no need for conversion) and the error
is ignored.
> Any ideas how to clean this up? IMO it's a bit messy.
We could commit SGML files in the PO file encoding. But this requires
care.
The proper solution is to wait for the upgrade to Etch. It was also once
suggested to install a local build of po4a and access it by setting PATH
(and a Perl specific path?) in the Makefile.
Jens
Reply to: