ferm (2.7-8) unstable; urgency=medium

  In this version, ferm's unconditional usage of the iptables xtables/-legacy
  tools has been changed. ferm will now by default use whatever version of the
  iptables tools have been selected with Debian's alterantives mechanism, which
  defaults to the nftables version of the tools.

  ferm offers possibilities to select the tool version of your chosing. See
  the documentation for more details.

  See README.Debian for more information about this.

 -- Marc Haber <mh+debian-packages@zugschlus.de>  Sat, 18 Jul 2026 13:47:58 +0200

ferm (2.7-7) unstable; urgency=medium

  The issues mentioned in the NEWS entry for 2.7-4 have been resolved.

  Ferm now uses a two-stages initialization. It is documented in
  README.Debian.

 -- Marc Haber <mh+debian-packages@zugschlus.de>  Fri, 03 Jul 2026 09:44:39 +0200

ferm (2.7-4) unstable; urgency=medium

  Since Debian 13, ferm has migrated to initialize itself using systemd,
  with a ferm.service unit. This might have unwanted results for you if
  your ruleset needs a functional network, for example to resolve hostnames,
  to build.

  See README.Debian and #863802 for more information about the ongoing
  discussion and plans.

 -- Marc Haber <mh+debian-packages@zugschlus.de>  Mon, 25 May 2026 21:45:07 +0200

ferm (2.7-8) experimental; urgency=medium

  In this experimental version, ferm's unconditional usage of the iptables
  xtables/-legacy tools has been changed. ferm will now by default use
  whatever version of the iptables tools have been selected with Debian's
  alterantives mechanism, which defaults to the nftables version of the tools.

  See README.Debian for more information about this.

 -- Marc Haber <mh+debian-packages@zugschlus.de>  Sat, 18 Jul 2026 13:47:58 +0200
