On Sat, Oct 14, 2006 at 09:37:59PM -0400, Jim Cornette wrote:
Michal Jaegermann wrote:
>On Sat, Oct 14, 2006 at 12:25:50PM -0400, Thomas J. Baker wrote:
>>>On Wed, 2006-03-15 at 10:18 -0500, Julian C. Dunn wrote:
>>>>I just did a yum update, updating to initscripts 8.31.1-1 (among other
>>>>things like a new kernel).
>>I too had this happen on my laptop. It only happened on one of my three
>>rawhide systems so it's hard to figure out exactly why.
>Things like that happen when instead of updating a package yum
>decides to remove an old package first and later to install a new
>version. Look at
What is happening here? Is the new package upgraded, then the older
package removed, taking out files from the newly installed package?
No, not really. At least it does not seem to be that way.
A bug report quoted above has examples where such problem was
observed. Look at a sequence of events which follows
"Running Transaction" to see "Removing/Updating" and effects.
If this would happen with packages which do not have config files
then you would not get into any troubles . The issue appears to be
that "remove" step saves "not-anymore-needed" configuration files
saving them with .rpmsave suffix, but "update" knows that it should
not clobber config files which originally were there so it refrains
from unpacking defaults ones. That is actually what it _should_ do.
Net effects may turn out to be nasty.
I assume that what Thomas and Julian are talking about is
another manifestation of that bug. If that is really something
else that would interesting too.