Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
On Sun, Jan 8, 2012 at 11:08 PM, Bruno Wolff III br...@wolff.to wrote: It might make some sense to have a separate repo for the lastest kernels on released versions of Fedora. Maybe one than one, since some people may be willing to test RCs and other people just want to get a jump on trying the latest released kernel. I don't see how that repo can't be rawhide. A vast majority of the time, the rawhide kernel can be installed on the previous release without any userspace updates (the 3.0 transition was a notable exception). We already build all the RCs, and people that are likely to test in updates-testing are probably capable of grabbing it from rawhide anyway. If there's a concern over the debug options in the rawhide kernel being enabled (which would be ironic, considering we're talking about getting advanced testing and debug), the kernel team is going to build one kernel per release/RC without those on. We've done that with the initial 3.2 kernel build. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
On 01/09/2012 07:24 AM, Josh Boyer wrote: a concern over the debug opt Alternatively - just build it without debugging - download the source rpm(s). After installing/setting up the rpm tools, unpack (rpm -iv) the source rpm in ~/rpmbuild/SRPMS dir - then go to ~/rpmbuild/SPEC and do: rpmbuild -bb --without debug --without debuginfo --target=$(uname -m) kernel.spec gene -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
On 01/09/2012 09:38 AM, Genes MailLists wrote: On 01/09/2012 07:24 AM, Josh Boyer wrote: a concern over the debug opt Alternatively - just build it without debugging - download the source rpm(s). ... Of course (should go without saying ... but) the obvious downside to the speed benefit, is the reduction of useful information if there is a problem - so it can be helpful to keep a debug kernel around. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
On Mon, Jan 09, 2012 at 07:24:48 -0500, Josh Boyer jwbo...@gmail.com wrote: If there's a concern over the debug options in the rawhide kernel being enabled (which would be ironic, considering we're talking about getting advanced testing and debug), the kernel team is going to build one kernel per release/RC without those on. We've done that with the initial 3.2 kernel build. I appreciate that. I can switch to a debug kernel if something comes up. But a lot of the time these kernels work well and the performance hit on my machines (they are pretty old) is too much for me to tolerate always running debug kernels. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
On Mon, 09 Jan 2012 08:57:26 +1100 Bojan Smojver bo...@rexursive.com wrote: Given this: https://plus.google.com/109995262342451767357/posts/FzpWWo4sRip Would it be possible to get a 3.2 build for F-16, so that we can start testing? The rawhide/F17 build works fine on f16 (at least as far as I can see). kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
On Sun, Jan 8, 2012 at 5:11 PM, Kevin Fenzi ke...@scrye.com wrote: On Mon, 09 Jan 2012 08:57:26 +1100 Bojan Smojver bo...@rexursive.com wrote: Given this: https://plus.google.com/109995262342451767357/posts/FzpWWo4sRip Would it be possible to get a 3.2 build for F-16, so that we can start testing? The rawhide/F17 build works fine on f16 (at least as far as I can see). Yep. For F15/F16, we'll likely wait for the 3.2.1 release before we rebase it. That should probably happen somewhere not long after FUDCon. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
On Mon, 2012-01-09 at 08:57 +1100, Bojan Smojver wrote: Would it be possible to get a 3.2 build for F-16, so that we can start testing? I'm going to reply to my own message here, to keep the thread, but it is really in reply to the other two messages, which I don't have in my mailbox right now and Gmane is down. I was thinking more along the lines of: - an official updates-testing build is more likely to reach more people (it is great that that Rawhide build works, but not many will try it like that) - a sufficiently high karma (say 500) will prevent the package from ever reaching stable (i.e. if we're really waiting for 3.2.1) and yet, bugs can be filed/fixed against it etc. -- Bojan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
On Mon, Jan 09, 2012 at 14:55:58 +1100, Bojan Smojver bo...@rexursive.com wrote: I was thinking more along the lines of: - an official updates-testing build is more likely to reach more people (it is great that that Rawhide build works, but not many will try it like that) You really can't do that the way things are now. That would block doing updates to the current (in updates) kernel that are needed. Some kernel developers put builds up on their fedorapeople pages to make these packers available. It might make some sense to have a separate repo for the lastest kernels on released versions of Fedora. Maybe one than one, since some people may be willing to test RCs and other people just want to get a jump on trying the latest released kernel. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Kernel 3.1 being phased out, time for 3.2 in F-16?
--- Original message --- From: Bruno Wolff III You really can't do that the way things are now. That would block doing updates to the current (in updates) kernel that are needed. Good point. Didn't think of that, to be honest. OK, never mind. Bad plan. -- Bojan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
