[pmg-devel] [PATCH pmg-api/gui] perparations and breaking changes

[Dominik Csapak]

in bookworm, postgres15 has more restrictive permissions, so we have to
adapt to that

in addition, we want to disable some options by default, namely:
advfiler (advances statistic filters)
use_bayes
use_awl (auto-whitelist)

these patches simply change default in the config & frontent, so these
are breaking changes. To deal with that we have (at least) these three
possibilities:
* simply document them in the upgrade guide
  easiest for us, but has *some* potential for issues when users
  don't properly read/follow them and their bayes/awl db get's deleted
* use preinst/postinst script to set the old defaults as explicit values
  in the config. this shouldn't be too hard, but is some baggage
  that we have to keep until the next major version
* introduce a pmg7to8 tool like for pve
  it's the most work, but we could potentiall use this also for
  detecting misconfigurations, add warnings e.g. about templates, not
  running postgres instances (or still running old instances after the
  upgrade), not current packages, etc.

pmg-api:

Dominik Csapak (3):
  dbtools: grant permissions public schema for created databases
  config: disable awl and bayes by default
  config: disable advanced statistic filters by default

 src/PMG/Config.pm  | 6 +++---
 src/PMG/DBTools.pm | 8 ++++++++
 2 files changed, 11 insertions(+), 3 deletions(-)

pmg-gui:

Dominik Csapak (2):
  configuration: options: adapt to new advanced statistic filter default
  spam: options: adapt do new defaults for bayes/awl

 js/SpamDetectorOptions.js | 4 ++--
 js/SystemOptions.js       | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.30.2