Rawhide boot problems
kevin at scrye.com
Fri Sep 7 17:00:07 UTC 2012
On Fri, 7 Sep 2012 11:51:57 -0500
Bruno Wolff III <bruno at wolff.to> wrote:
> I actually wish people would stop doing updates just for branched and
> not doing new rawhide builds. This is especially bad during freezes
> (and the current one has been very long), as rawhide doesn't inherit
> from updates-testing, so you don't automagicly get fixes. For now I
> have enabled updates-testing for 18 in addition to rawhide for my
> rawhide machine, in order to get a lot of the gnome related stuff.
> I think our policy is that you should do rawhide builds, but at least
> some significant groups of packagers actively don't do rawhide
> builds. If that is going to continue, we should consider having
> rawhide inherit from updates-testing.
I'd like to propose the opposite:
Lets drop any inheritance between branched and rawhide.
Is it really that much trouble to commit/build in rawhide first? Thats
where you should be doing your development anyhow. Then, only if all
looks well, should you push to branched.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: not available
More information about the devel