Re: upgraded config files in /lib/systemd/system
- Date: Sun, 5 Mar 2017 20:47:13 +0100
- From: Harald Dunkel <harri@xxxxxxxxx>
- Subject: Re: upgraded config files in /lib/systemd/system
-----BEGIN PGP SIGNED MESSAGE-----
On 02/28/17 15:23, Dominique Dumont wrote:
> I don't understand why a change in /lib/systemd/system should trigger a conflict warning.
A unit file provided by the package maintainer might introduce new
dependencies, for example. Maybe an ExecStart or ExecStop script has
been changed, or there are new/different command line options.
I don't think that conflicts between the user's old modified unit
files in /etc and the new packages unit files are easy to avoid.
> Either you have changed a value not modified by end user and there's no conflict
> Or you change a value overridden by user, then your change is not taken into account by systemd: conflict is solved by giving priority to user value.
Sorry to say, but this doesn't solve anything. It just hides the
conflict. I understand that this hasn't been taken into account,
but it should be considered for Buster.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----