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