Andrew Hodgson wrote:
Each time I do an upgrade (i.e, RHEl4U4 to RHEL4U5 and from 5.0 to 5.1
today), I always end up with a bunch of .rpmnew files for files I
haven’t touched. Are these definitely safe to merge in to the .conf
or other data file using something like mv file.conf.rpmnew
file.conf? Could some of these be because I have I386 and x86_64
packages installed?
This has been a problem plaguing Fedora for quite some time as well.
I've got into the habit of doing something like this:
for f in $(find / -xdev -name '*.rpmnew); do
diff $f ${f%.rpmnew} && rm $f
done
I think that's right -- you'll probably want to be a little cautious
before cut'n'pasting something untested that includes an "rm" :-)
Generally speaking, there's no output at all from that loop but if there
is it points out specific files that have been updated that you should
address.
I think it's a multiarch bug that needs to be fixed really, but I'm
afraid to say I've never got as far as investigating the root cause or
even looking in bugzilla.
jch
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
