https://bugzilla.novell.com/show_bug.cgi?id=401125 Summary: zypper loops when on kernel conflict the "keep" choice is selected Product: openSUSE 11.0 Version: Final Platform: PC OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: mrmazda@ij.net QAContact: qa@suse.de Found By: --- My usual upgrade method is to use Smart, since other methods like zypper and yast are too difficult to get to leave kernels, and especially, working initrds, in place. However after converting one of my Factory installs over to the new 11.0 repositories today, Smart didn't seem capable of finding the new packages from 11.0 repos that weren't in the 11.0rc1 repos. So, I manually fetched rpm, perl-Bootloader, mkinitrd, kernel-pae-2.6.25.5-1.1, splashy, yast2-bootloader, zypper, libzypp & a few others and deps, then installed them using rpm. Next I rebooted to ensure that the new kernel and initrd actually worked, after which without first removing the prior kernel-pae-2.6.25.4-10 I tried to do zypper ref; zypper dup. Zypper then found a bizarre conflict and offer of resolutions: Problem: conflicting requests Solution 1: keep kernel-pae Solution 2: do not install kernel-pae-2.6.25.5-1.1.i586 When I chose 1, it looped until I chose 2 instead. When I chose 2, it told me: .. The following packages are going to be REMOVED: kernel-pae kernel-pae While zypper was doing the dup I examined /boot and saw complete absence of kernels, but when done I found via rpm query it had installed kernel-debug. I then checked /lib/modules and found directories for pae, default, debug and xen, even though there was no xen or default kernel or initrd in /boot. I inspected /boot/grub/menu.lst and found only one 11.0 entry with enough on the kernel line to enable a boot (failsafe for the pae kernel). None of the rest had root= or anything else on them. Zypper should leave all the kernels undisturbed when any kernel in the upgrade list matches any kernel already installed. Zypper should not present a choice when announcing a conflict that it won't or can't execute. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.