bug#27621: Poppler's replacement is ABI-incompatible with the original

2017-07-10 Thread Mark H Weaver
Leo Famulari writes: > On Sun, Jul 09, 2017 at 05:25:07PM -0400, Mark H Weaver wrote: >> They did, however, cherry-pick an upstream patch to fix a null pointer >> dereference bug in 0.52.0. I'll look into adding this patch to our >> poppler. > > Thanks! Let us know how it goes. Pushed to master

bug#27621: Poppler's replacement is ABI-incompatible with the original

2017-07-09 Thread Leo Famulari
On Sun, Jul 09, 2017 at 05:25:07PM -0400, Mark H Weaver wrote: > They did, however, cherry-pick an upstream patch to fix a null pointer > dereference bug in 0.52.0. I'll look into adding this patch to our > poppler. Thanks! Let us know how it goes. > FWIW, Fedora considers CVE-2017-9775 to be of

bug#27621: Poppler's replacement is ABI-incompatible with the original

2017-07-09 Thread Mark H Weaver
Leo Famulari writes: > On Sat, Jul 08, 2017 at 06:04:37PM -0400, Mark H Weaver wrote: >> Here's what we need to do: instead of replacing 0.52.0 with 0.56.0, we >> need to find backported fixes for poppler-0.52.0 (or possibly some newer >> version that has the same ABI as 0.52.0), and apply those

bug#27621: Poppler's replacement is ABI-incompatible with the original

2017-07-08 Thread Leo Famulari
On Sat, Jul 08, 2017 at 06:04:37PM -0400, Mark H Weaver wrote: > Ben Woodcroft writes: > > > Currently Inkscape fails to start as the poppler shared library changes from > > libpoppler.so.66 to libpoppler.so.67 upon grafting. Is this the correct way > > to fix this issue? > The problem originate

bug#27621: Poppler's replacement is ABI-incompatible with the original

2017-07-08 Thread Mark H Weaver
retitle 27621 Poppler's replacement is ABI-incompatible with the original severity 27621 important thanks Ben Woodcroft writes: > Currently Inkscape fails to start as the poppler shared library changes from > libpoppler.so.66 to libpoppler.so.67 upon grafting. Is this the correct way > to fix th