On Thu, 2010-07-01 at 09:04 -0400, Kamil Paral wrote:
----- "AutoQA" <trac(a)fedorahosted.org> wrote:
> #32: Add autotest rpm dependencies into fedora infrastructure repo
> -----------------------------+----------------------------------------------
> Reporter: jlaska | Owner: jkeating
>
> Type: task | Status: closed
>
> Priority: major | Milestone: Packaging, Review, &
> Deployment
> Component: infrastructure | Version: 1.0
>
> Resolution: invalid | Keywords:
>
> -----------------------------+----------------------------------------------
> Changes (by jlaska):
>
> * status: new => closed
> * resolution: => invalid
>
> Comment:
>
> Nothing to track in this ticket anymore. A package repository is
> available for those interested in testing. Instructions available
> at
>
https://fedoraproject.org/wiki/Install_and_configure_autotest and
>
https://fedoraproject.org/wiki/Install_and_configure_AutoQA
>
> All packages need to be packaged for Fedora, this is a requirement by
> the
> infrastructure team. Packaging of autoqa dependencies will be
> tracked in
> a different ticket for each package.
>
> --
> Ticket URL: <
https://fedorahosted.org/autoqa/ticket/32#comment:6>
> AutoQA <
http://autoqa.fedorahosted.org>
> Automated QA project
I'm not sure how this works. We instruct people to add infrastructure
repo [1], but when I have a look at that repo, there's nothing really
interesting there [2]. I think jlaska's autoqa repo [3] is completely
sufficient now, isn't it? Do we still need to instruct people to add
infrastructure repo?
Good point, I didn't pay close attention to whether the infrastructure
repository was used during my last autotest-server deployment. I've
removed that step from the wiki instructions.
Thanks,
James