Bug 141030 - /etc/vimrc.rpmnew always created when vim upgraded
Summary: /etc/vimrc.rpmnew always created when vim upgraded
Alias: None
Product: Fedora
Classification: Fedora
Component: vim   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-28 15:49 UTC by W. Michael Petullo
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-06 09:57:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description W. Michael Petullo 2004-11-28 15:49:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7.3)
Gecko/20041027 Epiphany/1.4.4

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):

How reproducible:

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?

Additional info:

Comment 1 Karsten Hopp 2004-11-29 14:34:45 UTC

*** This bug has been marked as a duplicate of 132371 ***

Comment 2 W. Michael Petullo 2005-02-14 17:51:43 UTC
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.

Comment 3 W. Michael Petullo 2005-07-18 18:03:29 UTC
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.

Comment 4 Karsten Hopp 2005-09-06 09:57:22 UTC
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.

Comment 5 Nils Philippsen 2005-10-28 12:41:52 UTC
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 :-)?

Note You need to log in before you can comment on or make changes to this bug.