Bug#602453: pd-pmpd: FTBFS - unoconv needs writable $HOME
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
Bug#602453: pd-pmpd: FTBFS - unoconv needs writable $HOME
Vincent Bernat ber...@debian.org writes: listener. Moreover, this is not 100% reliable. I was afraid there might be further complications with unoconv/OO.o, hence my suggestion to split the package (which would, however, require another pass through NEW. :-/) Another possibility might be to use ooo2dbk in conjunction with docbook-utils, dblatex, or the like. Maybe this is is better to keep the documentation in sxw format? Perhaps, though I'd suggest trying to keep the PDF if feasible. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602453: pd-pmpd: FTBFS - unoconv needs writable $HOME
On Fri, Nov 5, 2010 at 12:11, Aaron M. Ucko u...@debian.org wrote: Vincent Bernat ber...@debian.org writes: listener. Moreover, this is not 100% reliable. OK, then we will avoid unoconv. Thanks Vincent. I was afraid there might be further complications with unoconv/OO.o, hence my suggestion to split the package (which would, however, require another pass through NEW. :-/) Another possibility might be to use ooo2dbk in conjunction with docbook-utils, dblatex, or the like. Maybe this is is better to keep the documentation in sxw format? Perhaps, though I'd suggest trying to keep the PDF if feasible. The pdf comes with upstream tarball, we were just regenerating it out of principle. I think we can just install the upstream provided one. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602453: pd-pmpd: FTBFS - unoconv needs writable $HOME
Felipe Sateler fsate...@debian.org writes: The pdf comes with upstream tarball, we were just regenerating it out of principle. I think we can just install the upstream provided one. That's fair; under the circumstances, I won't object to that approach either, even if it isn't quite as pure. The important facts are that you have the source and can produce an equivalent PDF document with free tools. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602453: pd-pmpd: FTBFS - unoconv needs writable $HOME
Package: pd-pmpd Version: 0.9-1 Severity: serious Justification: fails to build from source 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? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602453: pd-pmpd: FTBFS - unoconv needs writable $HOME
On Thu, Nov 4, 2010 at 20:29, Aaron M. Ucko u...@debian.org wrote: Package: pd-pmpd Version: 0.9-1 Severity: serious Justification: fails to build from source 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? -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
