Bug 235627 - up2date clobbers modified files
up2date clobbers modified files
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Bret McMillan
Brandon Perkins
Depends On:
  Show dependency treegraph
Reported: 2007-04-08 11:19 EDT by monty
Modified: 2007-11-16 20:14 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-22 11:02:45 EDT
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 monty 2007-04-08 11:19:35 EDT
Description of problem:
When up2date installed the recent update to mysql (RHSA-2007:0152-01) it replaced the file /etc/
init.d/mysqld even though the file had been modified before running up2date. This change to the file 
broke the MySQL installation on the server.

up2date did not create a backup of the file before it was replaced.
up2date did not send any notification.
up2date did not log the change.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Red Hat Bugzilla 2007-04-11 22:20:09 EDT
User bnackash@redhat.com's account has been closed
Comment 2 Todd Sanders 2007-05-22 11:02:45 EDT
This is not a bug with up2date.  rpm -Uhv would exhibit the same behavior.  Only
config files are persisted through an rpm upgrade. Please log this error against
mysql, if you feel that packaging needs modification.

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