Thorsten Kukuk schrieb:
On Tue, Feb 25, Ludwig Nussel wrote:
If the config is too complex to fix automatically, what kind of qualification does a human have to have to sort it out manually by staring at rpmnew files? IOW no matter what, having to manually sort out rpmnew files is a clear indication of a deeper problem that needs to be solved at the root. Anything built to deal with rpmnew files is just papering over the problem.
Correct, we need to fix the problem that every typo fix in a configuration file will lead to a *.rpmnew or *.rpmsave file. And this is this whole exercise about: minimize the situations, where RPM has to create a rpmnew or rpmsave file. And not doing the opposite, mess even more around with configuration file automatically so that RPM has to create even more rpmnew and rpmsave files which will even more likely break users systems earlier than later.
So what's the takeaway for libnss_usrfiles2 then? And what's the case that caused security issues you mentioned? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org