I didn't run upgrade on it yet - I just wanted to see if I could
access the site to make sure my config settings were right.  Here's
what I see when I run the commands below:

>>> from reviewboard.accounts import backends
>>> print backends.__file__
/usr/lib/python2.4/site-packages/ReviewBoard-1.6-py2.4.egg/reviewboard/
accounts/backends.py
>>> print backends.get_registered_auth_backends
Traceback (most recent call last):
  File "<console>", line 1, in ?
AttributeError: 'module' object has no attribute
'get_registered_auth_backends'
>>> print backends.get_registered_auth_backends
Traceback (most recent call last):
  File "<console>", line 1, in ?
AttributeError: 'module' object has no attribute
'get_registered_auth_backends'


Since you said 'so long as you did rb-site upgrade', I gave that a try
next and got:

$ rb-site upgrade /var/www/reviewboard
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/
__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated;
use settings.DATABASES instead.
  DeprecationWarning
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/
__init__.py:60: DeprecationWarning: Short names for ENGINE in database
configurations are deprecated. Prepend default.ENGINE with
'django.db.backends.'
  DeprecationWarning
Rebuilding directory structure
Upgrading site settings_local.py
Updating database. This may take a while.

[!] Unable to execute the manager command syncdb: cannot import name
    get_registered_auth_backends
Registering new SCM Tool Plastic SCM
(reviewboard.scmtools.plastic.PlasticTool) in database
Traceback (most recent call last):
  File "/usr/bin/rb-site", line 7, in ?
    sys.exit(
  File "/usr/lib/python2.4/site-packages/ReviewBoard-1.6-py2.4.egg/
reviewboard/cmdline/rbsite.py", line 1747, in main
    command.run()
  File "/usr/lib/python2.4/site-packages/ReviewBoard-1.6-py2.4.egg/
reviewboard/cmdline/rbsite.py", line 1645, in run
    site.migrate_database()
  File "/usr/lib/python2.4/site-packages/ReviewBoard-1.6-py2.4.egg/
reviewboard/cmdline/rbsite.py", line 353, in migrate_database
    self.run_manage_command("evolve", ["--noinput", "--execute"])
  File "/usr/lib/python2.4/site-packages/ReviewBoard-1.6-py2.4.egg/
reviewboard/cmdline/rbsite.py", line 472, in run_manage_command
    execute_manager(reviewboard.settings, [__file__, cmd] + params)
  File "/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/
core/management/__init__.py", line 438, in execute_manager
    utility.execute()
  File "/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/
core/management/__init__.py", line 379, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/
core/management/base.py", line 191, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/
core/management/base.py", line 220, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.4/site-packages/django_evolution-0.6.5-
py2.4.egg/django_evolution/management/commands/evolve.py", line 60, in
handle
    self.evolve(*app_labels, **options)
  File "/usr/lib/python2.4/site-packages/django_evolution-0.6.5-
py2.4.egg/django_evolution/management/commands/evolve.py", line 140,
in evolve
    database))
  File "/usr/lib/python2.4/site-packages/django_evolution-0.6.5-
py2.4.egg/django_evolution/mutations.py", line 418, in mutate
    return self.add_column(app_label, proj_sig, database)
  File "/usr/lib/python2.4/site-packages/django_evolution-0.6.5-
py2.4.egg/django_evolution/mutations.py", line 426, in add_column
    self.field_attrs, model)
  File "/usr/lib/python2.4/site-packages/django_evolution-0.6.5-
py2.4.egg/django_evolution/mutations.py", line 33, in create_field
    related_model_sig = proj_sig[related_app_name][related_model_name]
KeyError: 'site'

I notice 'upgrade' ported my settings_local.py file, so skipping that
step was definitely not a good idea.  It appears I've made quite a
mess of things!  I have a backup of my site-packages from before I ran
easy_install ReviewBoard so if need by, I can start over.


On Sep 9, 2:04 pm, Christian Hammond <chip...@chipx86.com> wrote:
> Untarring the site should be fine, so long as you did a 'rb-site upgrade' on
> it.
>
> This is strange. It's definitely using RB 1.6, but somehow it's failing to
> import that function. This certainly seems like an issue local to your
> setup, so we'll need to tack it down. Run the shell again and do:
>
>     from reviewboard.accounts import backends
>     print backends.__file__
>     print backends.get_registered_auth_backends
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
> On Fri, Sep 9, 2011 at 12:27 PM, Steve <seide.al...@gmail.com> wrote:
> > Your use of the word installed suggest where I may have gone wrong.  I
> > have RB 1.0.9  installed on another machine in production.  The goal
> > here was to migrate that over to this machine.  So I never  ran rb-
> > site install, I just installed all the software and then untar'ed the
> > old site in place.  Maybe that's the source of my problem.
>
> > Here's the output of the commands you gave me:
>
> > $ rb-site manage /var/www/reviewboard shell
> > /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/
> > __init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated;
> > use settings.DATABASES instead.
> >  DeprecationWarning
> > /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/
> > __init__.py:60: DeprecationWarning: Short names for ENGINE in database
> > configurations are deprecated. Prepend default.ENGINE with
> > 'django.db.backends.'
> >  DeprecationWarning
> > Python 2.4.3 (#1, May  5 2011, 16:39:10)
> > [GCC 4.1.2 20080704 (Red Hat 4.1.2-50)] on linux2
> > Type "help", "copyright", "credits" or "license" for more information.
> > (InteractiveConsole)
> > >>> import reviewboard
> > >>> print reviewboard.VERSION
> > (1, 6, 0, 0, 'final', 0, True)
> > >>> from reviewboard.admin.middleware import get_registered_auth_backends
> > Traceback (most recent call last):
> >   File "<console>", line 1, in ?
> >  File "/usr/lib/python2.4/site-packages/ReviewBoard-1.6-py2.4.egg/
> > reviewboard/admin/middleware.py", line 21, in ?
> >    from reviewboard.admin.siteconfig import load_site_config
> >  File "/usr/lib/python2.4/site-packages/ReviewBoard-1.6-py2.4.egg/
> > reviewboard/admin/siteconfig.py", line 43, in ?
> >    from reviewboard.accounts.backends import
> > get_registered_auth_backends
> > ImportError: cannot import name get_registered_auth_backends
>
> > --Steve
>
> > On Sep 9, 11:11 am, Christian Hammond <chip...@chipx86.com> wrote:
> > > This sounds like Review Board may not have been properly installed.
>
> > > Try running: rb-site manage /path/to/site shell
>
> > > And then:
>
> > >     import reviewboard
> > >     print reviewboard.VERSION
> > >     from reviewboard.admin.middleware import get_registered_auth_backends
>
> > > And paste the results
>
> > > Christian
>
> > > --
> > > Christian Hammond - chip...@chipx86.com
> > > Review Board -http://www.reviewboard.org
> > > VMware, Inc. -http://www.vmware.com
>
> > > On Fri, Sep 9, 2011 at 8:27 AM, Steve <seide.al...@gmail.com> wrote:
> > > > I have a new CentOS 5.6 box on which I've installed RB 1.6.  When I
> > > > try to access the site for the first time, I get this error:
>
> > > > Mod_python error: "PythonHandler django.core.handlers.modpython"
>
> > > > Traceback (most recent call last):
>
> > > >  File "/usr/lib64/python2.4/site-packages/mod_python/apache.py", line
> > > > 299, in HandlerDispatch
> > > >    result = object(req)
>
> > > >  File "/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/
> > > > core/handlers/modpython.py", line 213, in handler
> > > >    return ModPythonHandler()(req)
>
> > > >  File "/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/
> > > > core/handlers/modpython.py", line 174, in __call__
> > > >    self.load_middleware()
>
> > > >  File "/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/
> > > > core/handlers/base.py", line 47, in load_middleware
> > > >    raise exceptions.ImproperlyConfigured('Error importing middleware
> > > > %s: "%s"' % (mw_module, e))
>
> > > > ImproperlyConfigured: Error importing middleware
> > > > reviewboard.admin.middleware: "cannot import name
> > > > get_registered_auth_backends"
>
> > > > My current configuration is:
>
> > > > - Python 2.4.3
> > > > - MySQL 5.0.77
> > > > - Apache 2
> > > > - mod_python-3.2.8-3.1.x86_64
> > > > - patch 2.5.4
> > > > - python-devel-2.4.3-44.el5
> > > > - MySQL-python-1.2.1-1.x86_64 base, then upgraded to
> > > > MySQL_python-1.2.3
>
> > > > Do I need a newer mod_python?  If not, can someone suggest what is
> > > > ImproperlyConfigured?
>
> > > > Thanks!
>
> > > > -- Steve
>
> > > > --
> > > > Want to help the Review Board project? Donate today at
> > > >http://www.reviewboard.org/donate/
> > > > Happy user? Let us know athttp://www.reviewboard.org/users/
> > > > -~----------~----~----~----~------~----~------~--~---
> > > > To unsubscribe from this group, send email to
> > > > reviewboard+unsubscr...@googlegroups.com
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/reviewboard?hl=en
>
> > --
> > Want to help the Review Board project? Donate today at
> >http://www.reviewboard.org/donate/
> > Happy user? Let us know athttp://www.reviewboard.org/users/
> > -~----------~----~----~----~------~----~------~--~---
> > To unsubscribe from this group, send email to
> > reviewboard+unsubscr...@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/reviewboard?hl=en

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to