Red Hat Bugzilla – Bug 141030
/etc/vimrc.rpmnew always created when vim upgraded
Last modified: 2007-11-30 17:10:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7.3)
Description of problem:
I am following the Fedora Raw Hide tree. Everytime I upgrade vim, the
package creates a /etc/vimrc.rpmnew. The contents of /etc/vimrc and
/etc/vimrc.rpmnew are always the same.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Upgrade to a newer vimrc package. Notice that /etc/vimrc.rpmnew is
created. Also notice that "diff /etc/vimrc /etc/vimrc.rpmnew" prints
nothing. Why is /etc/vimrc.rpmnew created?
*** This bug has been marked as a duplicate of 132371 ***
I just upgraded to 6.3.061-2 and got the "warning: /etc/vimrc created as
/etc/vimrc.rpmnew" message again. /etc/vimrc and /etc/vimrc.rpmnew are
identical. I could not reopen #132371 because I did not initially open that one.
I just saw "warning: /etc/vimrc created as
/etc/vimrc.rpmnew" when upgrading to 6.3.080-1. The contents of
/etc/vimrc.rpmnew and /etc/vimrc are identical.
That's due to a limitation in rpm. If you have the same config file in two
subpackages which don't require each other, you'll end up with a rpmnew file.
There's only one solution which I'd like to avoid: move the vimrc into its own
subpackage and require that by vim-minimal and vim-common.
It's arguable what's uglier, getting vimrc.rpmnew or having a "vim-vimrc"
("vim-config", ...) subpackage. I deem the latter the lesser of two evils,
especially in the light of that this is actually one the primary purposes of
subpackages (to avoid packaging common files into multiple packages). Maybe for
FC5 (pretty please :-)?