Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Il 14/10/2010 12:12, Petr Mladek ha scritto:
On Wed, 2010-10-13 at 17:44 +0200, Carlo Strata wrote:
Hi Everyone,

this is my first TDF post! :-)

I'm an active and long time OpenSuSE and Novell's OOo user and bug
poster, too!

Now, in my OpenSuSE daily updated 11.2, x86-64, notebook I have
Novell/OpenSuSE OBS OOo 3.2.1.6 (x86-64) (still with the famous fixed
but not released pdf bug
https://bugzilla.novell.com/show_bug.cgi?id=615812).

More helping hands are always welcome. Feel free to add the fix to the
package, see http://en.opensuse.org/openSUSE:Build_Service_Collaboration

My two questions are:

1. May OOo 3.2.1.x/3.3.x and Libò coexist (in the same operating system
instance, I mean)? At least in linux? May I go on with just downloaded
Libò x86-64 beta2?

LibreOffice is continuation of the OpenOffice.org project. We do not
plan to provide OpenOffice.org-3.3 for openSUSE. Instead of we are going
to provide libreoffice-*-3.3* packages that will replace the older
OpenOffice_org packages during the system update.

Note that we newer provided the plain OOo packages for openSUSE. We
always added the extra patches from the Go-oo project. We are still
going to use these extra changes on top of the LibreOffice code.

If you want more packages in parallel, you might use the universal
LibreOffice Linux packages. They might be installed in parallel with the
universal OOo packages, old openSUSE OpenOffice_org packages and the
upcoming openSUSE libreoffice packages. It is because they are installed
into /opt/libreoffice while the others are installed
below /opt/openoffice*, /usr/lib/ooo3, /usr/lib/libreoffice

I was curious and than I'll install "vanilla Libò" ;-)

But after install on my OpenSuSE 11.2 x86-64, I got this message:
"carlo@carlobook:~> /opt/libreoffice3/program/soffice
/opt/libreoffice3/program/soffice.bin: error while loading shared libraries: libuno_sal.so.3: cannot open shared object file: No such file or directory
"

After googling I understood that this was probably due to the URE package:

libreoffice-ure-1.7.0-1.x86_64.rpm

which most install in
/opt/libreoffice/libreoffice/ure

but all other packages instead install themselves in
/opt/libreoffice3

so I tried fixing the bug with two test:

1. fails:
carlobook:/opt/libreoffice3 # ln -s /opt/libreoffice/libreoffice/ libreoffice

2. successes:
carlobook:/opt/libreoffice3 # ln -s /opt/libreoffice/libreoffice/ure ure

:-) :-) ;-)

My first Libò run! Very fast load!!!

I suggest you fixing the problem!

HTH,

Carlo


2. When does Novell/OpenSuSE start to build Libò in his (our!) OBS?

I have created the LibreOffice:Unstable project in OBS yesterday. I am
running a first test build there. If it goes well, I would publish the
libreoffice-3.3-beta2 packages on Friday or Monday.

It means that the packages might appear at
http://download.opensuse.org/repositories/LibreOffice:/Unstable over the
weekend or in the beginning of the following week.

It's now time for Novell and OpenSuSE whole Community to start giving
solid/concrete Libò/TDF support signs! :-)

Sure. We do out best. There are just too many things to do.

Thank you very much for your great work, ideas and answers! Have a
nice evening

Thanks for support and understanding.

Best Regards,
Petr


PS: Please, keep me in CC if you want fater answer. I have many unread
mails on the mailing list :-(



--
To unsubscribe, e-mail to discuss+help@documentfoundation.org
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/discuss/

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.