I have to agree that openpkg rpm upgrades often cause problems with config files. I hate it when my modified configs get moved to .rpmsave when I know that they would work perfectly fine with the new package. This does cause potential downtime for services that get restarted with a vanilla config that doesn't do what people using the service expect.
Talking about it with David offline I think we see what the problem might be. Take a look at the Maximum RPM book description of "rpm -U â What Does it Do?": http://www.rpm.org/max-rpm/ch-rpm-upgrade.html#S1-RPM-UPGRADE-WHAT-IT-DOES The problem we seem to be encountering is the following scenario from that chapter: Original file = X, Current file = Y, New file = Z They state that if the current config file is different from the original and the new file is different from both then the new file gets installed. That seems to be what happens a lot with openpkg rpms. What we are used to having happen on rpm for Suse and Redhat is the following: Original file = X, Current file = Y, New file = X This keeps our modified config file because RPM is able to tell that the original and new config were the same so the current config file, so you really want the current file. So why do we see the first scenario happen more often in openpkg. Just throwing David's and my theory out that may cause a flame war. We think that the openpkg config files are changing more often than say Redhat or Suse. Even if the config files are compatible between versions. It seems that at least those two groups do a really good job of not changing config files between minor and compatible revs. So we don't have to worry as much about our config file getting clobbered. I don't think that is happening in the openpkg rpm world. What can be done about it, well I don't have the perfect end solution, but maybe a tighter control of modifications to config files between openpkg revisions. Mark Keller Systems Administrator Portland State University ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
