[Bug 223667] New: aborted kernel update not aborted because of dependencies
https://bugzilla.novell.com/show_bug.cgi?id=223667 Summary: aborted kernel update not aborted because of dependencies Product: openSUSE 10.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse-beta@cboltz.de QAContact: jsrain@novell.com (initially reported in bug 222829, comment #24) I run YaST2 online_update to install the kernel test updates. I clicked "Übernehmen" (continue/apply) to install the updates. Then I answered the dialog reminding me of a reboot after the kernel update with "Abbrechen" (cancel). After this, kernel-default was dropped in as auto-dependency :-( I clicked "Abbrechen" and now see the following: - the _patch_ "Test kernel update" is taboo - the patches "perl-Bootloader" and "kernel module packages" are selected for installation - the perl-bootloader package was marked for update ("Aktualisieren") (so far, everything is ok. Now to the big problem...) - some kmp packages (those I have installed) were marked for update - the kernel-default _package_ was marked for update - but I had explicitely rejected it and the _patch_ is marked as taboo. Expected result: - kernel-default should not be marked for update - the kmp packages should also not be updated because they depend on the kernel update I'm just syncing the y2logs and a solver testcase to www.cboltz.de/tmp/ (filename y2logs-tabookernel-222829.tar.bz2, too large for bugzilla) Sidenotes: - I'm going to update to RC1, so if you want me to test something, you have to be fast ;-) - workaround: set the kmp patch to taboo also - maybe the solution is to make the kmp patch depend on the kernel patch -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|schubi@novell.com | Resolution| |WORKSFORME ------- Comment #3 from schubi@novell.com 2006-11-28 07:27 MST ------- Thanks for the logs. "- the kernel-default _package_ was marked for update - but I had explicitely rejected it and the _patch_ is marked as taboo." The kmp packages will be updated. They need a new kernel which will be selected by the solver. Setting "taboo" to the patch means not that the packages will not be handled by other dependencies. It is the same as with patterns. If two patterns recommend the same package the package will be installed if one pattern has been set to install and the other to taboo. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 suse-beta@cboltz.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Comment #4 from suse-beta@cboltz.de 2006-11-29 11:59 MST ------- I know that new KMPs need a new kernel ;-) Sorry, this doesn't "workforme". It's a real problem. My point is: I explicitely rejected the kernel update because I wasn't able to reboot at this moment. If the new kernel is installed anyway (and the user doesn't reboot because he rejected the kernel update and thinks all is OK), it will cause several "strange" problems in the running system or will even break the installation if there are KMP updates available while running YOU in the installation. The correct solution is: If the kernel update is rejected, the KMP updates should automatically be rejected, too. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 ------- Comment #6 from suse-beta@cboltz.de 2006-12-01 10:33 MST ------- Can you do a workaround by using clever dependencies? Just a wild guess: Make the KMP patch depend on the kernel patch Since the kernel patch is set to taboo when rejected, chances are better that the KMP patch and its packages are unselected then. Dependency should be: KMP patch requires "kernel patch >= KMP patch" (>= because hopefully there will be less KMP updates than kernel updates) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dmacvicar@novell.com |hmuelle@novell.com Status|REOPENED |NEW ------- Comment #7 from schubi@novell.com 2006-12-04 01:38 MST ------- What is the reason for not including the kmp packages int the kernel patch. Harald ? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 hmuelle@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hmuelle@novell.com |schubi@novell.com ------- Comment #8 from hmuelle@novell.com 2006-12-04 03:41 MST ------- In short the high level picture, the contraints my differ for various products: These KMP packages need to come from Novell in general, obviously. (e.g. NVidia, ATI) Even if the are provided by us - Novell, they might be provided by another group independently of our updates. E.g. the KMP might be part of an addon product. (e.g. OES provides some KMP on top of SLES9 kernel) The most obvious reason a KMP needs to be updated only if there is a incompatible change in a kernel. Our goal is to keep the kABI stable if possible, so that normally a KMP need not to be updated every time when we have to provide a kernel update. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|schubi@novell.com |lslezak@novell.com ------- Comment #9 from schubi@novell.com 2006-12-04 05:33 MST ------- We had a look into the messages and there will be not handled the status "cancel". So I assume that the message should not show the cancel button. Ladislav can you help here ? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 ------- Comment #10 from suse-beta@cboltz.de 2006-12-04 14:25 MST ------- (In reply to comment #9)
We had a look into the messages and there will be not handled the status "cancel". So I assume that the message should not show the cancel button.
If you are talking about the reboot reminder dialog where I clicked cancel (which I assume): a) canceling works if nothing requires the new kernel (read: if no KMP update is available) b) canceling is necessary if someone installs the updates during installation - at least the dialog states so ;-) Conclusion: Please do _not_ remove the cancel button. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|lslezak@novell.com |schubi@novell.com ------- Comment #11 from lslezak@novell.com 2006-12-06 02:14 MST ------- OK, reassigning back to Schubi... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|schubi@novell.com |visnov@novell.com ------- Comment #12 from schubi@novell.com 2006-12-07 01:38 MST ------- Good. The popup will be generated by "licence to confirm". So my comment #9 is wrong cause it is NOT a message resolvable.
From the solver sight everything is OK cause the dependencies are solved correctly (comment #3). As we cannot put kmp and kernel patches together (comment #8) and we need a connection between these patches I see the same solution as Christian (comment #6) only. Has anyone another solution ? Otherwise Harald/Stano please make a decision.
-- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 visnov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |kkaempf@novell.com ------- Comment #13 from visnov@novell.com 2007-02-06 05:01 MST ------- Klaus, any suggestions? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 kkaempf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|kkaempf@novell.com | ------- Comment #14 from kkaempf@novell.com 2007-02-08 06:24 MST ------- comment #3: We are aware of the problem with patterns but haven't found a proper solution yet. There is ongoing discussion on opensuse-factory on this topic comment #4: I see your point. But I don't agree with the proposed solution. A rejected (tabooed or locked) kernel patch should lock the update kernel package in order to prevent its installation. However, it should not affect kmp updates as they are not necessarily tied to the kernel update. A newer kmp package might match the existing kernel. If it does not (if it needs a newer kernel), the locked kernel package will prevent the kmp upgrade. There is still a slight chance that another kernel package (different from the locked one) fulfills the kmp requirement and gets selected for upgrade. So we probably have to lock all packages with the same name (i.e. all 'kernel-default') -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 kmachalkova@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Ulrich.Windl@rz.uni-regensburg.de ------- Comment #15 from kmachalkova@novell.com 2007-02-09 13:32 MST ------- *** Bug 237269 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 visnov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|visnov@novell.com |kkaempf@novell.com Component|YaST2 |libzypp QAContact|jsrain@novell.com |kkaempf@novell.com -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 visnov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rafpolak@o2.pl ------- Comment #16 from visnov@novell.com 2007-02-27 01:40 MST ------- *** Bug 205760 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |j.sendler@os.bvnk.org ------- Comment #18 from schubi@novell.com 2007-03-29 07:36 MST ------- *** Bug 255677 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|schubi@novell.com |hmuelle@novell.com ------- Comment #19 from schubi@novell.com 2007-04-04 07:07 MST ------- currently we have following licence to confirm in the patches: -------- This update can be used to install a new kernel. If you decide to use the kernel update, we recommend that you reboot your system upon completion of the YaST Online Update, as additional kernel modules may be needed which can only be loaded after the system is rebooted. If you are in the course of performing a new installation, you should deselect this kernel update in order to avoid problems with the hardware detection during the installation. --------- Which means that you have to reboot your machine if the kernel *PACKAGE* has been updated. This popup will be not shown if the user select the kernel package for update only (It is possible). But which should also happens. So I think that this licence to confirm belongs to the package and not to the patch. If the user recjects this licence the kernel package will be locked and a new solver run will be started again which shows additional problems e.G. with kmp packages. I have tested with an own repo and ist works. So put this text to the kernel descriptions in the primary.xml file. Harald, can you manage it ? Klaus, any objections ? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vaclavik@ujp.cz ------- Comment #23 from mhorvath@novell.com 2007-05-21 06:02 MST ------- *** Bug 275880 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 ------- Comment #24 from mhorvath@novell.com 2007-05-21 06:07 MST ------- *** Bug 275880 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|schubi@novell.com | ------- Comment #26 from schubi@novell.com 2007-06-08 02:10 MST ------- It seems that there is a bug in YaST2 and package bindings too. See Bug 279491. Nevertheless we need the licence description on the correct place ---> Put it to the packages an not to patches. ;-) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223667#c27
Harald Mueller-Ney
https://bugzilla.novell.com/show_bug.cgi?id=223667#c28
Ruediger Oertel
https://bugzilla.novell.com/show_bug.cgi?id=223667#c29
Stefan Schubert
and might even not be touched at all for some cases (where a patch just adds new metadata using existing rpms but adds no new rpms).
Than you will not have to need the "reboot" popup at all. I think that this popup should also be shown if you are installing the kernel while e.g. the single selection frame. So I believe that the correct place will be still in primary.xml. -- 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=223667#c30
Ruediger Oertel
https://bugzilla.novell.com/show_bug.cgi?id=223667
Ruediger Oertel
https://bugzilla.novell.com/show_bug.cgi?id=223667#c33
Harald Mueller-Ney
https://bugzilla.novell.com/show_bug.cgi?id=223667
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=223667#c35
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=223667
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=223667#c36
Stephan Kulow
participants (1)
-
bugzilla_noreply＠novell.com