#767095 gkrellm: CPU config changed after upgrade to 2.3.6~rc1-1

Package:
gkrellm
Source:
gkrellm
Description:
GNU Krell Monitors
Submitter:
Vincent Lefevre
Date:
2021-01-20 03:21:06 UTC
Severity:
minor
Tags:
#767095#5
Date:
2014-10-28 12:13:58 UTC
From:
To:
The Debian Plicy Manual says:

  Configuration file handling must conform to the following behavior:

    local changes must be preserved during a package upgrade, and [...]

but the CPU config changed after upgrade to gkrellm 2.3.6~rc1-1:
I had chosen to display composite CPU's (because my machine has
8 CPU's), but after the upgrade, all CPU's were displayed (and
the window was partly off-screen). I had to deselect all CPU's
and re-enabled Composite CPU manually.
#767095#10
Date:
2014-11-01 09:14:25 UTC
From:
To:
The Debian Policy Manual is about packaging and how package scripts (pre/post scripts) behave, not about how applications themselves behave on upgrade.

Since gkrellm 2.3.6 changes how configuring CPU krells work it falls back to its internal default value.

If you would extend the Debian Policy Manual to actual application behavior you would basically kick out any big desktop environment. I did not count the number of times I had to reconfigure things in KDE or XFCE on a new minor version but I can assure you there were many of such little hiccups.


Regards,
Stefan
#767095#15
Date:
2014-11-02 01:52:11 UTC
From:
To:
Control: severity -1 minor

OK, though the Debian Policy Manual isn't very clear on this point.
Lowering the severity.

Most software upgrades the config file, taking into account previous
configuration. IMHO, gkrellm should do the same thing. I've just sent
a mail to upstream (Bill Wilson).