-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I found a thread here about this problem, but no answer or resolution as to whether it's a bug, or even something that can be fixed.
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=12114&forum=38
I'm trying to get PDF support under DocMGR to work correctly and it's complaining about pdftoppm being missing.
A bit of Googling and I found where pdftoppm is supposed to be included with poppler-utils package.
I check on my FC 7 system which is running poppler-utils poppler-utils-0.5.4-7.fc7, and pdftoppm is physically there and located in /usr/bin.
I'm running CentOS 5 with poppler-utils-0.5.4-4.3.el5_1.
Is this a bug? Or is this resolvable?
Thanks, Max
Max Hetrick wrote:
A bit of Googling and I found where pdftoppm is supposed to be included with poppler-utils package.
I check on my FC 7 system which is running poppler-utils poppler-utils-0.5.4-7.fc7, and pdftoppm is physically there and located in /usr/bin.
I'm running CentOS 5 with poppler-utils-0.5.4-4.3.el5_1.
Is this a bug? Or is this resolvable?
Looks like a bug - probably happened when poppler-utils and xpdf still were installable side by side (and both provided pdftoppm). Though I found no bug report upstream regarding that issue - is noone missing pdftoppm?
Cheers,
Ralph
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ralph Angenendt wrote:
Looks like a bug - probably happened when poppler-utils and xpdf still were installable side by side (and both provided pdftoppm). Though I found no bug report upstream regarding that issue - is noone missing pdftoppm?
Thanks, Ralph.
Is there anything that you'd like me to do so that a bug report could be filed?
Regards, Max
Max Hetrick wrote:
Ralph Angenendt wrote:
Looks like a bug - probably happened when poppler-utils and xpdf still were installable side by side (and both provided pdftoppm). Though I found no bug report upstream regarding that issue - is noone missing pdftoppm?
Thanks, Ralph.
Is there anything that you'd like me to do so that a bug report could be filed?
Hmmm. I just rebuilt from the tar.gz which is in Upstream's SRPM - this doesn't build pdftoppm, although the Source is there.
Okay. The spec file does a:
%configure --enable-cairo-output --disable-splash-output
ChangeLog says:
2006-02-23 Albert Astals Cid aacid@kde.org
* utils/Makefile.am: Do not build pdftoppm when SplashOutputDev * is disabled as that does not work
rpm -q --changelog poppler says:
* Mon Sep 05 2005 Kristian Høgsberg krh@redhat.com - 0.4.2-1 - Update to 0.4.2 and disable splash backend so we don't build it.
I think that explains it. Up to you if you want to file a bug report. But that sounds more like an RFE to me.
Cheers,
Ralph
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ralph Angenendt wrote:
Hmmm. I just rebuilt from the tar.gz which is in Upstream's SRPM - this doesn't build pdftoppm, although the Source is there.
Okay. The spec file does a:
%configure --enable-cairo-output --disable-splash-output
ChangeLog says:
2006-02-23 Albert Astals Cid aacid@kde.org
* utils/Makefile.am: Do not build pdftoppm when SplashOutputDev * is disabled as that does not workrpm -q --changelog poppler says:
- Mon Sep 05 2005 Kristian Høgsberg krh@redhat.com - 0.4.2-1
- Update to 0.4.2 and disable splash backend so we don't build it.
I think that explains it. Up to you if you want to file a bug report. But that sounds more like an RFE to me.
Thanks for checking into this, Ralph. I checked on my FC7 instance and the changelog line is there as well, so I'm assuming - --disable-splash-output is not part of poppler-0.5.4-7.fc7 package, which explains why pdftoppm is present on the FC7 instance.
Thanks again! Max
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ralph Angenendt wrote:
I think that explains it. Up to you if you want to file a bug report. But that sounds more like an RFE to me.
FWIW, I downloaded the precompiled binaries for xpdf here:
ftp://ftp.foolabs.com/pub/xpdf/xpdf-3.02pl2-linux.tar.gz
I extracted pdftoppm out of here and placed it in /usr/bin with the the other tools and it seems to be working fine. I don't know what else I might break by doing this, but it seemed to satisfy my DocMGR errors and enabled PDF support again with it.
I'm guessing this isn't acceptable long term, but seemed to do the trick for me to get me rolling again. I wanted to pass it along.
Thanks guys,
Max
On Thu, 7 Feb 2008, Ralph Angenendt wrote:
I check on my FC 7 system which is running poppler-utils
Looks like a bug - probably happened when poppler-utils and xpdf still were installable side by side (and both provided pdftoppm). Though I found no bug report upstream regarding that issue - is noone missing pdftoppm?
very curous, Ralph. I recall filing such upstream a couple of months ago and forgot about it as I built around it. I cannot put my fingers on it atm, however.
A variant has been (mis) reported before, though:
https://bugzilla.redhat.com/show_bug.cgi?id=211724
and closed pointing to an alternative conversion routine.
I see this fustercluck from packaging moves as well:
https://bugzilla.redhat.com/show_bug.cgi?id=219936 https://bugzilla.redhat.com/show_bug.cgi?id=219032 https://bugzilla.redhat.com/show_bug.cgi?id=219828 https://bugzilla.redhat.com/show_bug.cgi?id=219033
'spot' requests a clean filing of the issue against 'poppler' but I cannot find that this happened.
-- Russ herrold
R P Herrold wrote:
very curous, Ralph. I recall filing such upstream a couple of months ago and forgot about it as I built around it. I cannot put my fingers on it atm, however.
A variant has been (mis) reported before, though:
Yes, I found that too (with a reference to throwing out xpdf from EL4 and going the poppler route).
But nothing for EL5.
Cheers,
Ralph
-
Max Hetrick -
R P Herrold -
Ralph Angenendt