Bug 82044 - Last Errata overwrote system wide config file
Last Errata overwrote system wide config file
Status: CLOSED DUPLICATE of bug 82037
Product: Red Hat Linux
Classification: Retired
Component: vim (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-01-16 13:33 EST by Manfred Hollstein
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:51:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Manfred Hollstein 2003-01-16 13:33:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021203

Description of problem:
Installing the recently released errata packages for vim, overwrote
the system wide config file /usr/share/vim/vim61/macros/vimrc without
any notice.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Make mods to /usr/share/vim/vim61/macros/vimrc and save them
2.rpm -Uvh vim*-6.1-18.8x.1*.rpm
3.Look for your modifications in /usr/share/vim/vim61/macros/vimrc
  and see how they have been wiped out :-(

Actual Results:  Config file will be silently overwritten, no vimrc.rpmsave is

Expected Results:  The file should have been installed either as
/usr/share/vim/vim61/macros/vimrc.rpmnew, or the existing one should
have been renamed to /usr/share/vim/vim61/macros/vimrc.rpmsave

Additional info:  FWIW, the man page talks about /usr/share/vim/vimrc being
the system wide config file, but strace'ing vim shows that that's not the case;
so, the man page needs update'ing, too.
Comment 1 Karsten Hopp 2003-01-16 13:46:08 EST

*** This bug has been marked as a duplicate of 82037 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:51:12 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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