Rawhide boot problems

Kevin Fenzi kevin at scrye.com
Tue Sep 11 15:52:05 UTC 2012

On Mon, 10 Sep 2012 15:29:36 -0700
Adam Williamson <awilliam at redhat.com> wrote:

> On 2012-09-10 15:22, Lennart Poettering wrote:
> > On Mon, 10.09.12 15:14, Adam Williamson (awilliam at redhat.com) wrote:

> > What I am proposing is to get rid of the "master" branch, so that 
> > people
> > can just branch off F-19 as early and as late as they want, and
> > they do
> > it from F-18 on their own. The mass branching would go away this
> > way, (might only be a side-effect of distro-wide rebuilds).
> >
> > This way, Lennart would just maintain systemd in the F-18 branch.
> > And then in a month or two he would branch F-19 off this branch.
> > And then when he is ready to open F-20 he would branch it off F-19.
> > And so on. But the time where Lennart decides to branch off is up
> > to him.
> >
> > In your example above the boost maintainer otoh could branch off
> > F-19 much earlier than Lennart branches off systemd. Both packagers
> > would have full flexibility when to branch off.
> >
> > This would give packagers much more flexibility about branching and
> > would also simplify our model as the master branch would just go
> > away... One branch less that can be confused is a win for
> > everybody.
> I don't see a problem with that, but then I'm just the monkey :)

So, the biggest problem is that in the past, FESCo has said that
rawhide should never "go back" in versions. If we change the
inheritance to pull from say f18-updates-testing, it means if an update
was pulled it also would 'disappear' from rawhide the next day. 

If I was wanting a f19 branch for my big library build and I needed to
build a new systemd version, could I branch it? or that would only be
up to you? (ie, would it be any package maintainer, or just people with
acls to the package). How do we tell pkgdb that there is a new branch?
Currently it's done at mass branch time, but in this model there would
have to be some way for maintainer/brancher to tell it. 

There's a lot of assumption in the tools that there is a master branch
pointing to rawhide at all times. I'm not sure how much work that would
be to change. 

Anyhow, I don't hate the idea, but I think there would probibly be a
lot more work in setting it up that people suspect. ;) 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120911/9ab1bfd9/attachment-0001.sig>

More information about the devel mailing list