[exact-image] Re: [PATCH 7/8] Disable unused Evas Helper function to avoid FTBFS

On Thursday 05 March 2015 12:58:04 Sven Eckelmann wrote: On Thursday 05 March 2015 12:51:44 René Rebe wrote: http://git.enlightenment.org/core/efl.git/commit/?id=a01418aff884f9d6f3d 68 e4fcee1414e736a7313 Just search for typedef Eo Evas; to find the interesting

[exact-image] Re: [PATCH 7/8] Disable unused Evas Helper function to avoid FTBFS

On Thursday 05 March 2015 12:51:44 René Rebe wrote: http://git.enlightenment.org/core/efl.git/commit/?id=a01418aff884f9d6f3d68 e4fcee1414e736a7313 Just search for typedef Eo Evas; to find the interesting part. How now does the Debian need to be to reproduce this? I

[exact-image] Fwd: Bug#790780: edisplay: possible memory leak

-- Forwarded Message -- Subject: Bug#790780: edisplay: possible memory leak Date: Wednesday 01 July 2015, 16:55:24 From: Ivan Shmakov i...@siamics.net To: 790...@bugs.debian.org Package: edisplay Version: 0.8.9-7+deb8u1 There seem to be a possible memory leak in

[exact-image] Fwd: [Bug 1516548] [NEW] bardecode does not like colons in directory names

From: https://bugs.launchpad.net/ubuntu/+source/exactimage/+bug/1516548 Most relevant looking part of the code is in codecs/Codecs.cc (ImageCodec::getCode): // parse the codec spec, prefixed to the filename, e.g. jpg:, tif:, raw:, ... std::string::size_type idx_colon = filename.find

[exact-image] Re: Bug#790780: edisplay: possible memory leak

On Wednesday 01 July 2015 19:38:00 Sven Eckelmann wrote: On Wednesday 01 July 2015 19:07:15 René Rebe wrote: thanks for the report, I will look into it. I assume this is latest Debian with this quite new Enligthenment 17-something Evas? It is 0.8.9-7+deb8u1 from Debian Jessie. So it is using

[exact-image] CVE-2015-8366: Index overflow in smal_decode_segment

Hi, more information about this CVE can be found at https://security-tracker.debian.org/tracker/CVE-2015-8366 Kind regards, Sven signature.asc Description: This is a digitally signed message part. --- If you wish to unsubscribe

[exact-image] [PATCH] Sort X_SRCS to fix reproducible builds on armhf

--- See https://tests.reproducible-builds.org/history/exactimage.html 0.9.1-13 vs. 0.9.1-14. The diffs can be seen at https://tests.reproducible-builds.org/dbd/testing/armhf/exactimage_0.9.1-12.diffoscope.html build/bottom.make | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[exact-image] Fwd: Bug#811784: exactimage: FTBFS with GCC 6: narrowing conversion

-- Forwarded Message -- Subject: Bug#811784: exactimage: FTBFS with GCC 6: narrowing conversion Date: Tuesday 19 January 2016, 18:00:17 From: Martin Michlmayr To: sub...@bugs.debian.org Package: exactimage Version: 0.9.1-10 Severity: important User:

[exact-image] [PATCH 2/3] Use typecasts instead of [0] to flatten multi-dimensional arrays.

From: Dave Coffin --- codecs/dcraw.h | 44 ++-- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/codecs/dcraw.h b/codecs/dcraw.h index 3190549..45487ce 100644 --- a/codecs/dcraw.h +++ b/codecs/dcraw.h @@ -19,8

[exact-image] [PATCH 1/3] Updated color matrices, support the Canon EOS 5DS.

From: Dave Coffin --- codecs/dcraw.h | 61 -- 1 file changed, 42 insertions(+), 19 deletions(-) diff --git a/codecs/dcraw.h b/codecs/dcraw.h index 2888356..3190549 100644 --- a/codecs/dcraw.h +++

[exact-image] Fwd: Bug#833703: php5-exactimage: encodeImage() and encodeImageFile() segfault

-- Forwarded Message -- Subject: Bug#833703: php5-exactimage: encodeImage() and encodeImageFile() segfault Date: Montag, 8. August 2016, 14:28:36 CEST From: bohwaz To: Debian Bug Tracking System Package: php5-exactimage

[exact-image] Fwd: Bug#833702: php5-exactimage: Duplicate function names between ExactImage and GD

-- Forwarded Message -- Subject: Bug#833702: php5-exactimage: Duplicate function names between ExactImage and GD Date: Montag, 8. August 2016, 14:13:43 CEST From: bohwaz To: Debian Bug Tracking System Package:

[exact-image] [PATCH] Remove obsolete path reorientation code (fixes nonzero fill)

From: John Horigan Bug-Debian: https://bugs.debian.org/522360 Origin: backport, https://sourceforge.net/p/agg/svn/127/ --- codecs/svg.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/codecs/svg.cc b/codecs/svg.cc index 4f54bd3..7c0231c 100644 --- a/codecs/svg.cc +++

[exact-image] Fwd: exactimage: FTBFS in experimental: gfx/X11Helper.hh:33:10: fatal error: Evas_Engine_Software_X11.h: No such file or directory

--- Begin Message --- Source: exactimage Version: 1.0.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: affects -1 + edisplay Hello, exactimage fails to build against EFL 1.20 from experimental: In file included from

Re: [exact-image] SVN repository

On Dienstag, 15. Mai 2018 13:02:30 CEST Dr Rainer Woitok wrote: [...] > the web page at > >https://exactcode.com/opensource/exactimage/ > > mentions an SVN source repository without specifying a URL. How can I > clone from this repository? I cannot find the URL on the page but it was:

[exact-image] Re: Bug#895511: exactimage FTBFS with libevas-dev 1.20.7

On Donnerstag, 12. April 2018 19:21:14 CEST Andreas Metzler wrote: > So I do not expect efl to change back, re-introducing an optional > unfavoured API. This sounded differently in October 2017 [1]. But ok, please close the libevas-dev bug (#878572). We will most likely drop exactimage from

[exact-image] Fwd: Bug#939031: exactimage: Uses GifQuantizeBuffer - stops working with newer giflib

--- Begin Message --- Source: exactimage Version: 1.0.2-4 Severity: important Hello, this package uses GifQuantizeBuffer() from giflib. The symbol has been dropped in giflib 5.2 (libgif-dev/libgif7 5.2.1 is available in experimental) and therefore the package a) stops working when the gif

[exact-image] Re: [PATCH] Fix Python3 syntax compatibility of python example

On Saturday, 31 August 2019 09:55:20 CEST Sven Eckelmann wrote: > This is just the first stepping stone to get Python3 support. The biggest > blocker right now is the support of the binary string interface for > encodeImage and decodeImage. The problem is described at > http://www.swi

[exact-image] [PATCH] Fix Python3 syntax compatibility of python example

--- This is just the first stepping stone to get Python3 support. The biggest blocker right now is the support of the binary string interface for encodeImage and decodeImage. The problem is described at http://www.swig.org/Doc3.0/Python.html#Python_nn77 This move to Python3 is necessary because

[exact-image] Re: Fwd: Bug#939031: exactimage: Uses GifQuantizeBuffer - stops working with newer giflib

> this package uses GifQuantizeBuffer() from giflib. The symbol has been > dropped in giflib 5.2 (libgif-dev/libgif7 5.2.1 is available in > experimental) and therefore the package > a) stops working when the gif library package is upgraded and > b) FTBFS against libgif-dev >= 5.2. I have now

[exact-image] Fwd: Bug#1017510: exactimage FTBFS with openexr 3.1.5

--- Begin Message --- Source: exactimage Version: 1.0.2-8 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/fetch.php?pkg=exactimage=ppc64el=1.0.2-8%2Bb7=1660728909=0 ... codecs/openexr.cc:65:11: error: ‘Int64’ does not name a type; did you mean ‘int64_t’? 65 |