From: Jiri Popelka <jpopelka@redhat.com>
To: Till Kamppeter <till.kamppeter@gmail.com>, sho@bbr.jp
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] pdftopdf
Date: Tue, 29 May 2012 18:06:21 +0200 [thread overview]
Message-ID: <4FC4F3FD.6080605@redhat.com> (raw)
In-Reply-To: <4F54D580.7090608@gmail.com>
Otani-san, Till,
compiling cups-filters 1.0.18 I see
...
checking UGooString.h usability... no
checking UGooString.h presence... no
checking for UGooString.h... no
...
Trying to discover what's this UGooString and why it's not on my system
I found out that it used to be part of poppler but was definitelly
removed [1] in version 0.6.0. pdftopdf still uses it and has it's own
copy which it uses when there's no UGooString found on the system.
It seem's [2] that the last known version (before it was removed) was
quite different than what's been in pdftopdf's UGooString.[h|cxx].
I have no idea which version is newer but it's worth checking whether
the [2] version doesn't fix any bugs.
Anyway, I think that the checking for system wide UGooString.h when
building pdftopdf could be removed because I don't think anybody uses
poppler < 0.6.0. It just confuses people (like me).
[1]
http://cgit.freedesktop.org/poppler/poppler/commit/?id=bf7e0e980bf29994021cb1228f89f582adddf284
[2]
http://cgit.freedesktop.org/poppler/poppler/tree/poppler/UGooString.cc?id=ba74bb3b0632593d1937911d73709fc870480efd
--
Jiri
On 03/05/2012 04:02 PM, Till Kamppeter wrote:
>
> Otani-san, for the time being until we succeed to get the Poppler
> developers to expose the additional APIs for implementing pdftopdf and
> pdftoopvp, can you update the duplictaed code to the newest file
> versions available, so that the known vulnerabilities are fixed? Thanks
> in advance.
next prev parent reply other threads:[~2012-05-29 16:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 11:18 [Printing-architecture] pdftopdf Tim Waugh
2012-03-01 12:36 ` Till Kamppeter
2012-03-01 13:55 ` Tim Waugh
2012-03-02 4:03 ` Koji Otani
2012-03-02 9:39 ` Richard Hughes
2012-03-02 9:58 ` Koji Otani
2012-03-02 11:22 ` Tim Waugh
2012-03-02 12:08 ` Koji Otani
2012-03-02 12:13 ` Tim Waugh
2012-03-03 2:33 ` Koji Otani
2012-03-05 12:14 ` Tim Waugh
2012-03-05 15:02 ` Till Kamppeter
2012-05-29 16:06 ` Jiri Popelka [this message]
2012-05-29 16:50 ` Till Kamppeter
2012-03-05 15:15 ` Till Kamppeter
2012-03-06 6:01 ` Koji Otani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC4F3FD.6080605@redhat.com \
--to=jpopelka@redhat.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=sho@bbr.jp \
--cc=till.kamppeter@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.