Comment 17 for bug 1109283

Hi Scott,

It is my understanding that if a user does something *unsupported*, say manually edit a file of an X python module to say hack their fixes in order for it to work the way they want it (which can break a system), then an SRU (or any new package version) will upgrade that file not caring if there has been any changes made.

So this is the same thing that is currently happening with MAAS in precise. In order for this work they have to do some manual configuration that is not standard. Since DNS/DHCP is being managed by cobbler, every time cobbler re-generates the configuration required file, it will automatically overwrite this file, regardless of the changes that the user has made. So in other words, cobbler overwrites /etc/dnsmasq.conf because it manages it. If a user wrote its own particular/additional configuration for dnsmasq, it will be lost once the file is renegerated by cobbler. This also happens when cobbler is upgraded to a newer version. So in reality, cobbler is currently and actually doing what we are arguing here. So this SRU does fix this, because newer MAAS won't affect user configured files for DNS/DHCP, as it has its own.

Hope this helps.