[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

kernel RPMs dependency on removing prior kernel?



Is the following kernel RPM behavior really necessary?  Yum repeatedly attempts
to remove at least one kernel whenever a kernel is updated or installed, and
fails if it cannot do so...  Removing a kernel to keep things a little cleaner
with kernel updates is not so bad, but continuing when it cannot do that is what
I'd want it to do (not fail).  I want these installed kernels, and I want them
staying right where they are, with the nvidia modules as well (these kernels all
have a buggy behavior with my usb drive and I'm keeping them to go back and test
if it gets resolved later).

Why cannot the RPM continue if removing a kernel fails?  And why is it
attempting to remove my NEWEST other kernel (the currently running/working one)?
 Wouldn't it be best to have the currently running kernel stay where it is with
an update or install irregardless of whether another prior kernel had been removed?

I never want a kernel rpm installing itself to remove my running kernel, so why
would this (2.6.23.1-42) dependency even get listed?

22:35:38  |root:1| |13 files:69M ~| |0 jobs|
 - yum install kernel.i686
 Loading "refresh-updatesd" plugin
 fedora                    100% |=========================| 2.1 kB    00:00
 livna-development         100% |=========================| 2.1 kB    00:00
 updates-testing           100% |=========================| 2.3 kB    00:00
 livna                     100% |=========================| 2.1 kB    00:00
 updates                   100% |=========================| 2.3 kB    00:00
 Setting up Install Process
 Parsing package install arguments
 Package kernel - 2.6.23.1-42.fc8.i686 is already installed.
 Resolving Dependencies
 --> Running transaction check
 --> Processing Dependency: kernel-i686 = 2.6.23.1-42.fc8 for package:
kmod-nvidia-2.6.23.1-42.fc8
 ---> Package kernel.i686 0:2.6.23.1-49.fc8 set to be updated
 --> Finished Dependency Resolution
 --> Running transaction check
 ---> Package kernel.i686 0:2.6.23.1-41.fc8 set to be erased
 --> Processing Dependency: kernel-i686 = 2.6.23.1-41.fc8 for package:
kmod-nvidia-2.6.23.1-41.fc8
 ---> Package kernel.i686 0:2.6.23-6.fc8 set to be erased
 --> Processing Dependency: kernel-i686 = 2.6.23-6.fc8 for package:
kmod-nvidia-2.6.23-6.fc8
 --> Processing Dependency: kernel-i686 = 2.6.23.1-42.fc8 for package:
kmod-nvidia-2.6.23.1-42.fc8
 ---> Package kernel.i686 0:2.6.23.1-49.fc8 set to be installed
 ---> Package kernel.i686 0:2.6.23.1-37.fc8 set to be erased
 --> Processing Dependency: kernel-i686 = 2.6.23.1-37.fc8 for package:
kmod-nvidia-2.6.23.1-37.fc8
 --> Running transaction check
 ---> Package kmod-nvidia-2.6.23-6.fc8.i686 0:100.14.19-8.lvn8 set to be erased
 --> Processing Dependency: kernel-i686 = 2.6.23.1-42.fc8 for package:
kmod-nvidia-2.6.23.1-42.fc8
 ---> Package kmod-nvidia-2.6.23.1-37.fc8.i686 0:100.14.19-14.lvn8 set to be erased
 ---> Package kmod-nvidia-2.6.23.1-41.fc8.i686 0:100.14.19-15.lvn8 set to be erased
 --> Finished Dependency Resolution
 Error: Missing Dependency: kernel-i686 = 2.6.23.1-42.fc8 is needed by package
kmod-nvidia-2.6.23.1-42.fc8

22:32:47  |root:1| |13 files:69M ~| |0 jobs|
 - cat /proc/version
 Linux version 2.6.23.1-42.fc8 (kojibuilder xenbuilder4 fedora phx redhat com)
(gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Tue Oct 30 13:55:12 EDT 2007

 22:35:25  |root:1| |13 files:69M ~| |0 jobs|
  - rpm -q kernel
  kernel-2.6.23-6.fc8
  kernel-2.6.23.1-37.fc8
  kernel-2.6.23.1-41.fc8
  kernel-2.6.23.1-42.fc8

-- 
Andrew Farris <lordmorgul gmail com> <ajfarris gmail com>
   gpg 0xC99B1DF3 at pgp.mit.edu

No one now has, and no one will ever again get, the big picture. - Daniel Geer
----                                                                       ----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]