Bug 25397

Summary: up2date fails to update specifically named files.
Product: [Retired] Red Hat Linux Reporter: Jonathan J. Miner <miner>
Component: up2dateAssignee: Preston Brown <pbrown>
Status: CLOSED NOTABUG QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: srevivo
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: 2001-02-20 01:35:37 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 Jonathan J. Miner 2001-01-31 20:24:10 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)


When noReplaceConfig=1 is in /etc/sysconfig/rhn/up2date, up2date will not 
update files where the config has changed, even if it is explicitly told 
to do so.  (i.e. up2date pkgname)

Reproducible: Always
Steps to Reproduce:
1. Install RH7
2. Modify /etc/ld.so.conf (add a non-standard directory, for whatever 
reason)
3. Run "up2date -l", this will list all updates, along with listing glibc 
as a package that will be skipped because its configuration has changed.
4. Run "up2date glibc" to update glibc, regardless the status of it's 
configuration files.

Actual Results:  Does not update, listing that the package was skipped.

Expected Results:  Update the package, since it was explicitly requested.
Comment 1 Adrian Likins 2001-02-08 04:54:37 UTC 
This should be fixed in the next release of up2date.
Comment 2 Preston Brown 2001-02-09 03:39:46 UTC 
fixed is stretching it; the old behaviour was the original design.  However, we
agree that what you tried to do is more intuitive, so we have changed it.

This will be the default behaviour in the next release.
Comment 3 Cristian Gafton 2001-02-20 01:35:32 UTC 
Assigned QA to jturner
Comment 4 Jay Turner 2001-03-07 21:10:39 UTC 
We have implemented a '--force' option which is used to override all
configuration options and just do what the user says (download, install,
whatever)  So, that being the case, we are going to leave this feature as designed.