Mailinglist Archive: zypp-devel (32 mails)

[0bo0 <0.bugs.only.0@xxxxxxxxx>]

i've enabled multiversion kernel support

        grep multi /etc/zypp/zypp.conf
                multiversion = provides:multiversion(kernel)

in recent zypper,

        rpm -qa | grep -i zypp
                zypper-1.4.0-4.1.x86_64
                libzypp-6.30.4-2.3.x86_64

enabling 2 OBS repos,

        egrep "base|pri" /etc/zypp/repos.d/Kernel*
                
/etc/zypp/repos.d/KernelHEAD.repo:baseurl=http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2
                /etc/zypp/repos.d/KernelHEAD.repo:priority=9
                
/etc/zypp/repos.d/KernelKOTD.repo:baseurl=http://download.opensuse.org/repositories/Kernel:/openSUSE-11.2/openSUSE_11.2
                /etc/zypp/repos.d/KernelKOTD.repo:priority=9

i've installed,

        zypper se -s | grep -i kernel-xen | grep ^i
                i | kernel-xen    | package    | 2.6.33-29.1     | x86_64 | 
KernelHEAD
                i | kernel-xen    | package    | 2.6.31.12-18.1  | x86_64 | 
KernelKOTD

so that,

        ls -al vmlinuz* initrd*
                -rw-r--r-- 1 root root 8221947 2010-03-06 09:06 
initrd-2.6.31.12-18-xen
                -rw-r--r-- 1 root root 8506658 2010-03-06 08:46 
initrd-2.6.33-29-xen
                lrwxrwxrwx 1 root root      20 2010-03-06 09:16 initrd-xen ->
initrd-2.6.33-29-xen
                -rw-r--r-- 1 root root 3377356 2010-03-05 23:33 
vmlinuz-2.6.31.12-18-xen
                -rw-r--r-- 1 root root 3260908 2010-03-06 00:02 
vmlinuz-2.6.33-29-xen
                lrwxrwxrwx 1 root root      21 2010-03-06 09:16 vmlinuz-xen ->
vmlinuz-2.6.33-29-xen

when kernel-xen pkgs in either KernelKOTD or KernelHEAD repos change,
i'd expected that a simple 'zypper up' or 'zypper dup' would pick up
those changes, and update respective, installed kernels -- as is the
case in single-version (i.e., NOT multiversion enabled) installations.

e.g., starting with installed,

        kernel-xen-2.6.33-28.1.x86_64
        kernel-xen-2.6.31.12-17.1.x86_64

assuming, of course, available updates, a

        zypper up

would simply/ideally upgrade,

        kernel-xen-2.6.33-28.1.x86_64     -->  kernel-xen-2.6.33-29.1.x86_64
        kernel-xen-2.6.31.12-17.1.x86_64  -->  kernel-xen-2.6.31.12-18.1.x86_64

removing the old versions, and upgrading the symlinks in /boot as appropriate.

that's, however, not the case.  with multiversion support enabled, it
seems that one, or the other, kernel _might_ get updated, and the
symlinks in /boot are mod'd to whatever gets last installed.

these may be an unavoidable artifacts, or a misconfiguration on my part ...

atm, to keep things working, I find it's best/necessary to _manually_
exec (note: zypper up, &/or using -r (repo) have no effect):

        zypper in kernel-xen-2.6.33-29.1.x86_64
        zypper in kernel-xen-2.6.31.12-18.1.x86_64
        cd /boot
        ln -sf vmlinuz-2.6.33-29-xen vmlinuz-xen
        ln -sf initrd-2.6.33-29-xen  initrd-xen

question:

        *IS* there a way to install AND upgrade/maintain multiple versions of
kernels using zypper?
        
        or, in the case of multiversion support, are we relegated to manual
intervention?

Thanks.
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx