Bug#545482: openoffice.org-common: unopkg should set PYTHONPATH

[Rene Engelhard <rene@debian.org>]

severity 545482 normal
tag 545482 + pending
thanks

On Mon, Sep 07, 2009 at 03:26:25PM +0200, Frederic Peters wrote:
> Installing a Python extension with 'unopkg add' fails with:
> 
>   ERROR: python-loader:<type 'exceptions.ImportError'>: No module named
>   pythonloader, traceback follows
>   no traceback available
>   Exception details: 
>   (com.sun.star.uno.RuntimeException) { { Message = "python-loader:<type
>   'exceptions.ImportError'>: No module named pythonloader, traceback
>   follows\X000ano traceback available", Context = (com.sun.star.uno.XInterface)
>   @0 } }
> 
>   unopkg failed.
> 
> Looking at the Debian ChangeLog I believe this to be similar to
>     * debian/shell-lib.sh: export PYTHONPATH="/@OOBASISDIR/program" as
>       regstering mailmerge.py aparently calls "import pythonloader" which
>       does not work anymore without (closes: #522536)
> 
> and would suggest to also export PYTHONPATH= in unopkg (which is a shell
> wrapper, so probably not difficult).

Indeed. (And btw, I do think this is more than minor, python extensions
are not that uncommon, and unopkg should work even when many people
will just use OOos UI for it...)

Grüße/Regards,

Rene
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  rene@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70