From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; T312461)
Description of problem:
When using up2date (the previous version installed with RedHat 7.3) to get the
newest update (2.8.39-1.7.3), some files in /etc/sysconfig/rhn remain
unchanged, and new files with *.rpmnew suffixes are inserted into the directory.
This may be because up2date was in-use when it tried to update itself. Or, it
may be that the new up2date doesn't want to brute-force overwrite these files.
Oh, the files are rhn_register, rhnsd, and up2date, all in /etc/sysconfig/rhn,
and all original files are non-updated but all files have new *.rpmnew suffixes.
This MAY be by design, but nothing in the up2date process suggested that I
should overwrite these files with the new ones, or if I should just leave the
new files as-is. The update process *DID* warn that it was creating the
*.rpmnew files, but it did not give any clues as to their final dispositions.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RedHat 7.3, ensuring that up2date is install.
2. Setup up2date, register, etc.
3. Do the update with "up2date -u"
4. (Notice warning messages)
5. Check in /etc/sysconfig/rhn to see if the above mentioned files have been
updated or if they are new with *.rpmnew suffixes.
Actual Results: Original files rhnsd, rhn_register, and up2date remain non-
updated, but new files with *.rpmnew suffixes exist instead.
Expected Results: Shouldn't the files rhnsd, rhn_register, and up2date have
been updated? Running an "rpm -V up2date" indicates that these files are NOT
matching the update.
This may NOT actually be a bug, but an "un-documented user expectation". :)
That is, should the user (like me) manually update these files, or should they
remain as-is, with the new *.rpmnew names?
The update was part of a recent RHN errata package, RHBA-2002:140-25.
More or less thats whats supposed to happen. The next version wont
have the files marked noreplace however, so there shouldnt be
.rpmnew's with the next version.
version 2.8.39 or 3.0.15 or higher (seperate branches) should
include this fix.
Created attachment 83584 [details]
test case for this bug
Fix confirmed with up2date-3.1.15-7.