[opensuse-factory] broken kernel locking?
Because of https://bugzilla.novell.com/show_bug.cgi?id=786318 I'm in the habit of setting a lock on the installed kernel, usually 'zypper al kernel-desktop', but sometimes kernel-default, depending on system, before doing a zypper dup; and when the dup is done, I unlock and dup again so as to minimize wasted bandwidth and time wasted uselessly building new initrds that will be replaced within minutes, if not mere seconds. Recently this stopped working, in that if kernel-desktop is installed and locked, kernel-default will be installed. If kernel-default is also locked, kernel-debug will be installed. If kernel-debug is also locked, kernel-pae will be installed. If kernel-pae is also locked, kernel-vanilla will be installed. Is this new behavior intentional? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-09-08 at 19:40 -0400, Felix Miata wrote:
Is this new behavior intentional?
I think you have to lock the installed kernel and taboo the update. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlItDrAACgkQtTMYHG2NR9WUWwCeKU0sWHr3/sRysUjMN4cQ6Asn gksAn0yuMkpHgX9jGiflZNwMqQQ3NekY =LFBk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Sonntag, 8. September 2013 schrieb Felix Miata:
Because of https://bugzilla.novell.com/show_bug.cgi?id=786318 I'm in the habit of setting a lock on the installed kernel, usually 'zypper al kernel-desktop', but sometimes kernel-default, depending on system, before doing a zypper dup; and when the dup is done, I unlock and dup again so as to minimize wasted bandwidth and time wasted uselessly building new initrds that will be replaced within minutes, if not mere seconds. Recently this stopped working, in that if kernel-desktop is installed and locked, kernel-default will be installed. If kernel-default is also locked, kernel-debug will be installed. If kernel-debug is also locked, kernel-pae will be installed. If kernel-pae is also locked, kernel-vanilla will be installed.
Is this new behavior intentional?
zypper al 'kernel*' should help. Nevertheless, the behaviour sounds strange - please open a bugreport. (Attaching the zypper logs and maybe also a solver testcase would be helpful.) Regards, Christian Boltz --
8.1 ist nicht 9.0 Also in der Quersumme schon ;-) [> Henne Vogelsang und Manfred Tremmel in suse-linux]
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-09-09 13:01 (GMT+0200) Christian Boltz composed:
Am Sonntag, 8. September 2013 schrieb Felix Miata:
Because of https://bugzilla.novell.com/show_bug.cgi?id=786318 I'm in the habit of setting a lock on the installed kernel, usually 'zypper al kernel-desktop', but sometimes kernel-default, depending on system, before doing a zypper dup; and when the dup is done, I unlock and dup again so as to minimize wasted bandwidth and time wasted uselessly building new initrds that will be replaced within minutes, if not mere seconds. Recently this stopped working, in that if kernel-desktop is installed and locked, kernel-default will be installed. If kernel-default is also locked, kernel-debug will be installed. If kernel-debug is also locked, kernel-pae will be installed. If kernel-pae is also locked, kernel-vanilla will be installed.
Is this new behavior intentional?
zypper al 'kernel*' should help.
Nevertheless, the behaviour sounds strange - please open a bugreport. (Attaching the zypper logs and maybe also a solver testcase would be helpful.)
I was able to reproduce again, but I employed downloadonly to avoid installing any unwanted kernels. On a hunch, after the download brought a kernel-debug package, I deleted it from the cache, and repeated, upon which it downloaded it again. Then I removed the microcode_ctl package that I had noted was being removed during previous dups. When I repeated again, no additional kernel got downloaded. So, I wonder if a bug is worth filing anyway? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 09 Sep 2013 22:22:21 -0400 Felix Miata <mrmazda@earthlink.net> wrote:
So, I wonder if a bug is worth filing anyway?
It is. If something pulls in unwanted kernels, it should be checked by zypper and kernel guys. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-09-10 22:55 (GMT-0500) Rajko composed:
On Mon, 09 Sep 2013 22:22:21 -0400 Felix Miata wrote:
So, I wonder if a bug is worth filing anyway?
It is.
If something pulls in unwanted kernels, it should be checked by zypper and kernel guys.
Pulls, yes, but I don't think on a fresh system attempting to recreate it would happen. Since every dup was removing microcode_ctl, it seems microcode_ctl would be an obsolete package that wouldn't be present on a fresh installation to be removed or to cause any previously uninstalled kernel variant to be installed alongside the existing kernel. No microcode_ctl is on factory or factory-snapshot mirrors any more. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Carlos E. R. -
Christian Boltz -
Felix Miata -
Rajko