Glad to hear :)
I'd recommend transitioning things to Python 2.6 when you can, as 1.7 won't
support Python 2.4.
Christian
On Mar 8, 2012, at 4:46, Sam wrote:
> Okay. Just figured it out. For some reason, my easy_install was installing
> things into the python2.6 dir when it should be insta
Okay. Just figured it out. For some reason, my easy_install was installing
things into the python2.6 dir when it should be installing to python2.4
since django and wsgi are both running on 2.4.
After I reinstalled setuptools and re-did the update for ReviewBoard,
things went back to normal and n
I also checked __init__.py and the VERSION = (1, 6, 4, 1, 'final', 0, True)
So I'm not sure how the mismatch message is saying that I'm currently
running 1.6.1
On Thursday, March 8, 2012 5:18:31 PM UTC+8, Sam wrote:
>
> Just upgraded by following the instructions in the documentation. Now
> whe
Here is the output when I run rb-site upgrade:
# rb-site upgrade /home/reviewboard
Rebuilding directory structure
Updating database. This may take a while.
Creating tables ...
Installing custom SQL ...
Installing indexes ...
No fixtures found.
/usr/lib/python2.6/site-packages/pycrypto-2.5-py2.6-l
Ya. I restarted memcached and apache.
Regarding the python mismatch. I'm not sure why when I installed RB 1.6.1
it was in /usr/lib/python2.4/site-packages/ReviewBoard-1.6.1-py2.4.egg
But after the upgrade, it defaulted to install
in /usr/lib/python2.6/site-packages/ReviewBoard-1.6.4.1-py2.6.egg
Hi Sam,
The versions of Python absolutely must match. Installing something into one
version and trying to use another is almost like installing something on
one computer and trying to run it from a separate one.
Have you tried reloading Apache after upgrading the site?
Christian
--
Christian H