On Fri, 2010-02-19 at 08:29 -0500, James Laska wrote:
Adding no frozen rawhide expert, jkeating to the cc list for
guidance
below.
Sorry for missing this, my email has been a mess since things started
rolling with NFR
On Fri, 2010-02-19 at 06:38 -0500, Kamil Paral wrote:
> ----- "James Laska" <jlaska(a)redhat.com> wrote:
>
> > ---
> > hooks/post-koji-build/watch-koji-builds.py | 2 ++
> > lib/python/koji_utils.py | 2 ++
> > repoinfo.conf | 17 ++++++++++++++++-
> > 3 files changed, 20 insertions(+), 1 deletions(-)
> >
> > diff --git a/hooks/post-koji-build/watch-koji-builds.py
> > b/hooks/post-koji-build/watch-koji-builds.py
> > index d1b1707..2dcfc6d 100755
> > --- a/hooks/post-koji-build/watch-koji-builds.py
> > +++ b/hooks/post-koji-build/watch-koji-builds.py
> > @@ -35,6 +35,8 @@ kojiserver =
> > 'http://koji.fedoraproject.org/kojihub'
> > taglist = set(('dist-f10-updates-candidate',
> > 'dist-f11-updates-candidate',
> > 'dist-f12-updates-candidate',
> > + 'dist-f13-updates-candidate',
> > + 'dist-f14-updates-candidate',
>
> Why do we want to have dist-f14 specified now? It will be equal to
> rawhide for next 6 months and no builds should be tagged like
> that (rawhide does not use updates repo).
I *think* (but not sure so I cc'd jkeating) it's as you state above.
All rawhide builds until Fedora 13 is released are tagged as
dist-f14-$something.
Jesse ... can you help clear this up?
That's right, dist-f14-updates-candidate will be unused until we branch
for F-14. I just pre-created the tags to save time later. There should
not be a need to watch it over dist-rawhide until we branch for F14.
> Even if somebody tags it
> like that, we don't want to test it, right?
Good question. Is probably a policy decision we need to discuss at some
future date? Where we'll decide what tests are performed against
rawhide package updates. My first thought is we'd perform all the same
tests we do against pending and stable releases, but perhaps all results
would be advisory?
My personal goal here is to put AutoQA package acceptance in front of
every public package repo. Therefor if a build does not pass package
acceptance, it wouldn't go into rawhide, it wouldn't go into
updates-testing, etc... What level of tests goes into 'package
acceptance' is debatable, and there should be a maintainer accessible
'override' to force the issue.
> > ))
> > archlist = ('i686', 'x86_64', 'noarch')
> >
> > diff --git a/lib/python/koji_utils.py b/lib/python/koji_utils.py
> > index e7c3d26..c9fad5d 100644
> > --- a/lib/python/koji_utils.py
> > +++ b/lib/python/koji_utils.py
> > @@ -25,6 +25,8 @@ from repoinfo import repoinfo
> > import rpmUtils.miscutils
> >
> > parents_for_tag = {
> > + 'dist-f14-updates-candidate':
> > ('f14','f14-updates','f14-updates-testing'),
>
> The same question as above.
I was being lazy here and changing the values ahead of time thinking
that would save an extra commit in the future. But we'll wait to hear
back from Jesse in case this has any adverse effects.
I don't know that it will. Nothing should be tagged with those
specifically they will only pick up inherited builds. So if you're
watching for tag actions, you'll catch them all at dist-rawhide.
> > + 'dist-f13-updates-candidate':
> > ('f13','f13-updates','f13-updates-testing'),
> > 'dist-f12-updates-candidate':
> > ('f12','f12-updates','f12-updates-testing'),
> > 'dist-f11-updates-candidate':
> > ('f11','f11-updates','f11-updates-testing'),
> > 'dist-f10-updates-candidate':
> > ('f10','f10-updates','f10-updates-testing'),
> > diff --git a/repoinfo.conf b/repoinfo.conf
> > index f358dc5..0b66c1c 100644
> > --- a/repoinfo.conf
> > +++ b/repoinfo.conf
> > @@ -3,7 +3,7 @@ parents =
> > arches = i386, x86_64, ppc
> > # tag defaults to dist-[section_name]
> > tag = dist-%(__name__)s
> > -baseurl =
http://gromit.redhat.com/pub/fedora/linux
> > +baseurl =
http://download.fedoraproject.org/pub/fedora/linux
> > goldurl = %(baseurl)s/releases/%(path)s/Everything/%(arch)s/os
>
> I would love if anyone could tell me what the Everything path
> is good for. The only difference I found for F12 is that it
> contains also ppc64 architecture.
> This is not really related to the patch, just something I've
> found I don't understand.
My understanding in the differences between the Everything/ and Fedora/
paths is that Fedora/ is for static installation content, and
Everything/ dynamic repodata. The other differences are probably
documented on the wiki somewhere, but I can't find them after some quick
searching.
You're both wrong (:
Fedora/ is the limited subset of packages that is on the DVD/split
media, and it's where the install images live.
Everything/ is the entire package set, and is the path used with yum.
It also has the debuginfo repos too.
Both are static from release point on.
> > updatesurl = %(baseurl)s/updates/%(path)s/%(arch)s
> > rawhideurl = %(baseurl)s/%(path)s/%(arch)s/os
> > @@ -13,6 +13,21 @@ arches = i386, x86_64
> > path = development
>
> This should be also changed, to 'development/rawhide' I believe.
> (It's the [rawhide] section, but the top line is cut off).
Oh, good catch. Fixed in my local commit.
> > url = %(rawhideurl)s
> >
> > +[f13]
> > +# path will change when Fedora 13 is released
> > +path = development/13
> > +url = %(rawhideurl)s
> > +
> > +[f13-updates]
> > +path = 13
> > +url = %(updatesurl)s
> > +parents = f13
> > +
> > +[f13-updates-testing]
> > +path = testing/13
> > +url = %(updatesurl)s
> > +parents = f13-updates, f13
> > +
> > [f12]
> > path = 12
> > url = %(goldurl)s
> > --
> > 1.6.6
> >
>
> Otherwise it looks good from my point of view.
I. Thanks for the feedback. I've updated my local patch, but will
hold pushing until Jesse has a change to respond.
James
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca:
http://identi.ca/jkeating