Package: src:ipe
Version: 7.1.10-1
Severity: normal

Hi!
ipe holds the dubious honor of being the only package build-depending on
libjpeg8-dev.  This goes against the jpeg8->jpeg62-turbo transition.
I see this has been introduced in SVN commit 47177, without any explanation.
I tried changing this b-dependency to libjpeg-dev -- ipe builds successfully
so it doesn't use any APIs introduced by jpeg8.

Is there a reason to use jpeg8?  The security team opposed having two jpeg
libraries in jessie, I guess the same applies to stretch.

Reply via email to