On Friday 08 April 2005 4:04, Bill Campbell wrote: > On Fri, Apr 08, 2005, Mark Keller wrote: > >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 > > I suspect that this is somewhat out of date as I think I've seen > files with suffixes other than the .rpmorig and .rpmsave cited in > this article. > > My hard copy of Maximum RPM is dated 1997, and I don't think a newer > version is available. >
The date on the site is 2000, but I do believe that the logic is still accurate for a plain %config option of the spec file. Looking at newer docs, there is %config(noreplace) in the %files directive to make a config file never get overwritten. That will cause the .rpmnew. So I think the only way to get the modified config file to stay is to make sure everyone uses %config(noreplace) when creating spec files. Quickly grepping through spec files only amanda, apache and openpkg are using noreplace for configs. Mark Keller Systems Administrator Portland State University ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
