Bug#754260: RFS: terminology/0.6.0-1 [ITP]
On Thu, Jul 31, 2014 at 1:16 PM, Nicolas Dandrimont wrote:
> * Anthony F McInerney <afm404@gmail.com> [2014-07-30 23:46:03 +0100]:
>> The eet file source issues, i ran a 'find' and couldn't see the files your
>> talking about, could you name one or two explicitly for me?
>
> The two files I was talking about are:
> ./src/bin/app_server_eet.c
> ./src/bin/app_server_eet.h
I can't find the source for these files in the upstream git repository
either. The source should look something like the two files below.
Please ask upstream what happened. It might be that they generated the
files and then deleted the source and now tweak the .c files instead
of the .geneet files. Or it could be that they rewrote these files
from scratch, there are versions without _eet in their name. The best
way to find out is to ask upstream.
https://git.enlightenment.org/apps/terminology.git/tree/src/bin/
https://git.enlightenment.org/tools/geneet.git/tree/history.geneet
https://git.enlightenment.org/tools/geneet.git/tree/phonebook.geneet
Also, looks like the tool used to create these files isn't in Debian yet.
https://git.enlightenment.org/tools/geneet.git/tree/
Also, src/bin/lz4 looks like an embedded code copy. Please ensure that
the package uses the system version of the lz4 library and that
src/bin/lz4 is removed in debian/rules build before ./configure is
run, so that the code copy is never used. For bonus points, convince
upstream to remove this directory from their VCS and tarballs. Please
note that lz4 recently had some security issues, so terminology might
be affected by them, depending on on how it uses lz4.
https://wiki.debian.org/EmbeddedCodeCopies
https://security-tracker.debian.org/tracker/source-package/lz4
--
bye,
pabs
https://wiki.debian.org/PaulWise
Reply to: