On Wednesday, 25 June 2014 at 11:28, Ralf Corsepius wrote: > On 06/23/2014 07:27 PM, Bruno Wolff III wrote: > >On Mon, Jun 23, 2014 at 12:44:31 -0400, > > Matthias Clasen <mclasen@xxxxxxxxxx> wrote: > >> > >>I would suggest that the fix for this is to not push broken kernels so > >>frequently that 'the oldest one is the only that works' becomes an > >>issue, and to introduce automatic testing that ensures you can at least > >>boot rawhide to the login screen, _before_ a build gets pushed out to > >>the masses. > > > >While this usually isn't a problem for the updates repo (though there > >have been times where kernels were not usable by me for several months > >even in the released branches), it's not so nice for rawhide (possibly > >plus the rawhide nodebug repo) where there can be new kernels pushed to > >rawhide each day (and more than one if you're testing things from koji). > > > >For example right now I need to use a 3.15 kernel on one of my machines > >because of an issue affecting md raid and the running kernel is the > >oldest and only working kernel installed on that machine. > I am also running the latest 3.15 on one of my (f20) machines, because > apparently x11/kernel interaction is broken for me with all 3.16 kernels > (Intel HD Graphics 4600 GPU), FWIW I had to stay on 3.11.10 until 3.14 came along, because 3.12 and 3.13 would not boot or come out of suspend randomly. So yes, there's a very good case for keeping the running kernel even if it's the oldest one installed. Regards, -- Fedora http://fedoraproject.org/wiki/User:Rathann RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu "Faith manages." -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations" -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
