For the record, the bug I described below (with failing double registration) is in fact http://bugs.debian.org/468202 which is already fixed.
If you have the problem, use the work around described below to fix your package and you'll be fine for the future. Rene told me that this bug is specifically about the "ERROR: JNI exception occured" that Daniel and Eduard have had. Thus I reverted the severity and tags changes, and retitle it properly. Cheers, On Mon, 03 Mar 2008, Raphael Hertzog wrote: > tag 466300 + confirmed > tag 466300 - moreinfo > severity 466300 serious > thanks > > On Sun, 02 Mar 2008, Krzysztof Burghardt wrote: > > 2008/2/29, Raphael Hertzog <[EMAIL PROTECTED]>: > > > But stracing the whole stuff lead me to discover the file > > > /var/spool/openoffice/uno_packages/cache/log.txt which contains > > > an error message: > > [...] > > > Can other people (in CC) check if they have similar error messages in > > > their > > > logs? > > > > ###### Progress log entry 2008-02-27 19:36:06 ###### > > Copying: writer2latex.uno.pkg > > ERROR: (com.sun.star.ucb.CommandFailedException) { { Message = "Error > > while adding: org.openoffice.legacy.writer2latex.uno.pkg", Context = > > (com.sun.star.uno.XInterface) @6a6da0 }, Reason = (any) { > > (com.sun.star.deployment.VersionException) { { Message = "Extension > > has already been added: org.openoffice.legacy.writer2latex.uno.pkg", > > Context = (com.sun.star.uno.XInterface) @6a6da0 }, New = > > (com.sun.star.deployment.XPackage) @707e80, Deployed = > > (com.sun.star.deployment.XPackage) @7152d0 } } } > > Same problem apparently. Manual fix is: > - stop any running openoffice > - run the following commands > $ sudo /usr/lib/openoffice/program/unopkg remove --shared > org.openoffice.legacy.writer2latex.uno.pkg > $ sudo dpkg --configure openoffice.org-writer2latex > > Alternatively, the extension registration can be done with "--force" so > that it will happily overwrite any already installed extension. > > See "/usr/lib/openoffice/program/unopkg --help". Another alternative is to > use the --list option and check if the extension is registered before > trying to register it. > > Right now, any upgrade will fail as it will try to re-register the > extension which is already registered. Given that postinst ought to be > idempotent, this is a serious problem. > > Cheers, > -- > Raphaël Hertzog > > Le best-seller français mis à jour pour Debian Etch : > http://www.ouaza.com/livre/admin-debian/ > > > -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/