The OP has never been seen again since the original post. Just sayin’... On Sat, Dec 9, 2017 at 9:39 Menelaos Maglis <mmag...@metacom.gr> wrote:
> Joe <j...@jretrading.com> writes: > > > I think there's a case for asking which way to set it during an expert > > install or during the upgrade that reversed the default setting. > > I think it is policy not to touch locally changed configuration during > upgrades. Usually packages ask what to do and/or provide information > when parameters are deprecated or other important architectural changes > are introduced in the new version. > My expectation with Debian is that if I touch a (systemd) configuration > file it wont be overridden during some upgrade. > > Of course, this will not occur if I have never touched the default > configuration and some setting, /within the package/, changed to a new > default. In this case, I expect some information in the upgrade manual > and to be displayed during package upgrade. > > During upgrade from a sysvinit to a systemd release this was, correctly > in my opinion, not handled by the systemd package; it was after all not > changing any of /its/ default behavior. This should have been > highlighted in the upgrade manual. > > Was the system behavior change found during upgrade tests? > Was there a bug or discussion to highlight this system change in the > upgrade manual? > Were people more package-centric and failed to smooth the overall > transition of the system? > The heated discussions around systemd did not help either. > > >
