On Mon, Nov 24, 2014 at 07:38:34AM -0600, John Hasler wrote: > It isn't just ideal. It's Debian policy to respect configuration > changes on upgrade.
That isn't the case, I'm afraid. At least if you are referring to [1], this section refers specifically to *configuration files*, in the context of a single package, rather than a wider notion of system-wide configuration. I personally think a higher-level system-wide preservation would be a worthy goal, but it isn't mandated by policy. The problem in this case is most likely a mixture of some packages not performing the same duties after upgrade, combined with possible changes of dependencies resulting in different pieces of software taking on the job of managing suspend/lid events. It's not a policy violation for a later-version of a piece of software to perform fewer duties than an earlier one; it's also not a policy violation for a package to not honour the configuration of an unrelated one. [1] https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files -- Jonathan Dowland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141124142854.gb29...@chew.redmars.org
