OoO En cette nuit striée d'éclairs du vendredi 05 novembre 2010, vers 02:32, Felipe Sateler <fsate...@debian.org> disait :
>> pd-pmpd fires up unoconv to convert its manual from Star Office's >> native format to PDF, but unoconv evidently needs a writable $HOME for >> whatever reason: >> >> | unoconv -f pdf >> /build/buildd-pd-pmpd_0.9-1-i386-D5fhxp/pd-pmpd-0.9/manual/pmpd.sxw >> | stat: cannot read file system information for `/home/buildd': No such file >> or directory >> | [Java framework] Error in function createSettingsDocument (elements.cxx). >> | javaldx failed! >> | Error: Unable to connect or start own listener. Aborting. >> | make[1]: *** [override_dh_auto_build] Error 251 >> >> To address this, you could either create and use a temporary $HOME or >> split the docs and examples out into architecture-independent packages >> (or perhaps a single such). >> >> Could you please do so? > Hmm, this seemed to work on at least ia64 and the uploading host > (built in a pbuilder chroot). And now I get failures on DISPLAY not > being set on a pbuilder chroot. > Vincent, do you know which environment variables need to be set > correctly to use unoconv? unoconv does not require anything by itself (neither DISPLAY nor writable HOME). However, OO.org UNO binding can be pretty difficult to make work without a desktop environment. Even with OpenOffice.org headless version, you will need a X server like xvfb to start OO.org listener. Moreover, this is not 100% reliable. Maybe this is is better to keep the documentation in sxw format? -- NO ONE WANTS TO HEAR FROM MY ARMPITS NO ONE WANTS TO HEAR FROM MY ARMPITS NO ONE WANTS TO HEAR FROM MY ARMPITS -+- Bart Simpson on chalkboard in episode 3F01
pgpWjrdUJfjYw.pgp
Description: PGP signature
