[SOLVED] Installing unoconv in CentOS 6.5

gtrawoger · 05-09-2014, 04:29 PM

Currently there is a bug in the Github repo (at least that is how I understand it -> link )

The depency for openoffice can't be found, since in CentOs 6.5 they switched to libreoffice and didn't change that depency in the unoconv package.

Code:

Error: Package: unoconv-0.5-1.el6.rf.noarch (rpmforge)
           Requires: openoffice.org-pyuno >= 2.0

This has been a known bug for 5 months now, and no fix so far. I am posting this here since it is a "hack" so to speak.

What you do is install libreoffice and download the RPM, and force the package to install. It will work (currently working on my machine) but it will also complain in yum:

Code:

Warning: RPMDB altered outside of yum.
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
unoconv-0.5-1.el6.rf.noarch has missing requires of openoffice.org-pyuno >= ('0', '2.0', None)

If you can live with that, here you go. Start with the LibreOffice download:

Code:

 
yum install libreoffice-headless yum-utils

Then you download the RPM with yum-utils:

Code:

 
yumdownloader unoconv

Force the install of the unoconv RPM:

Code:

 
rpm -i --nodeps unoconv<TAB>

Press TAB when you get to <TAB> for it to autocomplete the version you downloaded.

You should now have a working unoconv installation.

Hope this helps.

knudfl · 05-11-2014, 03:37 AM

Not "Github repo" ...
"unoconv-0.5-1.el6.rf.noarch" is a Rpmforge / Repoforge package
http://wiki.centos.org/AdditionalRes...ories/RPMForge
Quote : "" Note: Because this repository is NOT part of CentOS,
you should direct support questions to its maintainers at
the Repoforge Users mailing list.""

The solution could be : Make up a dummy rpm package with the file
`openoffice.org-pyuno´ as a workaround for the dependency.

-

gtrawoger · 05-12-2014, 08:07 AM

You are right. My bad. Not Github, but RF.

And I also agree that a dummy package would be a much more elegant fix, even if it's temporary. I just don't know how to do that!

I only posted what I did, since even after a couple hours of googling I could not find anybody posting a solution to this bug. Everyone was waiting for RF to fix it after they reported the bug, but nothing was done for months.