To upgrade using pip, just use the command in my previous email:
sudo pip install -U ReviewBoard
Christian
On Thu, Mar 2, 2017 at 18:48 Bill Hoo wrote:
> Hi Christian,
>
> Thank you for explain it, now we are clear what happend and already go
> back to RB2.5.7 with no
Hi Christian,
Thank you for explain it, now we are clear what happend and already go back
to RB2.5.7 with no pain.
Maybe this topic should be placed into FAQ page or a NOTE section in the
upgrade page, because some customers have the very same issue.
And I have on more question, when I'm
Hi Bill,
You're technically already on 2.5.7, and the database schema has not
changed. There is a way to force the database's stored version back to
2.5.7, but we should diagnose this first.
The ".dist-info" packages come from Python Wheel packages. These are
installed using pip. However, you
Hi Christian,
It's good to hear that's the problem. But I'm sure we always used the same
instruction to install/upgrade RB.
We are running Ubuntu Server 16.04 x64, and installed the RB 2.5.6
(followed by docs/manual/2.5/admin/installation/linux/
Hi Bill,
That does look to be the problem. The 2.5.7 version is taking precedence.
This indicates it wasn't installed the same way as 2.5.9. Did you install
via RPM? Pip?
If via RPM, you'll need to remove that version through rpm/yum first.
This is going to affect Djblets as well, so you'll
Christian,
Here's the contents of /usr/local/lib/python2.7/dist-packages/ directory,
celery-4.0.2-py2.7.egg
> cffi
> cffi-1.9.1.dist-info
> _cffi_backend.so
> concurrent
> cpplint-1.3.0-py2.7.egg
> Crypto
> cryptography
> cryptography-1.7.1.dist-info
> dateutil
> django
>
Thanks Christian,
I got your point and will check it again. BTW, RB 2.5.7 was installed
followed by the official instructions too.
We're out of office right now, I'll give you the contents tomorrow.
Regards,
Bill.
在 2017年3月1日星期三 UTC+8下午2:51:31,Christian Hammond写道:
>
> Hi Bill,
>
> Okay,
Hi Bill,
Okay, sounds like Python is fine then. It does still sound like it's
running the older version in Apache, though.
The important part is the part of the message saying "You are running 2.5.7
and the site was last upgraded to 2.5.9." The command line rb-site is
definitely using 2.5.9, but
I've checked the python version in our system, we have py2.7 and py3.5,
when I type "python" command in the console, its py2.7, and where I find
the "ReviewBoard-2.5.9-py2.7.egg" file is also in the py2.7's dist-packages
directory.
So I'm wondering its not a python's version mismatch error. Am
When I've seen this before, it was due to Apache running a different
version of Python than what was used to upgrade Review Board. For instance,
mod_wsgi might be using Python 2.6 while easy_install used Python 2.7, or
vice-versa. In this case, the wrong Review Board package is being used.
The
Here's the command we ran:
sudo rb-site upgrade /var/www/crisisgo_reviewboard
And the corresponding output:
Rebuilding directory structure
> Upgrading site settings_local.py
> Updating database. This may take a while.
>
> The log output below, including warnings and errors,
> can be ignored
Can you show me the exact rb-site command you ran and the exact output?
Thanks,
Christian
On Mon, Feb 27, 2017 at 22:18 Bill Hoo wrote:
> Hi Christian,
>
> We upgrade RB from 2.5.7 to 2.5.9, after we run:
>
> sudo easy_install -U ReviewBoard
>
> we get the following output:
Hi Christian,
We upgrade RB from 2.5.7 to 2.5.9, after we run:
sudo easy_install -U ReviewBoard
we get the following output:
Searching for ReviewBoard
> Reading https://pypi.python.org/simple/ReviewBoard/
> Downloading
>
Hi,
What happens when you run that command? What do you see?
Make sure you restart Apache after running it.
Christian
On Mon, Feb 27, 2017 at 21:03 Bill Hoo wrote:
> Hi there,
>
>
> We're upgrading RB from 2.5.7 to 2.5.9, but failed, we followed the
> official steps but
14 matches
Mail list logo