Keyboard problem after latest updates

[Andrew Farris]

Michal Jaegermann wrote:
> On Sat, Feb 23, 2008 at 04:17:06PM +0100, Antonio M wrote:
>> only one word: I was not switching from a version to another, but
>> applied some updates.
> 
> That is precisely what we were talking about.  OTOH would make you
> much happier if you would upgrade from F8 to, future, F9 and be
> confronted with the same issue?  Because this "release upgrade" is
> what in some sense you are doing here - if only "step-by-step".
> 
>     Michal

This is not true.  The process that a rawhide box goes through is VERY different 
from a fully updated release being upgraded to a new release.  The 
'step-by-step' that occurs is different because each edge in the graph (i.e. the 
path you took, step by step) has the possibility of being a very broken package. 
   The process is not necessarily distinct.. each rawhide box may or may not 
have every upgrade done (you could skip a day and not even apply some packages 
that got replaced two days in a row).

The other main difference is that later packages (near the actual new release) 
will have many bug fixes to make the upgrade process smoother *because rawhide 
testers found the bugs*.

A rawhide box that starts as F8 and gets updated hundreds of times before F9 
release is NOT expected to be the same as an F8 box that is upgraded once to 
F9... it needs to be reinstalled as a fresh F9 install after the release to be 
truly stable F9 install.  Rawhide is not a step-by-step upgrade from F8 to F9.

-- 
Andrew Farris <lordmorgul at gmail.com> www.lordmorgul.net
  gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E A2E0 F0F6 E622 C99B 1DF3
No one now has, and no one will ever again get, the big picture. - Daniel Geer
----                                                                       ----