Bug 82044

Summary: Last Errata overwrote system wide config file
Product: [Retired] Red Hat Linux Reporter: Manfred Hollstein <manfredh>
Component: vimAssignee: Karsten Hopp <karsten>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Manfred Hollstein 2003-01-16 18:33:55 UTC
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):
-6.1-18.8x.1

How reproducible:
Always

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
created.

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 18:46:08 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 18:51:12 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.