[opensuse-security] Patch slessp2-xen (version 7133) refuses to install on SLES11SP2
Hello, I am trying to apply latest security patches to a SLES11SP2 Xen host (i.e. a Dom0) but am getting a conflict: Problem: nothing provides kernel(default:net_core_dev) = 35139cad513aec92 needed by xen-kmp-default-4.1.3_06_3.0.51_0.7.9-0.7.1.x86_64 Solution 1: deinstallation of xen-kmp-default-4.1.3_04_3.0.42_0.7-0.5.1.x86_64 Solution 2: do not install patch:slessp2-xen-7133.noarch Solution 3: break xen-kmp-default-4.1.3_06_3.0.51_0.7.9-0.7.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): Could this be because I have just applied a kernel patch, but not yet rebooted? I want to minimise the amount of downtime. Running kernel is # uname -a Linux virt0 3.0.38-0.5-xen #1 SMP Fri Aug 3 09:02:17 UTC 2012 (358029e) x86_64 x86_64 x86_64 GNU/Linux but installed kernel is # rpm -qf /boot/vmlinuz-xen kernel-xen-base-3.0.42-0.7.3 # rpm -qa | grep xen-kmp xen-kmp-default-4.1.3_04_3.0.42_0.7-0.5.1 Any suggestions? Regards, Bob ============================================================== Bob Vickers R.Vickers@cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691 -- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-security+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, this problem is already known. The XEN update was built against the wrong kernel version AFAIK. We will fix this problem ASAP. HTH, Thomas Am 10.12.2012 13:49, schrieb Bob Vickers:
Hello,
I am trying to apply latest security patches to a SLES11SP2 Xen host (i.e. a Dom0) but am getting a conflict:
Problem: nothing provides kernel(default:net_core_dev) = 35139cad513aec92 needed by xen-kmp-default-4.1.3_06_3.0.51_0.7.9-0.7.1.x86_64 Solution 1: deinstallation of xen-kmp-default-4.1.3_04_3.0.42_0.7-0.5.1.x86_64 Solution 2: do not install patch:slessp2-xen-7133.noarch Solution 3: break xen-kmp-default-4.1.3_06_3.0.51_0.7.9-0.7.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c):
Could this be because I have just applied a kernel patch, but not yet rebooted? I want to minimise the amount of downtime.
Running kernel is # uname -a Linux virt0 3.0.38-0.5-xen #1 SMP Fri Aug 3 09:02:17 UTC 2012 (358029e) x86_64 x86_64 x86_64 GNU/Linux
but installed kernel is # rpm -qf /boot/vmlinuz-xen kernel-xen-base-3.0.42-0.7.3
# rpm -qa | grep xen-kmp xen-kmp-default-4.1.3_04_3.0.42_0.7-0.5.1
Any suggestions?
Regards, Bob
============================================================== Bob Vickers R.Vickers@cs.rhul.ac.uk Dept of Computer Science, Royal Holloway, University of London WWW: http://www.cs.rhul.ac.uk/home/bobv Phone: +44 1784 443691
- --
Thomas Biege
participants (2)
-
Bob Vickers -
Thomas Biege