[opensuse-kernel] master at 2.6.33-rc5
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - This is just a quick heads up that I've just pulled my 2.6.33 branch into master and pushed to the main repository. It should appear on gitorious, OBS, and KOTD shortly. Please note that I don't intend to push this for openSUSE 11.3 M1 since it's received only minimal testing so far and I'd like to let it settle a bit before committing it to a prerelease. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAktfczsACgkQLPWxlyuTD7ItjwCfeyOAvMEUzre4ZE9QFdg3nzEt NEwAnArD35pxOKdUISnis/3Zyh1yv7/n =9t8Y -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Jan 26, 2010 at 05:56:59PM -0500, Jeff Mahoney wrote:
Hi all -
This is just a quick heads up that I've just pulled my 2.6.33 branch into master and pushed to the main repository. It should appear on gitorious, OBS, and KOTD shortly.
Very cool, thanks so much for doing this work. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, 26 Jan 2010 17:56:59 -0500 Jeff Mahoney <jeffm@suse.com> wrote:
This is just a quick heads up that I've just pulled my 2.6.33 branch into master and pushed to the main repository. It should appear on gitorious, OBS, and KOTD shortly.
Please note that I don't intend to push this for openSUSE 11.3 M1 since
why not?
it's received only minimal testing so far and I'd like to let it settle a bit before committing it to a prerelease.
But using a 2 months old kernel, where we are sure that it will never be in any product, is also not really useful, is it? Is there some documentation on how to use KOTD with factory? I'm not really pleased with the outdated stuff that's in factory all the time. OTOH, i'm still a bit scared of only having the KOTD, so is there a method to do "zypper up" and get both kernels, the FACTORY "stable" kernel and the KOTD? (OT: Not that other subsystems than kernel are doing any better - QT4 is also outdated so that reporting bugs upstream KDE4 is "embarassing" at least) -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Am Mittwoch 27 Januar 2010 schrieb Stefan Seyfried:
On Tue, 26 Jan 2010 17:56:59 -0500
Jeff Mahoney <jeffm@suse.com> wrote:
This is just a quick heads up that I've just pulled my 2.6.33 branch into master and pushed to the main repository. It should appear on gitorious, OBS, and KOTD shortly.
Please note that I don't intend to push this for openSUSE 11.3 M1 since
why not? Most likely because Milestone1 is on the mirrors since yesterday.
Greetings, Stephan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/27/2010 03:42 AM, Stephan Kulow wrote:
Am Mittwoch 27 Januar 2010 schrieb Stefan Seyfried:
On Tue, 26 Jan 2010 17:56:59 -0500
Jeff Mahoney <jeffm@suse.com> wrote:
This is just a quick heads up that I've just pulled my 2.6.33 branch into master and pushed to the main repository. It should appear on gitorious, OBS, and KOTD shortly.
Please note that I don't intend to push this for openSUSE 11.3 M1 since
why not? Most likely because Milestone1 is on the mirrors since yesterday.
Even if it wasn't, I didn't really want to push a mostly untested kernel out for M1. There are a whole lot more things our users need to test than just the kernel. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAktgT60ACgkQLPWxlyuTD7JWIACcDevj+txshfE8Kd0wRGXMCIM4 8fIAn2ROxtVkiIaOVbRdHxCVc7E2AQiC =Gb7Z -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wednesday 27 January 2010, 09:28:13 Stefan Seyfried wrote:
OTOH, i'm still a bit scared of only having the KOTD, so is there a method to do "zypper up" and get both kernels, the FACTORY "stable" kernel and the KOTD?
Last time, I complained about this (it was in bugzilla, IIRC), I was told, that this is the intended behavior. openSUSE's policy is: you have to use a single kernel version, because neither zypper, nor rpmbuilding kernel modules can cope with it. I think, this this is a poor argument, but I'm not getting asked anyway... Notice, how this is different from distributions managed by yum: that has explicit handling to always _install_ new kernels. I can imagine a lot of scenarios, where this policy is superior. Pete -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Feb 02, 2010 at 04:51:35PM +0100, Hans-Peter Jansen wrote:
On Wednesday 27 January 2010, 09:28:13 Stefan Seyfried wrote:
OTOH, i'm still a bit scared of only having the KOTD, so is there a method to do "zypper up" and get both kernels, the FACTORY "stable" kernel and the KOTD?
Last time, I complained about this (it was in bugzilla, IIRC), I was told, that this is the intended behavior.
openSUSE's policy is: you have to use a single kernel version, because neither zypper, nor rpmbuilding kernel modules can cope with it. I think, this this is a poor argument, but I'm not getting asked anyway...
Notice, how this is different from distributions managed by yum: that has explicit handling to always _install_ new kernels.
I can imagine a lot of scenarios, where this policy is superior.
The zypp multiversion handling at least allows multiple kernels being installed. See /etc/zypp/zypp.conf So updateing will keep the old (known good) kernels. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, 2 Feb 2010 16:59:21 +0100 Marcus Meissner <meissner@suse.de> wrote:
The zypp multiversion handling at least allows multiple kernels being installed. See /etc/zypp/zypp.conf
So updateing will keep the old (known good) kernels.
Just to make sure ;) uncommenting this line in zypp.conf # multiversion = provides:multiversion(kernel) will do what I want? I can add the KOTD repo, and zypper up will install both: the newest FACTORY kernel (if there will ever be an update for the FACTORY kernel, I slowly don't believe in it anymore ;) and the newest KOTD? ...and of course, old kernels will accumulate until the disk is full, but that's fine, I can purge them manually. Did I understand that correctly? Thanks! seife -- Stefan Seyfried "Mit Außerirdischen, die nicht weiter gekommen sind als Microsoft und Apple, will ich persönlich nichts zu tun haben." -- Prof. Harald Lesch -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 02/02/2010 12:30 PM, Stefan Seyfried wrote:
On Tue, 2 Feb 2010 16:59:21 +0100 Marcus Meissner <meissner@suse.de> wrote:
The zypp multiversion handling at least allows multiple kernels being installed. See /etc/zypp/zypp.conf
So updateing will keep the old (known good) kernels.
Just to make sure ;)
uncommenting this line in zypp.conf
# multiversion = provides:multiversion(kernel)
will do what I want? I can add the KOTD repo, and zypper up will install both: the newest FACTORY kernel (if there will ever be an update for the FACTORY kernel, I slowly don't believe in it anymore ;) and the newest KOTD?
...and of course, old kernels will accumulate until the disk is full, but that's fine, I can purge them manually.
Did I understand that correctly?
Well if factory is really the bleeding edge, it would be pretty easy to issue a SR automatically from the Kernel:HEAD project when all packages are building. -Jeff -- Jeff Mahoney SUSE Labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tuesday 02 February 2010, Stefan Seyfried wrote:
uncommenting this line in zypp.conf
# multiversion = provides:multiversion(kernel)
will do what I want?
it will do what is implemented: - every package providing "multiversion(kernel)" will be rpm -i instead of rpm -U. by default this is kernel-* as they're provided by openSUSE:*. Note that this has side effects that are undesireable: kmp's won't get updated anymore to match the newest installed kernel, because there is one kernel (the old one) satisfying the dependencies. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 3.2.2010 00:10, Dirk Müller wrote:
On Tuesday 02 February 2010, Stefan Seyfried wrote:
uncommenting this line in zypp.conf
# multiversion = provides:multiversion(kernel)
will do what I want?
it will do what is implemented:
- every package providing "multiversion(kernel)" will be rpm -i instead of rpm -U.
by default this is kernel-* as they're provided by openSUSE:*.
plus all KMPs.
Note that this has side effects that are undesireable: kmp's won't get updated anymore to match the newest installed kernel, because there is one kernel (the old one) satisfying the dependencies.
If there are new KMPs available, they should be updated as well. The problem arises if some KMP is not (yet) available for the new kernel, you won't notice this because of the old kernel providing the dependencies. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wed, 3 Feb 2010 00:10:04 +0100 Dirk Müller <dmueller@suse.de> wrote:
On Tuesday 02 February 2010, Stefan Seyfried wrote:
uncommenting this line in zypp.conf
# multiversion = provides:multiversion(kernel)
will do what I want?
it will do what is implemented:
It probabyl does, but...
- every package providing "multiversion(kernel)" will be rpm -i instead of rpm -U.
by default this is kernel-* as they're provided by openSUSE:*.
Note that this has side effects that are undesireable: kmp's won't get updated anymore to match the newest installed kernel, because there is one kernel (the old one) satisfying the dependencies.
..."zypper up" will now never install a new kernel: strolchi:~ # zypper search -s kernel-default Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------------------------------+------------+-----------------+--------+------------------ i | kernel-default | package | 2.6.33-2.1 | i586 | factory-oss v | kernel-default | package | 2.6.33-rc7.14.1 | i586 | KOTD i | kernel-default | package | 2.6.33-rc6.12.1 | i586 | (System Packages) | kernel-default | srcpackage | 2.6.33-rc7.14.1 | noarch | KOTD | kernel-default-base | package | 2.6.33-2.1 | i586 | factory-oss [...snip more uninstalled packages, I really only have 2x kernel-default...] strolchi:~ # zypper up kernel-default Loading repository data... Reading installed packages... No update candidate for 'kernel-default'. Resolving package dependencies... Nothing to do. "zypper in kernel-default" will also say "Nothing to do", the only way to get a new kernel now seems to be "zypper in kernel-default-2.6.33-rc7.14.1" (zypper {in,up} -r KOTD kernel-default also does not do what I'd expect it to) That's not a serious problem, just something to be aware of. -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (8)
-
Dirk Müller -
Greg KH -
Hans-Peter Jansen -
Jeff Mahoney -
Marcus Meissner -
Michal Marek -
Stefan Seyfried -
Stephan Kulow