balboa (2.1.2+ds-1) unstable; urgency=medium

  The configuration structure has changed significantly in version 2.1.x.
  If you are upgrading from version 2.0.x, please note the following:

  * A new configuration file /etc/balboa/backend.yaml is now required.
    This file specifies the backend(s) to connect to. A default configuration
    pointing to 127.0.0.1:4242 has been installed.

  * The /etc/default/balboa file now requires an additional -b parameter
    pointing to the backend configuration file. If you have customized this
    file, you need to add: -b /etc/balboa/backend.yaml. During upgrades from
    2.0.x, the postinst will warn if the -b flag is missing.

  * If you still have /etc/balboa/database.yaml from older installations,
    please note that it is no longer used. Backend configuration is now
    handled separately via the backend.yaml file and the balboa-backend-*
    packages.

  * The /etc/default/balboa-backend-rocksdb file (previously
    /etc/default/balboa-rocksdb) now uses different default arguments.
    If you have customized this file, review the new defaults.

  * The feeders.yaml default configuration has been slimmed down. If you rely on
    socket-based inputs (gopassivedns or suricata_dns), you may need to
    re-add them to your /etc/balboa/feeders.yaml.

  If you experience issues after upgrading, check the following:
    1. Ensure /etc/balboa/backend.yaml exists and is valid YAML
    2. Ensure /etc/default/balboa includes the -b flag
    3. Restart both the backend and frontend services:
       systemctl restart balboa-backend@rocksdb
       systemctl restart balboa

 -- Sascha Steinbiss <satta@debian.org>  Wed, 09 Jul 2025 21:41:54 +0200