On Thu, Apr 12, 2018 at 10:38:55AM +0200, Sven Eckelmann wrote: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/exactimage.html > > Thanks for bringing this up again. This is a long standing bug in > libevas-dev. > Increasing the severity for the libevas-dev bug now because they have > uploaded > the problematic version to unstable without fixing it.
Hi Sven - (Thought I sent this info along already, but I don't see it in BTS. Very sorry for letting this slip through the cracks.) exactimage uses headers that accidentally exposed internal EFL data structures. Later that caused ABI/API compatability problems. Upstream decided to fix this by no longer shipping the engine headers. According to them, they had been optional functionality. Upstream is unclear on whether or not exactimage can be fixed with EFL 1.20. It sounds like the only external project to have used the engines directly. Their suggestion is to port to ecore-evas. I don't have the knowledge to help here, but Cedric from EFL offered help. Unfortunately, it's not as simple as shipping the headers in Debian. I tried that, but the bits used by exactimage have since moved around, and some of the structures have changed. We'd need to diverge significantly from upstream, and Pkg-E doesn't have the resources or expertise to maintain a distro-specific fork. Ross
Description: PGP signature