Hello Larry,
/
Openoffice.org-ure/ seems to be the main issue.
The versions provided by sl-base and sl-security (corresponding to
OpenOffice 3.1.1) is named openoffice.org-ure-3.1.1-19.5.el5.x86_64.rpm
(respectively openoffice.org-ure-3.1.1-19.5.el5.i386.rpm, depending on
the architecture of the target systems ).
The corresponding version provided by OpenOffice (3.2.1) is named:
openoffice.org-ure-1.6.1-9502.x86_64.rpm (respectively
openoffice.org-ure-1.6.1-9502.i386.rpm) .
When processing yum update (manually or by cron),
openoffice.org-ure-3.1.1-19.5 will systematically be substituted to
openoffice.org-ure-1.6.1-9502. It will result in an issue (message can
be: opt/openoffice.org3/program/soffice.bin: error while loading shared
libraries: libuno_sal.so.3: cannot open shared object file: No such file
or directory).
The proper way to set up OpenOffice 3.2.1 is therefore to:
* first, remove any OpenOffice version provided by SL (yum remove
openoffice.org*),
* second, install OpenOffice 3.2.1,
* and then block any further update of openoffice.org-ure (insert the
instruction exclude =openoffice.org-ure* in the section [main] of
/etc/yum.conf and/or in /etc/yum.d/yum.cron.excludes).
To fix the issue, first remove openoffice.org-ure and all related
dependencies and then re install OpenOffice 3.2.1.
I hope you'll get through this issue.
Best regards,
Hervé
Le 04.08.2010 15:09, Larry Linder a écrit :
I. Things are not how we would think.
1. ooffice3.2.1 is installed in /opt/openoffice.org3
however, ibuno_sal_so.3 is installed @ /opt/openoffice.org/ure/lib.
Different directories.
This works. Would not expect it.
2. When you "yum erase openoffice.org-base.i386" it complains that it cannot
find ibuno_sal.so.3.
According to "yum erase openoffice.org3" it is looking for the file in
openoffice.org3
3. This may be why the open office script fails. In the bump in the night -
some how the path to the libs get changed! When you
run /opt/openoffice.org3/program/soffice from a terminal window the message
is that it cannot find the ibuno_sal.so.3 lib.
The lib path must be hard coded and not in the directory where the rest of the
program is installed.
II. Excluding openoffice.org-base.i386
The script to exclude it does not work - there has to be something missing.
yum --exclude=openoffice.org-ure*
doesn't work. I am missing something.
Manually edited the /etc/yum/yum.cron.excludes and added the line
exclude=openoffice.org-ure.
Thanks for your help.
Larry Linder
On Wednesday 04 August 2010 03:24, Hervé Riboulot wrote:
Hello,
When using the daily yum update, you can directly exclude any update of
the openoffice.org-ure (providing libuno_sal.so.3 ) by setting up
accordingly the /etc/yum.d/yum.cron.excludes.
Just have a look to the README file. Quote: "If there are certain rpm
packages that you do not want to be updated with the daily yum update.
By default the kernel is already in this file. If you wish to add more
rpm packages, you need to list each one individually, all on the same
line, adding to those that are already there".
The general syntax is: exclude=.
If you intend to manually process the update, the syntax will be:
# yum --exclude=openoffice.org-ure*
Note that yumex proposes a GUI which comprises tools for managing the
'exclude' instruction (the related configuration file is /etc/yumex.conf).
Le 03.08.2010 22:10, Kinzel, David a écrit :
If you use the official install you do not get a working
system because
ibuno_sal.so.3 is not being installed. The script is broken.
Official install being (from OO or SL)? openoffice.org-ure should be
providing libuno_sal.so.3, at least in SL and upstream repos.
Can you manually run yum before the automated script, and see what is
triggering your packages to be removed or upgraded?
rpm -qa 'openoffice*' may be useful for people to see what versions are
interacting here.
This email communication and any files transmitted with it may contain
confidential and or proprietary information and is provided for the
use of the intended recipient only. Any review, retransmission or
dissemination of this information by anyone other than the intended
recipient is prohibited. If you receive this email in error, please
contact the sender and delete this communication and any copies
immediately. Thank you.
http://www.encana.com
