On Thu, 2011-06-02 at 09:53 -0400, James Laska wrote: > While updating the Fedora autotest package to the latest code, it seems that > the TestPlanner front-end does not successfully compile. I believe it may > still be a work in progress, so I've disabled including it in the Django > settings.py.
Ok James, I've looked into this, and here are my thoughts: 1) I tested the patches using clean setups, and I've got planner to compile, so I believe your glitch might be just a packaging glitch 2) We can turn the availability of the code using a config knob. However, first we need to figure out whether we will keep the planner front end in the autotest tree at all. So I'm deferring this for upstream, please carry those patches on your rpm for a little longer. Cheers, Lucas > Signed-off-by: James Laska <[email protected]> > --- > frontend/settings.py | 3 ++- > 1 files changed, 2 insertions(+), 1 deletions(-) > > diff --git a/frontend/settings.py b/frontend/settings.py > index 3ac7f80..f4a3e31 100644 > --- a/frontend/settings.py > +++ b/frontend/settings.py > @@ -109,7 +109,8 @@ TEMPLATE_DIRS = ( > INSTALLED_APPS = ( > 'frontend.afe', > 'frontend.tko', > - 'frontend.planner', > +# planner disabled until complete > +# 'frontend.planner', > 'django.contrib.admin', > 'django.contrib.auth', > 'django.contrib.contenttypes', _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
