https://bugzilla.novell.com/show_bug.cgi?id=680149 https://bugzilla.novell.com/show_bug.cgi?id=680149#c1 Duncan Mac-Vicar changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |NEEDINFO CC| |dmacvicar@novell.com InfoProvider| |mls@novell.com --- Comment #1 from Duncan Mac-Vicar 2011-03-18 12:18:13 UTC --- It wants to remove ONE of the TWO kernel-desktops you have installed in parallel from the mix of 11.3, 11.4 and Factory repos you have in your system. But running deptestomatic does not tell me why both kernel conflict it conflicts. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=680149 https://bugzilla.novell.com/show_bug.cgi?id=680149#c3 --- Comment #3 from Casual J. Programmer 2011-03-18 17:29:39 UTC --- rpm -qa | grep kernel-desktop kernel-desktop-2.6.37.1-2.2.x86_64 kernel-desktop-devel-2.6.38-2.1.x86_64 kernel-desktop-2.6.38-2.1.x86_64 Usually the old kernel gets deleted after an update. 1. yast2 does not complain 2. zypper does not specify which kernel it wants to remove

In order to fix these dependencies, the following actions need to be taken: Continue? [y/n/?] (y):

3. zypper does not complain on dup only on ve -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=680149 https://bugzilla.novell.com/show_bug.cgi?id=680149#c5 --- Comment #5 from Casual J. Programmer 2011-03-18 17:47:27 UTC --- If I'm not mistaken, nobody suggested it gets deleted by zypper (except if you let it have it's way after ve). Both kernels work fine, nothing is amiss, except zypper seeing dependency conflicts where there are none. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=680149 https://bugzilla.novell.com/show_bug.cgi?id=680149#c7 --- Comment #7 from Casual J. Programmer 2011-03-18 17:58:36 UTC --- No, the relevant line in /etc/zypp/zypp.conf is empty (default), yet I maintain, that something is amiss. See comment #3 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=680149 https://bugzilla.novell.com/show_bug.cgi?id=680149#c9 --- Comment #9 from Casual J. Programmer 2011-03-19 09:12:11 UTC ---

I don't know what you mean by 'yast does not complain', ...

I am using yast2 (qt) sw_single, selecting check dependencies from the menu (dependencies/check now) returns "All package dependencies are OK." In addition I think zypper does, in other cases of dependency conflicts, offer three options, usually, 1. keep the old situation, 2. accept the new situation dropping xyz, 3. break the dependencies. Why does it not let the user decide in this case ? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=680149 https://bugzilla.novell.com/show_bug.cgi?id=680149#c11 --- Comment #11 from Casual J. Programmer 2011-03-21 11:22:02 UTC --- Makes a lot of sense, doesn't it ? man zypper states: " verify (ve) [options] Check whether dependencies of installed packages are satisfied. In case that any dependency problems are found, zypper suggests packages to install or remove to fix them." Having multiple kernels isn't exactly a "dependency conflict", seems to me a classical case of "it's not a bug, it's a feature". I think we should concentrate on #3 and #9 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=680149 https://bugzilla.novell.com/show_bug.cgi?id=680149#c13 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #13 from Michael Andres 2011-11-04 15:46:53 CET --- (In reply to comment #3)

2. zypper does not specify which kernel it wants to remove

...

In order to fix these dependencies, the following actions need to be taken: Continue? [y/n/?] (y):

The '?' shows further options: y - Yes, accept the summary and proceed with installation/removal of packages. n - No, cancel the operation. v - Toggle display of package versions. a - Toggle display of package architectures. r - Toggle display of repositories from which the packages will be installed. m - Toggle display of package vendor names. d - Toggle between showing all details and as few details as possible. g - View the summary in pager. 'v' or 'd' will show the version.

3. zypper does not complain on dup only on ve

There's no need for dup to complain if it does not cause immediate trouble, and the next update of kernel-desktop will remove the 2 old versions anyway (unless marked as "multiversion" in /etc/zypp/zypp.conf). 've' is expected to raise all issues immediately, and this is what it does. The 2nd kernel is here by accident, so it gets removed. If you intentionally keep multiple versions, you should enter it in /etc/zypp/zypp.conf. -- 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.