[Pkg-netmeasure-discuss] Bug#889938: separate scapy from scapy3k

[Daniel Kahn Gillmor]

Package: src:scapy3k
Version: 0.23-1
Severity: normal
Control: clone -1 -2
Control: affects -1 + src:scapy
Control: reassign -2 src:scapy
Control: affects -2 + src:scapy3k

in debian, we have python-scapy and python3-scapy packages from
different upstream sources:

python-scapy comes from https://github.com/secdev/scapy/

python3-scapy comes from https://github.com/phaethon/scapy/

it appears that the phaethon source is a fork of the secdev source.
the phaethon module is now being renamed to scapy3k.

the secdev source (the original "upstream") appears to support python3
on its master branch (at least as of version v2.4.0rc4).

I think in debian in the future, python-scapy and python3-scapy should
both be derived from the secdev sources.

The phaethon sources should be shipped as python3-scapy3k.

Regards,

        --dkg

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-scapy depends on:
ii  libjs-sphinxdoc  1.6.6-2
ii  python3          3.6.4-1
ii  python3.6        3.6.4-3
ii  tcpdump          4.9.2-2

python3-scapy recommends no packages.

Versions of packages python3-scapy suggests:
ii  ipython3            5.5.0-1
ii  python3-matplotlib  2.1.1-2

-- no debconf information