Dear René, Am Freitag, den 08.05.2009, 10:13 +0200 schrieb Rene Engelhard: > 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: Great, that everything is fine. Will you close the report or should I? Thanks, Paul
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil