[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#792447: RFS: python-afl/0.2.1-1 -- American Fuzzy Lop fuzzy testing for Python code [ITP]



Control: tags -1 moreinfo

Hi Daniel,

I do not remember how we left this one, anyway:

now with the llvm stuff being fixed/rebuilt, I asked for a give back of
afl, and it is actually building almost everywhere
(just arm64 needs investigation, and s390x/kfreebsd-amd64 needs an llvm-toolchain-3.6 rebuild,
ongoing right now)


How do you feel about updating afl, checking if everything is good and then
followup with python-afl?

cheers,

Gianfranco




Il Lunedì 10 Agosto 2015 11:36, Daniel Stender <debian@danielstender.com> ha scritto:
On 10.08.2015 11:04, Gianfranco Costamagna wrote:
> I did a look, and the packaging looks really good (and the upstream maintainer too :) ).
> 
> However prior to sponsor I would like to see afl working, otherwise it would be not installable
> on sid.
> 
> (I'll try to work on llvm side in the next few days)
> 
> Little (I guess not trivial to fix) nitpick: you might avoid pthread link
> dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/python-afl/usr/lib/python2.7/dist-packages/afl.x86_64-linux-gnu.so was not linked against libpthread.so.0 (it uses none of the library's symbols)
> dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/python3-afl/usr/lib/python3/dist-packages/afl.cpython-34m-x86_64-linux-gnu.so was not linked against libpthread.so.0 (it uses none of the library's symbols)
> 
> But I really do not think this is trivial to solve (more a cython problem than a python-afl one IIRC)
> 
> cheers,
> Gianfranco


Very much welcome! :-)

Deal, when you've successfully fuzzed with it we go on with the sponsoring, I'll get into that link issue in the
meanwhile.

Best,

Daniel 

-- 
http://www.danielstender.com/blog/
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8


Reply to: