On two RHL 7.0 systems, I upgraded to glibc-2.2.4-18.7.0.
The update warned about having created an /etc/localtime.rpmnew. Since this
is a binary file and I could not spot differences, and since the update
touched this file and I thus thought it really should be updated, I did a
"mv /etc/localtime.rpmnew /etc/localtime".
I shouldn't have done that, I realize afterwards, because from that point
on my system kept EDT as timezone, as opposed to the correct CEST. I could
only resolve this by "cp /usr/share/zoneinfo/posix/Europe/Stockholm
/etc/localtime".Proposed solution: Updates of glibc should not care about
the /etc/localtime file.
That's normal rpm behaviour. /etc/localtime has to be IMHO part of glibc,
so that running timeconfig is not strictly necessary, and is %config(noreplace)
exactly so that it doesn't blow away your own setting. Blindly copying
.rpmnew files to the original files is a bad idea.
> Blindly copying .rpmnew files to the original files is a bad idea.
I always diff rpmnew files, but since this is a binary file, that was hardly
helpful. That's the problem - it creates a rpmnew file although none should be
needed. But maybe this is more of a problem with rpm.