[zypp-devel] managing upgrades -- not just installs -- of multiple kernel versions when zypper's multiversion support is enabled?
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.... /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@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Anyone ... ? On Sat, Mar 6, 2010 at 9:51 AM, 0bo0 <0.bugs.only.0@gmail.com> wrote:
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.... /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@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Saturday 06 March 2010 18:51:15 0bo0 wrote:
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 [...] 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 [...] 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 ...
To the satsolver 'Multiversion' just means, the already installed versions don't get deleted when a new package is installed. (similar to rpm -U vs -i). So the satsolver does not treat the different kernel-xen versions installed as individual packages with individual update candidates. The solver will look for one update candidate; most probably 2.6.33 or above. You could try to 'zypper dup --from KernelHEAD', then 'zypper dup --from KernelKOTD'. Maybe this fit's your needs. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Thu, Mar 11, 2010 at 2:14 AM, Michael Andres
To the satsolver 'Multiversion' just means, the already installed versions don't get deleted when a new package is installed. (similar to rpm -U vs -i).
I'd thought, or hoped, the logic was a bit more adaptable. Thanks for clearing that up.
So the satsolver does not treat the different kernel-xen versions installed as individual packages with individual update candidates. The solver will look for one update candidate; most probably 2.6.33 or above.
You could try to 'zypper dup --from KernelHEAD', then 'zypper dup --from KernelKOTD'. Maybe this fit's your needs.
Unfortunately, apparently not. @, zypper dup --from KernelKOTD Loading repository data... Reading installed packages... Computing distribution upgrade... 8 Problems: Problem: problem with installed package kernel-debug-devel-2.6.33-29.1.x86_64 Problem: problem with installed package kernel-default-2.6.33-29.1.x86_64 Problem: problem with installed package kernel-default-devel-2.6.33-29.1.x86_64 Problem: problem with installed package kernel-desktop-devel-2.6.33-29.1.x86_64 Problem: problem with installed package kernel-syms-2.6.33-29.1.x86_64 Problem: problem with installed package kernel-xen-2.6.33-29.1.x86_64 Problem: problem with installed package kernel-xen-devel-2.6.33-29.1.x86_64 Problem: problem with installed package kernel-source-2.6.33-29.1.noarch Problem: problem with installed package kernel-debug-devel-2.6.33-29.1.x86_64 Solution 1: Following actions will be done: downgrade of kernel-debug-devel-2.6.33-29.1.x86_64 to kernel-debug-devel-2.6.31.12-19.1.x86_64 deinstallation of kernel-debug-devel-2.6.33-29.1.x86_64 Solution 2: keep obsolete kernel-debug-devel-2.6.33-29.1.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): Doesn't appear too reliable, so it looks like manual intervention is required. I'm guessing that to do what I'd hoped, installed pkg metadata would need to include some record of the originating repo, and a zypper flag to 'dup', or whatever, from-to only _that_ repo would need to be implemented. Nice to have, but unclear if doable or planned. Thanks! -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (2)
-
0bo0 -
Michael Andres