On Wed, 13 Sep 2017 08:50:59 -0400 John Vogel <jvogel4@stny.rr.com> wrote:
On Wed, 13 Sep 2017 07:37:24 -0400 John Vogel <jvogel4@stny.rr.com> wrote:
On Tue, 12 Sep 2017 11:19:33 +0200 Xavier <zaz.colmant@free.fr> wrote:
poppler update to 0.59.0 breaks texlive. I guess it's an upstream problem (see log extract in attachment). I had to revert to poppler 0.57.0
Confirmed here as well. A different temporary fix is to remove the '--with-system-poppler' configure option from the texlive Pkgfile. Although I successfully built texlive with bundled poppler, I also opted for downgrading poppler back to 0.57.0. I don't have time right now to deal with poppler breaking any other packages.
I've looked into this a little bit. The actual issue seems to be that both texlive and cups-filters are using internal (unstable) poppler API. There has been some discussion on this on the poppler ML [1] and also mention on the cups-filters bugzilla [2] about poppler consumers not using the unstable internals and instead using one of the frontends.
[1] https://lists.freedesktop.org/archives/poppler/2017-September/012518.html [2] https://bugs.linuxfoundation.org/show_bug.cgi?id=1409
Ok, I've submitted a fix for this on flyspray (FS#1485). If you are in need of the fix before the texlive port gets updated, the patch for the port is included as an attachment on the flyspray task. Or you can manually add the patch to the Pkgfile your self: https://git.archlinux.org/svntogit/packages.git/plain/trunk/texlive-poppler-...