El mar, 21-02-2017 a las 01:56 +0100, Ralf Corsepius escribió: > On 02/21/2017 01:48 AM, Kevin Fenzi wrote: > > On Tue, 21 Feb 2017 00:14:56 +0000 > > "M. Edward (Ed) Borasky" <znmeb@xxxxxxxxx> wrote: > > ...snip... > > > > > > > > Rawhide as it currently exists can't stay solid enough for me > > > even > > > with just the few pieces I absolutely need. Tumbleweed, for all > > > it's > > > promise of "latest and greatest", is not supported by enough > > > third > > > parties to be useful even as just a host. And sid is, well, sid. > > > > I'm curious what issues you hit with Rawhide? Have any examples? > > Current rawhide (== Feb 15) does not match with what the builders > use. > => It's impossible to locally investigate runtime bugs > > Real world example: > https://bugzilla.redhat.com/show_bug.cgi?id=1425129 > Rawhide has been broken since the 15th, First due to nss, then rdma- core, followed by policycoreutils and setools breakages. it has taken a bunch of manual work to get it all figured out, cleaned up and composes kicked off, its exactly the types of breakages that I am trying to avoid by implementing the change. rawhide as it exists today will still exist i the buildsystem. Longer term I would like to extend things to do things like automatic rebuilds when we detect breakage. I am sure we are not going to get this perfect on day 1, but that over time we will improve and make it more and more useful. The goal is to make everyone life better. I have started looking at ways to make repos available for early testing and debugging problems in builds that have just been built for stable fedora's as well. We will have a repo of builds that have been built but not released. we will also be working to get notifications to developers quicker that a change they made, has broken things. Please do not assume that the reason why rawhide is currently a little stale is due to intentionally not pushing changes or holding anything back because it is not. It is entirely a matter of the type of breakage we want to avoid going forward, Dennis
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
