Your message dated Mon, 26 Oct 2026 21:05:17 +0000
with message-id <[email protected]>
and subject line Bug#1143491: fixed in dhcpig 2.7.3-1
has caused the Debian Bug report #1143491,
regarding dhcpig: new upstream release 2.7.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1143491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1143491
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dhcpig
Version: 1.6-3
Severity: wishlist
Tags: patch
X-Debbugs-Cc: [email protected]

Hi,

Upstream dhcpig has moved on quite a bit since 1.6, and I put together a
packaging update for it. I don't have a Salsa account, so I'm attaching it
here instead of a merge request -- if someone would rather I open one, just
say and I'll get an account sorted.

The short version: 1.x was a single pig.py script, and 2.x is a full
rewrite into an installable, tested package (src/dhcpig/, hatchling, PEP
517), with a small local web UI (dhcpig-web) alongside the CLI. The old pig
compatibility command got dropped upstream in 2.6.0. Changelog has the
details: https://github.com/kamorin/DHCPig/blob/v2.7.2/CHANGELOG.md

Release: https://github.com/kamorin/DHCPig/releases/tag/v2.7.2
Needs Python 3.11+ and scapy >= 2.5 (still the only runtime dependency).
Console scripts are dhcpig and dhcpig-web -- no more pig. Everything in the
package is GPL.

What I touched in the packaging, roughly:

- control: swapped python3-setuptools for pybuild-plugin-pyproject +
python3-hatchling (it's PEP 517 now), python3-all instead of bare python3,
and added python3-pytest/python3-scapy under <!nocheck> so the build
actually runs the upstream test suite. Dropped pkgconf, that was only
needed for the old setup.py. Runtime dep is python3-scapy (>= 2.5) --
deliberately not libpcap0.8, since that got renamed in the 64-bit time_t
transition and doesn't exist under the old name anymore. Bumped
debhelper-compat to 14 and Standards-Version to 4.7.4 while I was in there.
Also rewrote the long description -- the old one still described a
standalone gratuitous-ARP DoS mode that was retired upstream back in 2.3.
- rules: dropped the pig.py rename (the console scripts install themselves
now) and the setup.py clean guard, since there are no patches left that
need it. Wired PYBUILD_TEST_PYTEST so the unit suite runs at build time --
it's all no-root, sendp is monkeypatched, nothing touches a real socket.
Left tests/integration out, same as upstream does by default (needs
CAP_NET_RAW and a veth pair, no buildd has that).
- copyright: one GPL-2+ stanza, plus a separate one for the bundled
fingerprint data (also GPL-2+, sourced from a different upstream project).
- manpages: dhcpig.1 moved to packaging/dhcpig.1 upstream, and I wrote a
dhcpig-web.1 since upstream doesn't have one yet for the web UI.
- tests: the old test-help.sh grepped --help for a URL that 2.x doesn't
print anymore, so it would just fail as-is. Replaced it with three tests --
command-help, python-import, and packaged-assets (checks that the bundled
web/fingerprint files actually load from where they're installed -- not
marked superficial, since both loaders quietly fall back to empty if the
data's missing rather than erroring). None of them touch the network.
- One patch to fix an invalid freedesktop category in the .desktop file.
Everything from the 1.6 patch set is gone -- upstream folded all of it in
already.

I built and tested this in a clean debian:unstable container rather than
just eyeballing it. Full source+binary build, 387 upstream unit tests run
during the build and pass, and lintian on the .changes comes back with:

  W: dhcpig source: no-nmu-in-changelog
  W: dhcpig source: source-nmu-has-incorrect-version-number 2.7.2-1
  P: dhcpig source: maintainer-manual-page [debian/dhcpig-web.1]

The two warnings are just because I'm not a DM/DD signing this, so they'll
go away on a real upload. The pedantic one is about dhcpig-web.1 living
under debian/ instead of upstream -- happy to send it upstream once the
package itself is in good shape.

Installed the built .deb into a clean container afterward and ran the three
autopkgtests by hand -- all pass. None of them send a DHCP packet or open a
listening socket.

For what it's worth: 130,772 bytes download, 522 KiB installed, Depends:
python3-scapy (>= 2.5), python3:any. pristine-tar also reproduces the exact
tarball uscan pulls from GitHub, byte for byte (sha256
8b5801f6c118e7e7072e3f21c85b0ea5e63e03ab61e105a2975a62305da94659) --
checked that from a completely separate clone, not just my working copy.

Since I don't have Salsa access, the branches live on the upstream GitHub
repo instead, using the same debian/master / upstream/latest / pristine-tar
layout the team already uses on Salsa:

  https://github.com/kamorin/DHCPig/tree/debian/master
  https://github.com/kamorin/DHCPig/tree/upstream/latest
  https://github.com/kamorin/DHCPig/tree/pristine-tar
  https://github.com/kamorin/DHCPig/releases/tag/upstream%2F2.7.2

To grab it:

  git remote add kamorin https://github.com/kamorin/DHCPig.git
  git fetch kamorin debian/master upstream/latest pristine-tar
upstream/2.7.2
  git checkout kamorin/debian/master
  gbp buildpackage --git-builder=sbuild

(upstream's own master branch is untouched by any of this, for what it's
worth -- these are just extra branches alongside it)

If someone on the team has a few minutes to look this over, I'd appreciate
it -- happy to fix up anything that needs changing. Thanks for keeping this
package going.

--- End Message ---
--- Begin Message ---
Source: dhcpig
Source-Version: 2.7.3-1
Done: Kevin Amorin <[email protected]>

We believe that the bug you reported is fixed in the latest version of
dhcpig, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kevin Amorin <[email protected]> (supplier of updated dhcpig package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 22 Aug 2026 12:00:00 +0000
Source: dhcpig
Architecture: source
Version: 2.7.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <[email protected]>
Changed-By: Kevin Amorin <[email protected]>
Closes: 1143491
Changes:
 dhcpig (2.7.3-1) unstable; urgency=medium
 .
   * New upstream release 2.7.3 (Closes: #1143491).
     Upstream 2.x is a full rewrite: the single pig.py script is now a Python
     package with a subcommand CLI and a stdlib-only local web UI.
   * d/control:
     - Build with pybuild-plugin-pyproject and hatchling; upstream dropped
       setup.py in favour of a PEP 517 build.
     - Drop the pkgconf and python3-setuptools build dependencies, neither of
       which the new build system uses.
     - Build-depend on python3-pytest and python3-scapy under <!nocheck> so the
       upstream test suite runs at build time.
     - Rewrite the long description for the 2.x feature set and spell out the
       absence of an authorisation gate.
   * d/rules: build with pybuild and run upstream's pytest suite; drop the
     pig.py-to-dhcpig rename, which upstream's console scripts make redundant.
   * d/watch: drop the Repacksuffix and Dversionmangle. Nothing is excluded
     from the tarball and no +dfsg revision was ever uploaded, so the repack
     was vestigial.
   * d/copyright: give the bundled Satori-derived DHCP fingerprint table its
     own stanza, and refresh the upstream copyright years.
   * d/NEWS: document the incompatible command line. "dhcpig <interface>" is
     no longer accepted; "dhcpig exhaust <interface>" is the equivalent.
   * d/tests: replace the superficial --help test with upstream's suite run
     against the installed package, plus a smoke test covering both entry
     points and the retired 1.x invocation.
   * d/dhcpig-web.1: add a manual page for the new web UI entry point.
   * d/dhcpig-web.desktop: ship a launcher with freedesktop-valid categories;
     upstream's uses the Kali-specific "09-sniffing-spoofing".
   * d/salsa-ci.yml: re-enable the package build jobs now that there is a
     build system to exercise.
   * d/control: recommend pkexec, which the desktop launcher uses to obtain
     the root privileges dhcpig-web needs for raw sockets.
   * d/dhcpig.lintian-overrides: override three deliberate findings, each
     with its reason.
Checksums-Sha1:
 d6901ed17c3c67422b0328fad99a6013efbc622d 2159 dhcpig_2.7.3-1.dsc
 640df0db3bb7e8218124a0caf17b377a0fc4ac6a 244513 dhcpig_2.7.3.orig.tar.gz
 9644555239d0dc7d15d7946631898c2c9d13c49e 6864 dhcpig_2.7.3-1.debian.tar.xz
 960910f4913e2d010203777399fe3fd820bbed73 6961 dhcpig_2.7.3-1_source.buildinfo
Checksums-Sha256:
 db4511f77157a1e5185f364d1e5455566c38d92142e50f1173df129e31a93d49 2159 
dhcpig_2.7.3-1.dsc
 bcb2a1cbf832f5738298205d7c09b216b83c982d87a1677d90f2d443df0c4a69 244513 
dhcpig_2.7.3.orig.tar.gz
 c8dd79db14c811d7ee4f62fcc38cce6049d53a8bb53c90886faa1b08d1887434 6864 
dhcpig_2.7.3-1.debian.tar.xz
 5ef75998daabb33e6f1026d1b163336da59ace089ce7f8e00ca5af3b23f77e7b 6961 
dhcpig_2.7.3-1_source.buildinfo
Files:
 afd41ac2615be7ae7cf919fccd61c603 2159 net optional dhcpig_2.7.3-1.dsc
 e414beda2171a52c1404b1abf5e19bfd 244513 net optional dhcpig_2.7.3.orig.tar.gz
 915ce3520596f674032a410a3b61a4fa 6864 net optional dhcpig_2.7.3-1.debian.tar.xz
 c1097111e5968c4e71ef7ff30f3c65a8 6961 net optional 
dhcpig_2.7.3-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmrfuwIACgkQMfMURUSh
dBpOhBAAl7NUol3nAoNHOVD6y+JEPV6MyvIM+7ZoRmZiIfFkKdI1YnTgOS3/XyIf
NuQUghc0rAB/IJZ/dHoWFiUld2V/dAy9E9r7z/qcANPtdWxipLkxB6IvXa5Osw2Z
7YSLfziBnqyQTCFkeL2XbjSKjuqb8WqMO6+onfa2wi9bOmczym1alGbZ4xbm5gQP
YlG2VmOfTHJ2/6WE18voy42BWUtZtu7EBjmQW/VtozRbdM/f1s33z7OL7eOz5eyo
LiHDYM9LghqmacigRPu6A7bZkcgMAUgjeD++CdwU7eKywPYOWRfnL/ync72vWI9g
ng2a7iOLGglNYHRani7SU+SB9wArmo1Wjy8yKcqTKwpGbDfCXNKw4P9Hh4jcCKl+
PmNjb/va6NecH7u8K4qK0+ZtuuLbNpwKNwHl4yWb+qRvKkORNncqZxGtgTHAqUs4
yDptC5c7jOihlkr4GsPqmenjkagj1Gtnde87gmDwYgdB+39y3YvUuKJQ9cuknJnV
LDutBYEjH1xxvaIRITaHyX1oBRZLAYroVcwf73mquLvG4LJKSYrG/0UfNAf95BLH
zCiyo571A08x+1qfIufJi6wD4ZRd2dD8CIglNrsD5iQ3n8uB+3b7ENOy8gt06OBr
WXaSU5dehkEDeOQpv4TwNXP/cPQeHXCXCVEPFeZfdqRD/JqghUs=
=Bxv3
-----END PGP SIGNATURE-----

Attachment: pgpUfH2il5tJX.pgp
Description: PGP signature


--- End Message ---

Reply via email to