LibreOffice Manager (lomanager)

[seedsgrow]

I used BleachBit to clear up a little space. I think the only /var files it deleted were temporary files. I still have a cache folder with an apt subfolder in /var. I can still add and delete packages with apt through Synaptic. A file, LO-rpms, is created in /var/temp during the attempt at installation of LibreOffice.

[pinoc]

I used BleachBit to clear up a little space. I think the only /var files it deleted were temporary files. I still have a cache folder with an apt subfolder in /var. I can still add and delete packages with apt through Synaptic. A file, LO-rpms, is created in /var/temp during the attempt at installation of LibreOffice.

lomanager does not touch anything in /var. LO-rpms is not a file but a folder located in /tmp and it will just contain the LO-rpms if the user has decided to keep them upon finalizing the LO-installation. This folder is just a storage directory and has nothing to do with the LO-installation as such. From your error message it is evident that the LO-rpms could not be installed, either because their download was or got interrupted, or your rpm-database is corrupt, or whatever else, all the rest are follow-up errors. If you want you can read through the script (/usr/bin/lomanager) step-by-step and figure out something more.
Alternatively, you can also try to run lomanager on a different machine, were it will just work, yes that's right  , then follow Important Notes 1) and install the LO-rpms on this machine.
hope this helps,
-p.

[Aradalf]

I used BleachBit to clear up a little space. I think the only /var files it deleted were temporary files. I still have a cache folder with an apt subfolder in /var. I can still add and delete packages with apt through Synaptic. A file, LO-rpms, is created in /var/temp during the attempt at installation of LibreOffice.

I believe /var/tmp is a symbolic link to /tmp, so maybe that's why you see Lomanager files in /var/tmp.

[seedsgrow]

Yes, /var/tmp/LOtmp is a directory rather than a file, and, yes, it is a symlink to the folder in /tmp that lomanager creates there to hold the LibreOffice rpms until it is installed.Rather than mess any further with the installation script, I used the tarball downloaded there to extract the LibreOffice rpms and manually installed them by entering the rpm command in Konsole. I then added the menu entries manually through the menu editor. I was able to use the desktop integration rpm for Mandriva that was included in the tarball along with the base packages to add the LibreOffice entries to the menu.

The script did work on my laptop PCLOS system.

[zorlac]

Maybe I missed the quick fix for this buried here somewhere but after lomanager did the deed all my OO icons in the office box on desktop 2 of the full monty are broken now. 
Guess it's a manual fix for each individual one?   

[pinoc]

Maybe I missed the quick fix for this buried here somewhere but after lomanager did the deed all my OO icons in the office box on desktop 2 of the full monty are broken now. 
Guess it's a manual fix for each individual one?   

Hi zorlac,
 the OO-launchers in the top left container on desktop 2 are not broken but simply dead now since there is no OpenOffice anymore in the system. To get the LibreOffice launchers in place please check here
regards,
-p.

[kjpetrie]

Nice job, pinoc!

I've just run it in two computers and the only small improvement I could suggest is that lomanager check for the files in LO-rpms before downloading them, as I had rsynced my desktop to my laptop to avoid downloading them twice, and I had to cancel the download and install manually (easy enough to do - cd into /tmp/LO-rpms/, su to root and use "rpm -ivh `ls`")! It would have been nice if it had been handled by the script, though.

[pinoc]

Nice job, pinoc!

I've just run it in two computers and the only small improvement I could suggest is that lomanager check for the files in LO-rpms before downloading them, as I had rsynced my desktop to my laptop to avoid downloading them twice, and I had to cancel the download and install manually (easy enough to do - cd into /tmp/LO-rpms/, su to root and use "rpm -ivh `ls`")! It would have been nice if it had been handled by the script, though.

Hi kjpetrie,
dang, too late!  Just uploaded 0.2-6 with the change that the intermediate directory into which the rpms are downloaded and from where they are installed is no longer under /tmp/ but in /root/. This to avoid potential space conflicts if /tmp has not been mounted inside the root-system for which the LO-space requirements are checked for.
Your suggestion is good but I still prefer the option that the user will simply follow Important notes 1 which is easy to do. Otherwise, and depending on the user-selected LO-locale, it might get rather complex in the lomanager script to verify the existence, completed download or not, and correct versions of the required rpms to be installed, and more complex -> more error-prone.
best,
-pinoc

[coffeetime]

J-Lo successfully installed. Everything works like a charm!

>pinoc,

and thank You!!

[Was_Just19]

I recently used Lomanager to download and install LibreOffice.
This time I retained the rpms and had a look at what it downloaded.

This raises a couple of questions .......

Living in Europe and speaking English, I have no need of the US rpms that I am aware of, but they are apparently downloaded along with the European rpms. Is this necessary?

I never use LO calc, math or base and rarely presentation. I would not miss their presence if they were not installed. Did I miss a selection screen which determines what main options are installed? If not is it possible to allow a user to make a selection to determine what is to be installed?

So for instance in the situation I described above, I would wish to install Writer & Presentation and whatever associated rpms would be needed but not the others. I am very aware of my download limit on this connection and unnecessary downloads are to be avoided.

For the present it seems it might be best if I completely uninstall LO and then just install the rpms I need.

It would be nice, if it could be arranged, that I would only download those RPMs that I need and not the others.

regards.

[kjpetrie]

Yes, I noticed that too, but I wasn't clear whether the en_US versions are the default which the others just localise, or whether all versions are fully self-contained.

[Was_Just19]

Yes, I noticed that too, but I wasn't clear whether the en_US versions are the default which the others just localise, or whether all versions are fully self-contained.

I am not very clear on any of it either ....  only now started looking at it.
For a test I downloaded the main LO package (RPM) and the EN-GB language pack.
Extracted them into a local repository, and installed using Synaptic from there.
I now have EN-GB and no US modules installed and do not have Math, Calc or Base installed either.
Will see how it goes over a little time.
The installed parts - Write, Impress, Draw and Printer Admin all seem to function as expected, but I have only briefly looked at them so something might rear its ugly head over time.

regards.

[pinoc]

to my understanding, and if you go to their download page, you first have to download the base package, which is en_US, and then you can add whatever localization. I prefer keeping it this way as it simple to handle. asking the user which LO-component he/she wants and for what locale might be too complex for some of them (yes, don't laugh, we had plenty of examples of such users recently), and depending on the chosen combination, something might not work as expected, or the user says "oh, and why don't I have this LO-component?". Right now they get the whole pack and can remove whatever they don't like, that should be fine.
-p.

[Was_Just19]

to my understanding, and if you go to their download page, you first have to download the base package, which is en_US, and then you can add whatever localization. I prefer keeping it this way as it simple to handle. asking the user which LO-component he/she wants and for what locale might be too complex for some of them (yes, don't laugh, we had plenty of examples of such users recently), and depending on the chosen combination, something might not work as expected, or the user says "oh, and why don't I have this LO-component?". Right now they get the whole pack and can remove whatever they don't like, that should be fine.
-p.

Understood 

I will do it manually I think in future as I want control over what I install.

Thanks for your reply.

regards.

[johnmart]

pinoc, thanks for maintaining & developing lomanager.

I get confused what is happening when I run lomanger.
When lomanager is updated I expect that it will install an LO upgrade, but that is not always the case, rt? bugfixes, addlocale changes etc.
But each new LO upgrade requires a new lomanger that corresponds to the new version number?

So my suggestion is that a bit of detail be included with the install dialog box. ie;

LOmanager detects LO version.x & will upgrade to version.xx
or
LOmanager detects LO version--you have the latest version.

I have no idea how difficult it would be to script that. If complex, maybe simply mention in the dialog box:

LOmanager installs version.xx

The user can check the version number in LO or synaptic.
Again, thanks for great app.