Bug 587130 - Update falsely reports "warning: /etc/shadow created as /etc/shadow-rpmnew"
Update falsely reports "warning: /etc/shadow created as /etc/shadow-rpmnew"
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: setup (Show other bugs)
13
All Linux
low Severity medium
: ---
: ---
Assigned To: Ondrej Vasik
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-28 22:02 EDT by Jerry Amundson
Modified: 2010-04-29 04:25 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-04-29 04:25:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jerry Amundson 2010-04-28 22:02:57 EDT
Description of problem:
Update falsely reports "warning: /etc/shadow created as /etc/shadow-rpmnew" 

Version-Release number of selected component (if applicable):
Fedora 13 Beta version

How reproducible:
always

Steps to Reproduce:
1.install fc13
2.yum update
3.
  
Actual results:
Update falsely reports "warning: /etc/shadow created as /etc/shadow-rpmnew" 

Expected results:
Truthful report.

Additional info:
Comment 1 Ondrej Vasik 2010-04-29 04:25:18 EDT
Thanks for report... 

However - that's no-win thing. .rpmnew files from several potentially dangerous files are removed in %post lua scriptlet - as one user complained that his admin used those .rpmnew files to replace original (as he usually does when he doesn't know about any change in that particular config file done by him manually) - which caused loss of the user accounts. Request for some nowarn flag for config files was done in rpm.org page (see http://rpm.org/ticket/6 ), so far no action there (except it was accepted by rpm maintainers). 

Closing that bugzilla WONTFIX as I don't have any chance to resolve the issue properly. Once it will be resolved in rpm, I'll do the change in setup package.

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