Thorsten Leemhuis wrote:
Hence the question: isn't there a easy way to avoid this somehow
in the
future?
Just stop enabling updates-testing by default. That will fix both your case
(you'll have enabled=1 as a hand-edit and thus RPM will recognize your file
as modified and not overwrite it with a version with enabled=0) and the
common case of a user who just wants to get the new release early and have a
sane upgrade path to the official release (which is a very common and IMHO
totally reasonable expectation). Users who want updates-testing should
always enable it explicitly (like you did).
Kevin Kofler