Axel Thimm wrote at about 00:24:27 +0300 on Friday, June 13, 2008: > On Thu, Jun 12, 2008 at 02:26:06PM -0400, Jeffrey J. Kosowsky wrote: > > > > I just tried installing the rpm but it wants to remove for > > > > dependencies one of my 2 older kernels (and associated kmdl's) and > > > > upgrade my kernel to 2.6.25. > > > > Can you post command & output? Thanks! > > Sure... Here it is (plus I am also appending my currently installed > > nvidia and kernel-related rpms) > > > ---> Package kernel.i686 0:2.6.25.4-10.fc8 set to be installed > > > ---> Package kernel.i686 0:2.6.24.7-92.fc8 set to be erased > > > Removing: > > kernel i686 2.6.24.7-92.fc8 installed > > 46 M > > Installing for dependencies: > > kernel i686 2.6.25.4-10.fc8 updates > > 18 M > > > Also, my current running kernel is: 2.6.24.4-64.fc8 > > > > And, I have the following kernel-related rpms currently installed: > > kernel-2.6.24.4-64.fc8.i686.rpm > > kernel-2.6.24.7-92.fc8.i686.rpm > > My educated guess: The update tried to pull in a new kernel. yum found > that you had two already installed and the default is to keep only two > (?). But it couldn't remove the oldest one as it was the running > kernel, so it went on to the next one. > Yes -- I do have it set to keep the latest two kernels. I think your 'guess' is probably right on target.
> If that's right then there is some bug in yum's installonlyn kernel > logic (if one kernel needs to be skipped it should reduce the number of > to be removed kernels by one, not leave it alone). It does sound like a bug. I have never run into it before since I usually reboot after a kernel upgrade but since my system is so stable and since I keep a lot of stuff open in emacs (such as half-composed mail) and due to some combination of laziness and/or forgetfullness, I never bothered to reboot after the last kernel update. > I'd say that the rest is expected behaviour: You asked for the legacy > driver that currently points to a version that only offers kmdls for > the latest kernel, so the depsolver had to include that kernel into > the update. > > But at least this answers the original question: Yes, the legacy > drivers do support 2.6.25. :) That is good news (I think). > -- > Axel.Thimm at ATrpms.net > > [GNUPG:] ERRSIG 401552D4639A99F1 17 2 01 1213305867 9 > [GNUPG:] NO_PUBKEY 401552D4639A99F1 _______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
