On Fri, Jan 31, 2014 at 12:30:17AM +0100, drago01 wrote: > On Thu, Jan 30, 2014 at 9:02 PM, Kevin Fenzi <[email protected]> wrote: > > On Thu, 30 Jan 2014 14:04:53 -0500 > > Josh Boyer <[email protected]> wrote: > > > >> On Thu, Jan 30, 2014 at 2:03 PM, poma <[email protected]> > >> wrote: > >> > On 30.01.2014 18:19, Peter Robinson wrote: > >> >> On Thu, Jan 30, 2014 at 5:12 PM, poma <[email protected]> > >> >> wrote: > >> >>> Who builds these kernels? > >> >>> Perhaps the better question is how can I actually find who builds > >> >>> these kernels? :) > >> >>> And if any exists, where is a git repo for these kernels? > >> >> > >> >> Generally it's jforbes. The config is basically the fedora kernel > >> >> git repo with the debug options disabled. > >> >> > >> >> Peter > >> >> > >> > > >> > So practically with the Rawhide "- Disable debugging options." > >> > stage, Rawhide & RawhideKernelNodebug are on the same path? > >> > >> Yes. > >> > >> Also, rawhide kernels from koji aren't signed either. Signing of RPMs > >> is only done late in the release process, and for updates to a stable > >> release. > > > > To clarify what Josh said: > > > > rawhide _rpms_ are not signed [...] > > Why?
Koji doesn't do auto-signing, people have suggested auto-signing isn't any better than not signing, the signing we do for releases is done in a manual fashion as a result, and the signing software is... fragile. I think that mostly sums it up. Basically the churn of rawhide and the lack of automation makes it infeasible to really do. josh _______________________________________________ kernel mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/kernel
