Hide Forgot
Description of problem: When a package upgrade affects a %config file that has been locally modified, RPM will leave the old custom file and the new distributed file (in an arrangement depending on the noreplace option) for the admin to merge. But a two-way merge requires considerable outside knowledge to choose the correct version at each difference. In addition to changes in the package and changes made by the admin (which she hopefully marks with comments), automated processes including RPM scriptlets may poke at %config files. Ideally, the latter changes might be commented too. But in any event, a three-way merge is easier to do correctly. I propose that when RPM installs a %config file F, it should keep an extra copy of the distributed file for the admin to use later as the common ancestor of a merge. The simplest thing would be to write it to F.rpmbase (or so) in the same directory; scripts that scan extension directories hopefully already skip *.rpm?* . Supposing that I want this functionality, I am guessing that adding to RPM's existing code for handling %config files on install would be the easiest way to get it. Version-Release number of selected component (if applicable): rpm-4.8.1-5.fc14 How reproducible: Almost always Steps to Reproduce: 1. Install a package with a %config file. 2. Upgrade to a new version of the package in which the %config file has changed. Actual results: "diff -u foo foo.rpmnew", head scratching. Expected results: foo.rpmbase is created in step 1, so the files can be merged with "diff3 foo foo.rpmbase foo.rpmnew" or so.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping