Bug#527558: openoffice.org-emailmerge: unopkg failed: ERROR: There is no such extension deployed: org.openoffice.legacy.mailmerge.py
Hi,
Paul Menzel wrote:
> while upgrading to openoffice.org 3.1.0-1 the following error was
> displayed.
>
> Vorbereiten zum Ersetzen von openoffice.org-emailmerge 1:3.0.1-11
> (durch .../openoffice.org-emailmerge_1%3a3.1.0-1_all.deb) ...
>
> […]
> ERROR: There is no such extension deployed: org.openoffice.legacy.mailmerge.py
>
> unopkg failed.
> Removing extension org.openoffice.legacy.mailmerge.py...
> ERROR: There is no such extension deployed: org.openoffice.legacy.mailmerge.py
>
> unopkg failed.
> done.
As said in the other bug you filedi for writer2latex, this is already a
broken condition before the upgrade. org.openoffice.legacy.mailmerge.py should
be registered when openoffice.org-emailmerge is installed.
I think this was a side-effect of (filed by you!)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522022.
Because OOo 3.1 had some restructuring which I needed to change
some stuff in python-uno for...
> Entpacke Ersatz für openoffice.org-emailmerge ...
> […]
And then it correctly installed and registered it: (at least according
to unopkg):
> -- Package-specific info:
> Identifier: org.openoffice.legacy.mailmerge.py
> URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/tAEcp9_/mailmerge.py
> is registered: yes
> Media-Type: application/vnd.sun.star.uno-component;type=Python
> Description:
Grüße/Regards,
René
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' rene@debian.org | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
Reply to: