Bug 61853

Summary:	up2date up2date screw old configuration file
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <mpo>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	gafton, mihai.ibanescu, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-05-08 20:51:50 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 Need Real Name 2002-03-25 10:49:02 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:
when you up2date up2date it rewrites you config file. I have specifically 
ignored  certain groups of file ie. perl from being updated so as not to break 
my webserver. however after up2date updated it's self it removed the ignore 
perl section out of the config file. These mean that my nightly cron update 
caused perl to be downloaded and my webserver to crash.

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


How reproducible:
Always

Steps to Reproduce:
1.up2date up2date
2.
3.
	

Actual Results:  It rewrites the config file with the standard

Expected Results:  It should include any changes required to the config file 
but also keep packages which are specifically ignored

Additional info:

Comment 1 Adrian Likins 2002-05-08 20:51:45 UTC

Do you know if the old up2date config was setup to ignore
possible file conflict issues?

Generally, up2date wont update rpms if the status of the config
files is in a state that may cause something to not work. It
sounds like up2date was in this state (locally modified config,
and a difference between old default and new default configs)
so if --force or "noReplaceConfig" was setup, it would have
overwrite the config file.

Comment 2 Adrian Likins 2002-08-09 03:11:34 UTC

There were some rpm bugs that could result in the wrong
version of a config file being used. These should be fixed
with current releases.