OpenOffice.org test packages (from PPA) do not install properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openoffice.org (Ubuntu) |
Fix Released
|
Undecided
|
Chris Cheney |
Bug Description
Binary package hint: openoffice.org
Added the following PPA to a karmic installation and ran an upgrade:
deb http://
Here are the errors I got:
1)
─┤ Configuring ure ├─
Component registries might be corrupted
You are upgrading from a version which might have corrupted service/component registry files (*.rdb), especially /var/lib/
2)
dpkg reported:
Preparing to replace ure 1.5.1+OOo3.
Unpacking replacement ure ...
Preparing to replace uno-libs3 1.5.1+OOo3.
Unpacking replacement uno-libs3 ...
Preparing to replace openoffice.
javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package openoffice.
is installed.
If it is already installed then try removing ~/.openoffice.
ERROR: Couldn't open registry file://
unopkg failed.
javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package openoffice.
is installed.
If it is already installed then try removing ~/.openoffice.
ERROR: Couldn't open registry file://
Exception details:
(com.sun.
unopkg failed.
Unpacking replacement openoffice.
also
dpkg: openoffice.
python-uno depends on openoffice.org-core (= 1:3.1.1-
openoffice.
also
Setting up openoffice.
javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package openoffice.
is installed.
If it is already installed then try removing ~/.openoffice.
Copying: mailmerge.py
Enabling: mailmerge.py
javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package openoffice.
is installed.
If it is already installed then try removing ~/.openoffice.
unopkg done.
tags: | added: iso-testing |
1) Is a real issue but we are demoting it to a release note for Lucid. If the user experiences this problem this note is referring to they have to purge/reinstall all of OOo and remove ~/.openoffice.org from their user profile. There is no workaround.
2)
a) As far as I can tell this is not really a problem it just looks ugly. It is caused by the directories moving during major version changes (eg 3.1.1 -> 3.2.0) and the ordering of which debian packaging scripts are executed and when.
b) no idea about this issue will have to look into it
c) This isn't really an issue at all, it is just telling the user they should have java installed to have a fully functional OOo. It displays this message each time OOo is run, and in the example it is run twice.
Chris