Re: upgraded config files in /lib/systemd/system
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAli8azMACgkQCp4qnmbT
gcvwagf+PU2QI2/0MPflk2JiN/Y+Y6jwH4KwhceqUQAZQi43zDJnB2C8a1HlJj+/
k/U/qoPNoBExqo2MW3OoaVg6Gr1SYs0fhs6kDge0vE/nZ+C8g+KCaDJNpkxlL8Yl
KgSViwuGCFWEnWJDGRs3zGgIFAD4EPIqlSN4Ap5wOuAZ6OSDakmBRtePZSdIc0G9
ea6mkhc68KhITi8aoe6FlTdjW+nqX2jezsMr0HyZfjZsPXztOpS+EIdhH27afudt
JxE1g9P36dDOHmTM75A1J5xCmJv/LwY00vvMzooaKhvy5vOrpmI5XOmWq51EyjwW
Blt4hqxXVivb8Y4DfEEvXSdwtfgZBQ==
=S+mQ
-----END PGP SIGNATURE-----
Reply to: