Bug#989957: pocsuite3/1.7.5-1 [ITP] -- an open-sourced remote vulnerability testing framework.

[Tian Qiao <abcnsxyz@gmail.com>]

Sorry, I made a mistake in my previous reply. 

Since pocsuite3 is written in Python, it works out of the box with Python version 3.x on any platform.
If the user uses it on Linux, the system's "nasm" and "objdump" will be used. 

Besides, "nasm.exe" and "objdump.exe" are provided for the convenience of Windows users.

Lintian’s warning is source-contains-prebuilt-windows-binary, and it suggested that:
Check if upstream also provides source-only tarballs that you can use as the upstream distribution instead.
If not, you may want to ask upstream to provide source-only tarballs.
(https://lintian.debian.org/tags/source-contains-prebuilt-windows-binary)

> On Jun 23, 2021, at 11:47 PM, Tobias Frost <tobi@debian.org> wrote:
>> 
>> 
>>> On Jun 23, 2021, at 8:52 PM, Paul Wise <pabs@debian.org> wrote:
>>> 
>>> How were these files created? It looks like they are generated from the
>>> assembly files in the src/ subdirectory. All generated files should be
>>> built from source at build time, and preferably removed from the
>>> upstream source repository and tarballs, or the Debian tarball.
>>> 
>>> -- 
>>> bye,
>>> pabs
>>> 
>>> https://wiki.debian.org/PaulWise
> 
> Both "nasm" and "objdump" are available in Debian, so you can Recommend: or
> Depends: on them (read up the differences in the Debian Policy and decide whats
> more appropiate). Or do the build at package build-time…
> 
> Well, no. Debian policy is that everything has to be built from its sources.
> (So you need to do that at either build time or runtime.)
> 
> -- 
> tobi

Thanks pabs & tobi for the valuable suggestion.

Best Regards,

— Tian