subject:"Re\: Upgrade to ReviewBoard 2.5.9 failed."

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-03-02 Thread Christian Hammond

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 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 using pip + rb-site to upgrade RB,
> its downgrade to 2.5.7, but how can I upgrade to 2.5.9 by pip?
>
> Best regards,
> Bill.
>
> 在 2017年3月2日星期四 UTC+8下午6:45:03，Christian Hammond写道：
>
> 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 also have *.egg files, which are
> installed using easy_install. Wheels will take precedence over eggs.
>
> I suspect what happened was that Review Board was once installed via pip,
> and later you may have tried downgrading back to 2.5.7 using easy_install
> (due to the fact that Djblets and other dependencies do not have eggs for
> those versions, but rather have dist-info files).
>
> Pip is the recommended way to install Review Board, and upgrading using
> pip should resolve your issue, I believe. Try:
>
> sudo pip install -U ReviewBoard
>
> Christian
>
>
> --
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> On Wed, Mar 1, 2017 at 11:49 PM, Bill Hoo  wrote:
>
> 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/
> )
> at the very first place, and then upgraded to 2.5.7 (followed by
> upgrading/upgrading-reviewboard/
> ),
> and this time when we upgrade to 2.5.9, we still use the same way, but get
> this error.
>
> I'm wondering if there's any way to go back to 2.5.7 and keep our origin
> data?
>
> Thanks,
> Bill.
>
> 在 2017年3月2日星期四 UTC+8下午2:04:55，Christian Hammond写道：
>
> 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 need to take care of
> both of those packages. Potentially other packages going forward.
>
> Christian
>
> --
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> On Wed, Mar 1, 2017 at 8:42 PM, Bill Hoo  wrote:
>
> 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
> Django-1.6.11.dist-info
> django_evolution
> django_evolution-0.7.6.dist-info
> django_haystack-2.4.1.dist-info
> django_multiselectfield-0.1.4.dist-info
> django_pipeline-1.3.27.dist-info
> djblets
> Djblets-0.9.4.dist-info
> Djblets-0.9.6-py2.7.egg
> dns
> dnspython-1.15.0.dist-info
> docutils
> docutils-0.13.1.dist-info
> easy-install.pth
> easy_install.py
> easy_install.pyc
> enum
> enum34-1.1.6.dist-info
> feedparser-5.2.1.dist-info
> feedparser.py
> feedparser.pyc
> futures-3.0.5.dist-info
> haystack
> idna
> idna-2.2.dist-info
> ipaddress-1.0.17.dist-info
> ipaddress.py
> ipaddress.pyc
> markdown
> Markdown-2.4.1.dist-info
> memcache.py
> memcache.pyc
> mimeparse-0.1.3.dist-info
> mimeparse.py
> mimeparse.pyc
> multiselectfield
> MySQLdb
> _mysql_exceptions.py
> _mysql_exceptions.pyc
> MySQL_python-1.2.5.dist-info
> _mysql.so
> paramiko
> paramiko-2.1.1.dist-info
> pep8-1.7.0-py2.7.egg
> PIL
> Pillow-3.4.2.dist-info
> pillowfight-0.2.dist-info
> pip
> pip-9.0.1.dist-info
> pipeline
> pkg_resources
> publicsuffix
> publicsuffix-1.1.0.dist-info
> pyasn1
> pyasn1-0.1.9.dist-info
> pycparser
> pycparser-2.17.dist-info
> pycrypto-2.6.1.dist-info
> pyflakes-1.4.0-py2.7.egg
> pygments
> Pygments-2.1.3.dist-info
> python_dateutil-1.5.dist-info
> python_memcached-1.58.dist-info
> pytz
> pytz-2016.10.dist-info
> rbtools
> RBTools-0.7.9.dist-info
> recaptcha
> recaptcha_client-1.0.6.dist-info
> recaptcha_client-1.0.6-py2.7-nspkg.pth
> reviewboard
> ReviewBoard-2.5.7.dist-info
> ReviewBoard-2.5.7-py2.7.egg
>

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-03-02 Thread Bill Hoo

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 using pip + rb-site to upgrade RB, 
its downgrade to 2.5.7, but how can I upgrade to 2.5.9 by pip?

Best regards,
Bill.

在 2017年3月2日星期四 UTC+8下午6:45:03，Christian Hammond写道：
>
> 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 also have *.egg files, which are 
> installed using easy_install. Wheels will take precedence over eggs.
>
> I suspect what happened was that Review Board was once installed via pip, 
> and later you may have tried downgrading back to 2.5.7 using easy_install 
> (due to the fact that Djblets and other dependencies do not have eggs for 
> those versions, but rather have dist-info files).
>
> Pip is the recommended way to install Review Board, and upgrading using 
> pip should resolve your issue, I believe. Try:
>
> sudo pip install -U ReviewBoard
>
> Christian
>
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> On Wed, Mar 1, 2017 at 11:49 PM, Bill Hoo  
> wrote:
>
>> 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/ 
>> ) 
>> at the very first place, and then upgraded to 2.5.7 (followed by 
>> upgrading/upgrading-reviewboard/ 
>> ),
>>  
>> and this time when we upgrade to 2.5.9, we still use the same way, but get 
>> this error.
>>
>> I'm wondering if there's any way to go back to 2.5.7 and keep our origin 
>> data?
>>
>> Thanks,
>> Bill.
>>
>> 在 2017年3月2日星期四 UTC+8下午2:04:55，Christian Hammond写道：
>>>
>>> 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 need to take care of 
>>> both of those packages. Potentially other packages going forward.
>>>
>>> Christian
>>>
>>> -- 
>>> Christian Hammond
>>> President/CEO of Beanbag 
>>> Makers of Review Board 
>>>
>>> On Wed, Mar 1, 2017 at 8:42 PM, Bill Hoo  wrote:
>>>
 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
> Django-1.6.11.dist-info
> django_evolution
> django_evolution-0.7.6.dist-info
> django_haystack-2.4.1.dist-info
> django_multiselectfield-0.1.4.dist-info
> django_pipeline-1.3.27.dist-info
> djblets
> Djblets-0.9.4.dist-info
> Djblets-0.9.6-py2.7.egg
> dns
> dnspython-1.15.0.dist-info
> docutils
> docutils-0.13.1.dist-info
> easy-install.pth
> easy_install.py
> easy_install.pyc
> enum
> enum34-1.1.6.dist-info
> feedparser-5.2.1.dist-info
> feedparser.py
> feedparser.pyc
> futures-3.0.5.dist-info
> haystack
> idna
> idna-2.2.dist-info
> ipaddress-1.0.17.dist-info
> ipaddress.py
> ipaddress.pyc
> markdown
> Markdown-2.4.1.dist-info
> memcache.py
> memcache.pyc
> mimeparse-0.1.3.dist-info
> mimeparse.py
> mimeparse.pyc
> multiselectfield
> MySQLdb
> _mysql_exceptions.py
> _mysql_exceptions.pyc
> MySQL_python-1.2.5.dist-info
> _mysql.so
> paramiko
> paramiko-2.1.1.dist-info
> pep8-1.7.0-py2.7.egg
> PIL
> Pillow-3.4.2.dist-info
> pillowfight-0.2.dist-info
> pip
> pip-9.0.1.dist-info
> pipeline
> pkg_resources
> publicsuffix
> publicsuffix-1.1.0.dist-info
> pyasn1
> pyasn1-0.1.9.dist-info
> pycparser
> pycparser-2.17.dist-info
> pycrypto-2.6.1.dist-info
> pyflakes-1.4.0-py2.7.egg
> pygments
> Pygments-2.1.3.dist-info
> python_dateutil-1.5.dist-info
> python_memcached-1.58.dist-info
> pytz
> pytz-2016.10.dist-info
>

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-03-02 Thread Christian Hammond

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 also have *.egg files, which are
installed using easy_install. Wheels will take precedence over eggs.

I suspect what happened was that Review Board was once installed via pip,
and later you may have tried downgrading back to 2.5.7 using easy_install
(due to the fact that Djblets and other dependencies do not have eggs for
those versions, but rather have dist-info files).

Pip is the recommended way to install Review Board, and upgrading using pip
should resolve your issue, I believe. Try:

sudo pip install -U ReviewBoard

Christian

-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

On Wed, Mar 1, 2017 at 11:49 PM, Bill Hoo  wrote:

> 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/
> )
> at the very first place, and then upgraded to 2.5.7 (followed by
> upgrading/upgrading-reviewboard/
> ),
> and this time when we upgrade to 2.5.9, we still use the same way, but get
> this error.
>
> I'm wondering if there's any way to go back to 2.5.7 and keep our origin
> data?
>
> Thanks,
> Bill.
>
> 在 2017年3月2日星期四 UTC+8下午2:04:55，Christian Hammond写道：
>>
>> 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 need to take care of
>> both of those packages. Potentially other packages going forward.
>>
>> Christian
>>
>> --
>> Christian Hammond
>> President/CEO of Beanbag 
>> Makers of Review Board 
>>
>> On Wed, Mar 1, 2017 at 8:42 PM, Bill Hoo  wrote:
>>
>>> 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
 Django-1.6.11.dist-info
 django_evolution
 django_evolution-0.7.6.dist-info
 django_haystack-2.4.1.dist-info
 django_multiselectfield-0.1.4.dist-info
 django_pipeline-1.3.27.dist-info
 djblets
 Djblets-0.9.4.dist-info
 Djblets-0.9.6-py2.7.egg
 dns
 dnspython-1.15.0.dist-info
 docutils
 docutils-0.13.1.dist-info
 easy-install.pth
 easy_install.py
 easy_install.pyc
 enum
 enum34-1.1.6.dist-info
 feedparser-5.2.1.dist-info
 feedparser.py
 feedparser.pyc
 futures-3.0.5.dist-info
 haystack
 idna
 idna-2.2.dist-info
 ipaddress-1.0.17.dist-info
 ipaddress.py
 ipaddress.pyc
 markdown
 Markdown-2.4.1.dist-info
 memcache.py
 memcache.pyc
 mimeparse-0.1.3.dist-info
 mimeparse.py
 mimeparse.pyc
 multiselectfield
 MySQLdb
 _mysql_exceptions.py
 _mysql_exceptions.pyc
 MySQL_python-1.2.5.dist-info
 _mysql.so
 paramiko
 paramiko-2.1.1.dist-info
 pep8-1.7.0-py2.7.egg
 PIL
 Pillow-3.4.2.dist-info
 pillowfight-0.2.dist-info
 pip
 pip-9.0.1.dist-info
 pipeline
 pkg_resources
 publicsuffix
 publicsuffix-1.1.0.dist-info
 pyasn1
 pyasn1-0.1.9.dist-info
 pycparser
 pycparser-2.17.dist-info
 pycrypto-2.6.1.dist-info
 pyflakes-1.4.0-py2.7.egg
 pygments
 Pygments-2.1.3.dist-info
 python_dateutil-1.5.dist-info
 python_memcached-1.58.dist-info
 pytz
 pytz-2016.10.dist-info
 rbtools
 RBTools-0.7.9.dist-info
 recaptcha
 recaptcha_client-1.0.6.dist-info
 recaptcha_client-1.0.6-py2.7-nspkg.pth
 reviewboard
 ReviewBoard-2.5.7.dist-info
 ReviewBoard-2.5.7-py2.7.egg
 ReviewBoard-2.5.9-py2.7.egg
 ReviewBot-0.3a0-py2.7.egg
 setuptools
 setuptools-32.1.3.dist-info
 six-1.10.0.dist-info
 six.py
 six.pyc
 tqdm
 tqdm-4.11.0.dist-info
 wheel
 wheel-0.29.0.dist-info
 whoosh
 Whoosh-2.7.4.dist-info


>>> I noticed that RB2.5.7 has a file named "ReviewBoard-2.5.7.dist-info",
>>> but 2.5.9 didn't. Is this a problem?
>>>
>>> Thanks,
>>> Bill.
>>>
>>> 在 2017年3月1日星期三

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-03-01 Thread Bill Hoo

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/ 
) at 
the very first place, and then upgraded to 2.5.7 (followed by 
upgrading/upgrading-reviewboard/ 
),
 
and this time when we upgrade to 2.5.9, we still use the same way, but get 
this error.

I'm wondering if there's any way to go back to 2.5.7 and keep our origin 
data?

Thanks,
Bill.

在 2017年3月2日星期四 UTC+8下午2:04:55，Christian Hammond写道：
>
> 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 need to take care of 
> both of those packages. Potentially other packages going forward.
>
> Christian
>
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> On Wed, Mar 1, 2017 at 8:42 PM, Bill Hoo  
> wrote:
>
>> 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
>>> Django-1.6.11.dist-info
>>> django_evolution
>>> django_evolution-0.7.6.dist-info
>>> django_haystack-2.4.1.dist-info
>>> django_multiselectfield-0.1.4.dist-info
>>> django_pipeline-1.3.27.dist-info
>>> djblets
>>> Djblets-0.9.4.dist-info
>>> Djblets-0.9.6-py2.7.egg
>>> dns
>>> dnspython-1.15.0.dist-info
>>> docutils
>>> docutils-0.13.1.dist-info
>>> easy-install.pth
>>> easy_install.py
>>> easy_install.pyc
>>> enum
>>> enum34-1.1.6.dist-info
>>> feedparser-5.2.1.dist-info
>>> feedparser.py
>>> feedparser.pyc
>>> futures-3.0.5.dist-info
>>> haystack
>>> idna
>>> idna-2.2.dist-info
>>> ipaddress-1.0.17.dist-info
>>> ipaddress.py
>>> ipaddress.pyc
>>> markdown
>>> Markdown-2.4.1.dist-info
>>> memcache.py
>>> memcache.pyc
>>> mimeparse-0.1.3.dist-info
>>> mimeparse.py
>>> mimeparse.pyc
>>> multiselectfield
>>> MySQLdb
>>> _mysql_exceptions.py
>>> _mysql_exceptions.pyc
>>> MySQL_python-1.2.5.dist-info
>>> _mysql.so
>>> paramiko
>>> paramiko-2.1.1.dist-info
>>> pep8-1.7.0-py2.7.egg
>>> PIL
>>> Pillow-3.4.2.dist-info
>>> pillowfight-0.2.dist-info
>>> pip
>>> pip-9.0.1.dist-info
>>> pipeline
>>> pkg_resources
>>> publicsuffix
>>> publicsuffix-1.1.0.dist-info
>>> pyasn1
>>> pyasn1-0.1.9.dist-info
>>> pycparser
>>> pycparser-2.17.dist-info
>>> pycrypto-2.6.1.dist-info
>>> pyflakes-1.4.0-py2.7.egg
>>> pygments
>>> Pygments-2.1.3.dist-info
>>> python_dateutil-1.5.dist-info
>>> python_memcached-1.58.dist-info
>>> pytz
>>> pytz-2016.10.dist-info
>>> rbtools
>>> RBTools-0.7.9.dist-info
>>> recaptcha
>>> recaptcha_client-1.0.6.dist-info
>>> recaptcha_client-1.0.6-py2.7-nspkg.pth
>>> reviewboard
>>> ReviewBoard-2.5.7.dist-info
>>> ReviewBoard-2.5.7-py2.7.egg
>>> ReviewBoard-2.5.9-py2.7.egg
>>> ReviewBot-0.3a0-py2.7.egg
>>> setuptools
>>> setuptools-32.1.3.dist-info
>>> six-1.10.0.dist-info
>>> six.py
>>> six.pyc
>>> tqdm
>>> tqdm-4.11.0.dist-info
>>> wheel
>>> wheel-0.29.0.dist-info
>>> whoosh
>>> Whoosh-2.7.4.dist-info
>>>
>>>
>> I noticed that RB2.5.7 has a file named "ReviewBoard-2.5.7.dist-info", 
>> but 2.5.9 didn't. Is this a problem?
>>
>> Thanks,
>> Bill.
>>
>> 在 2017年3月1日星期三 UTC+8下午2:51:31，Christian Hammond写道：
>>>
>>> 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 Apache is running against 2.5.7. Not having 
>>> access to the server, I can't really say why, so it'll take some 
>>> investigation on your end, but it does seem like the older version is 
>>> taking precedence.
>>>
>>> Was 2.5.7 also installed using easy_install? Can you show me the 
>>> contents of your dist-packages directory?
>>>
>>> Christian
>>>
>>> -- 
>>> Christian Hammond
>>> President/CEO of Beanbag 
>>> Makers of Review Board 
>>>
>>> On Tue, Feb 28, 2017 at 5:42 PM, Bill Hoo  wrote:
>>>
 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

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-03-01 Thread Christian Hammond

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 need to take care of
both of those packages. Potentially other packages going forward.

Christian

-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

On Wed, Mar 1, 2017 at 8:42 PM, Bill Hoo  wrote:

> 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
>> Django-1.6.11.dist-info
>> django_evolution
>> django_evolution-0.7.6.dist-info
>> django_haystack-2.4.1.dist-info
>> django_multiselectfield-0.1.4.dist-info
>> django_pipeline-1.3.27.dist-info
>> djblets
>> Djblets-0.9.4.dist-info
>> Djblets-0.9.6-py2.7.egg
>> dns
>> dnspython-1.15.0.dist-info
>> docutils
>> docutils-0.13.1.dist-info
>> easy-install.pth
>> easy_install.py
>> easy_install.pyc
>> enum
>> enum34-1.1.6.dist-info
>> feedparser-5.2.1.dist-info
>> feedparser.py
>> feedparser.pyc
>> futures-3.0.5.dist-info
>> haystack
>> idna
>> idna-2.2.dist-info
>> ipaddress-1.0.17.dist-info
>> ipaddress.py
>> ipaddress.pyc
>> markdown
>> Markdown-2.4.1.dist-info
>> memcache.py
>> memcache.pyc
>> mimeparse-0.1.3.dist-info
>> mimeparse.py
>> mimeparse.pyc
>> multiselectfield
>> MySQLdb
>> _mysql_exceptions.py
>> _mysql_exceptions.pyc
>> MySQL_python-1.2.5.dist-info
>> _mysql.so
>> paramiko
>> paramiko-2.1.1.dist-info
>> pep8-1.7.0-py2.7.egg
>> PIL
>> Pillow-3.4.2.dist-info
>> pillowfight-0.2.dist-info
>> pip
>> pip-9.0.1.dist-info
>> pipeline
>> pkg_resources
>> publicsuffix
>> publicsuffix-1.1.0.dist-info
>> pyasn1
>> pyasn1-0.1.9.dist-info
>> pycparser
>> pycparser-2.17.dist-info
>> pycrypto-2.6.1.dist-info
>> pyflakes-1.4.0-py2.7.egg
>> pygments
>> Pygments-2.1.3.dist-info
>> python_dateutil-1.5.dist-info
>> python_memcached-1.58.dist-info
>> pytz
>> pytz-2016.10.dist-info
>> rbtools
>> RBTools-0.7.9.dist-info
>> recaptcha
>> recaptcha_client-1.0.6.dist-info
>> recaptcha_client-1.0.6-py2.7-nspkg.pth
>> reviewboard
>> ReviewBoard-2.5.7.dist-info
>> ReviewBoard-2.5.7-py2.7.egg
>> ReviewBoard-2.5.9-py2.7.egg
>> ReviewBot-0.3a0-py2.7.egg
>> setuptools
>> setuptools-32.1.3.dist-info
>> six-1.10.0.dist-info
>> six.py
>> six.pyc
>> tqdm
>> tqdm-4.11.0.dist-info
>> wheel
>> wheel-0.29.0.dist-info
>> whoosh
>> Whoosh-2.7.4.dist-info
>>
>>
> I noticed that RB2.5.7 has a file named "ReviewBoard-2.5.7.dist-info", but
> 2.5.9 didn't. Is this a problem?
>
> Thanks,
> Bill.
>
> 在 2017年3月1日星期三 UTC+8下午2:51:31，Christian Hammond写道：
>>
>> 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 Apache is running against 2.5.7. Not having
>> access to the server, I can't really say why, so it'll take some
>> investigation on your end, but it does seem like the older version is
>> taking precedence.
>>
>> Was 2.5.7 also installed using easy_install? Can you show me the contents
>> of your dist-packages directory?
>>
>> Christian
>>
>> --
>> Christian Hammond
>> President/CEO of Beanbag 
>> Makers of Review Board 
>>
>> On Tue, Feb 28, 2017 at 5:42 PM, Bill Hoo  wrote:
>>
>>> 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 I do it
>>> right?
>>>
>>> Regards,
>>> Bill.
>>>
>>> 在 2017年2月28日星期二 UTC+8下午7:58:18，Christian Hammond写道：

 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 Python version issue can happen if you've done a big system upgrade
 or transferred between systems. I'd check for that and make sure your
 system is consistent with the versions of Python being used in the command
 line and on Apache.

 Christian


 On Tue, Feb 28, 2017 at 02:50 Bill Hoo  wrote:

> Here's the command we ran:
>
> sudo rb-site upgrade

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-03-01 Thread Bill Hoo

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
> Django-1.6.11.dist-info
> django_evolution
> django_evolution-0.7.6.dist-info
> django_haystack-2.4.1.dist-info
> django_multiselectfield-0.1.4.dist-info
> django_pipeline-1.3.27.dist-info
> djblets
> Djblets-0.9.4.dist-info
> Djblets-0.9.6-py2.7.egg
> dns
> dnspython-1.15.0.dist-info
> docutils
> docutils-0.13.1.dist-info
> easy-install.pth
> easy_install.py
> easy_install.pyc
> enum
> enum34-1.1.6.dist-info
> feedparser-5.2.1.dist-info
> feedparser.py
> feedparser.pyc
> futures-3.0.5.dist-info
> haystack
> idna
> idna-2.2.dist-info
> ipaddress-1.0.17.dist-info
> ipaddress.py
> ipaddress.pyc
> markdown
> Markdown-2.4.1.dist-info
> memcache.py
> memcache.pyc
> mimeparse-0.1.3.dist-info
> mimeparse.py
> mimeparse.pyc
> multiselectfield
> MySQLdb
> _mysql_exceptions.py
> _mysql_exceptions.pyc
> MySQL_python-1.2.5.dist-info
> _mysql.so
> paramiko
> paramiko-2.1.1.dist-info
> pep8-1.7.0-py2.7.egg
> PIL
> Pillow-3.4.2.dist-info
> pillowfight-0.2.dist-info
> pip
> pip-9.0.1.dist-info
> pipeline
> pkg_resources
> publicsuffix
> publicsuffix-1.1.0.dist-info
> pyasn1
> pyasn1-0.1.9.dist-info
> pycparser
> pycparser-2.17.dist-info
> pycrypto-2.6.1.dist-info
> pyflakes-1.4.0-py2.7.egg
> pygments
> Pygments-2.1.3.dist-info
> python_dateutil-1.5.dist-info
> python_memcached-1.58.dist-info
> pytz
> pytz-2016.10.dist-info
> rbtools
> RBTools-0.7.9.dist-info
> recaptcha
> recaptcha_client-1.0.6.dist-info
> recaptcha_client-1.0.6-py2.7-nspkg.pth
> reviewboard
> ReviewBoard-2.5.7.dist-info
> ReviewBoard-2.5.7-py2.7.egg
> ReviewBoard-2.5.9-py2.7.egg
> ReviewBot-0.3a0-py2.7.egg
> setuptools
> setuptools-32.1.3.dist-info
> six-1.10.0.dist-info
> six.py
> six.pyc
> tqdm
> tqdm-4.11.0.dist-info
> wheel
> wheel-0.29.0.dist-info
> whoosh
> Whoosh-2.7.4.dist-info
>
>
I noticed that RB2.5.7 has a file named "ReviewBoard-2.5.7.dist-info", but 
2.5.9 didn't. Is this a problem?

Thanks,
Bill.

在 2017年3月1日星期三 UTC+8下午2:51:31，Christian Hammond写道：
>
> 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 Apache is running against 2.5.7. Not having 
> access to the server, I can't really say why, so it'll take some 
> investigation on your end, but it does seem like the older version is 
> taking precedence.
>
> Was 2.5.7 also installed using easy_install? Can you show me the contents 
> of your dist-packages directory?
>
> Christian
>
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> On Tue, Feb 28, 2017 at 5:42 PM, Bill Hoo  
> wrote:
>
>> 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 I do it 
>> right?
>>
>> Regards,
>> Bill.
>>
>> 在 2017年2月28日星期二 UTC+8下午7:58:18，Christian Hammond写道：
>>>
>>> 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 Python version issue can happen if you've done a big system upgrade 
>>> or transferred between systems. I'd check for that and make sure your 
>>> system is consistent with the versions of Python being used in the command 
>>> line and on Apache.
>>>
>>> Christian
>>>
>>>
>>> On Tue, Feb 28, 2017 at 02:50 Bill Hoo  wrote:
>>>
 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 unless upgrade fails.
>
> --  --
> Creating tables ...
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
> No evolution required.
> ---  ---
>
> Resetting in-database caches.
>
> Upgrade complete!
>




 After the upgrade, we've checked the version of rb-site by typing

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-03-01 Thread Bill Hoo

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, 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 Apache is running against 2.5.7. Not having 
> access to the server, I can't really say why, so it'll take some 
> investigation on your end, but it does seem like the older version is 
> taking precedence.
>
> Was 2.5.7 also installed using easy_install? Can you show me the contents 
> of your dist-packages directory?
>
> Christian
>
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> On Tue, Feb 28, 2017 at 5:42 PM, Bill Hoo  
> wrote:
>
>> 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 I do it 
>> right?
>>
>> Regards,
>> Bill.
>>
>> 在 2017年2月28日星期二 UTC+8下午7:58:18，Christian Hammond写道：
>>>
>>> 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 Python version issue can happen if you've done a big system upgrade 
>>> or transferred between systems. I'd check for that and make sure your 
>>> system is consistent with the versions of Python being used in the command 
>>> line and on Apache.
>>>
>>> Christian
>>>
>>>
>>> On Tue, Feb 28, 2017 at 02:50 Bill Hoo  wrote:
>>>
 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 unless upgrade fails.
>
> --  --
> Creating tables ...
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
> No evolution required.
> ---  ---
>
> Resetting in-database caches.
>
> Upgrade complete!
>




 After the upgrade, we've checked the version of rb-site by typing 
 "rb-site --v" and its already 2.5.9.
 But the web page keeps asking me to upgrade the site:


 The version of Review Board running does not match the version the site 
> was last upgraded to. You are running *2.5.7* and the site was last 
> upgraded to *2.5.9*. 
>
> Please upgrade your site to fix this by running: 
>
> $ rb-site upgrade /var/www/crisisgo_reviewboard
>
>
 It seems the ReviewBoard itself are not upgrade correctly not the site.

 Thanks,
 Bill.



 在 2017年2月28日星期二 UTC+8下午6:19:09，Christian Hammond写道：
>
> 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:
>>
>>
>> Searching for ReviewBoard
>>> Reading https://pypi.python.org/simple/ReviewBoard/
>>> Downloading 
>>> https://pypi.python.org/packages/5a/62/fb2d4f199581aa33c1734595c0a85183b858034a22f8f1e2ff2a945617e5/ReviewBoard-2.5.9-py2.7.egg#md5=33efb523ebd43b35e178e141f713f362
>>> Best match: ReviewBoard 2.5.9
>>> Processing ReviewBoard-2.5.9-py2.7.egg
>>> removing 
>>> '/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg' 
>>> (and 
>>> everything under it)
>>> creating 
>>> /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
>>> Extracting ReviewBoard-2.5.9-py2.7.egg to 
>>> /usr/local/lib/python2.7/dist-packages
>>> ReviewBoard 2.5.9 is already the active version in easy-install.pth
>>> Installing rbext script to /usr/local/bin
>>> Installing rbssh script to /usr/local/bin
>>> Installing rb-site script to /usr/local/bin
>>>
>>> Installed

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-02-28 Thread Christian Hammond

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 Apache is running against 2.5.7. Not having
access to the server, I can't really say why, so it'll take some
investigation on your end, but it does seem like the older version is
taking precedence.

Was 2.5.7 also installed using easy_install? Can you show me the contents
of your dist-packages directory?

Christian

-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

On Tue, Feb 28, 2017 at 5:42 PM, Bill Hoo  wrote:

> 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 I do it
> right?
>
> Regards,
> Bill.
>
> 在 2017年2月28日星期二 UTC+8下午7:58:18，Christian Hammond写道：
>>
>> 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 Python version issue can happen if you've done a big system upgrade
>> or transferred between systems. I'd check for that and make sure your
>> system is consistent with the versions of Python being used in the command
>> line and on Apache.
>>
>> Christian
>>
>>
>> On Tue, Feb 28, 2017 at 02:50 Bill Hoo  wrote:
>>
>>> 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 unless upgrade fails.

 --  --
 Creating tables ...
 Installing custom SQL ...
 Installing indexes ...
 Installed 0 object(s) from 0 fixture(s)
 No evolution required.
 ---  ---

 Resetting in-database caches.

 Upgrade complete!

>>>
>>>
>>>
>>>
>>> After the upgrade, we've checked the version of rb-site by typing
>>> "rb-site --v" and its already 2.5.9.
>>> But the web page keeps asking me to upgrade the site:
>>>
>>>
>>> The version of Review Board running does not match the version the site
 was last upgraded to. You are running *2.5.7* and the site was last
 upgraded to *2.5.9*.

 Please upgrade your site to fix this by running:

 $ rb-site upgrade /var/www/crisisgo_reviewboard


>>> It seems the ReviewBoard itself are not upgrade correctly not the site.
>>>
>>> Thanks,
>>> Bill.
>>>
>>>
>>>
>>> 在 2017年2月28日星期二 UTC+8下午6:19:09，Christian Hammond写道：

 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:
>
>
> Searching for ReviewBoard
>> Reading https://pypi.python.org/simple/ReviewBoard/
>> Downloading https://pypi.python.org/packag
>> es/5a/62/fb2d4f199581aa33c1734595c0a85183b858034a22f8f1e2ff2
>> a945617e5/ReviewBoard-2.5.9-py2.7.egg#md5=33efb523ebd43b35
>> e178e141f713f362
>> Best match: ReviewBoard 2.5.9
>> Processing ReviewBoard-2.5.9-py2.7.egg
>> removing 
>> '/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg'
>> (and everything under it)
>> creating /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2
>> .7.egg
>> Extracting ReviewBoard-2.5.9-py2.7.egg to
>> /usr/local/lib/python2.7/dist-packages
>> ReviewBoard 2.5.9 is already the active version in easy-install.pth
>> Installing rbext script to /usr/local/bin
>> Installing rbssh script to /usr/local/bin
>> Installing rb-site script to /usr/local/bin
>>
>> Installed /usr/local/lib/python2.7/dist-
>> packages/ReviewBoard-2.5.9-py2.7.egg
>> Processing dependencies for ReviewBoard
>> Finished processing dependencies for ReviewBoard
>>
>>
>  it seems successful right? And then we run:
>
> rb-site upgrade /path/to/site
>
>
> After a while it says upgrade complete!
> Things are looking good. After these 2 steps, we restart Apache2 and
> memcache.
>
> But

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-02-28 Thread Bill Hoo

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 I do it 
right?

Regards,
Bill.

在 2017年2月28日星期二 UTC+8下午7:58:18，Christian Hammond写道：
>
> 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 Python version issue can happen if you've done a big system upgrade or 
> transferred between systems. I'd check for that and make sure your system 
> is consistent with the versions of Python being used in the command line 
> and on Apache.
>
> Christian
>
>
> On Tue, Feb 28, 2017 at 02:50 Bill Hoo  
> wrote:
>
>> 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 unless upgrade fails.
>>>
>>> --  --
>>> Creating tables ...
>>> Installing custom SQL ...
>>> Installing indexes ...
>>> Installed 0 object(s) from 0 fixture(s)
>>> No evolution required.
>>> ---  ---
>>>
>>> Resetting in-database caches.
>>>
>>> Upgrade complete!
>>>
>>
>>
>>
>>
>> After the upgrade, we've checked the version of rb-site by typing 
>> "rb-site --v" and its already 2.5.9.
>> But the web page keeps asking me to upgrade the site:
>>
>>
>> The version of Review Board running does not match the version the site 
>>> was last upgraded to. You are running *2.5.7* and the site was last 
>>> upgraded to *2.5.9*. 
>>>
>>> Please upgrade your site to fix this by running: 
>>>
>>> $ rb-site upgrade /var/www/crisisgo_reviewboard
>>>
>>>
>> It seems the ReviewBoard itself are not upgrade correctly not the site.
>>
>> Thanks,
>> Bill.
>>
>>
>>
>> 在 2017年2月28日星期二 UTC+8下午6:19:09，Christian Hammond写道：
>>>
>>> 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:


 Searching for ReviewBoard
> Reading https://pypi.python.org/simple/ReviewBoard/
> Downloading 
> https://pypi.python.org/packages/5a/62/fb2d4f199581aa33c1734595c0a85183b858034a22f8f1e2ff2a945617e5/ReviewBoard-2.5.9-py2.7.egg#md5=33efb523ebd43b35e178e141f713f362
> Best match: ReviewBoard 2.5.9
> Processing ReviewBoard-2.5.9-py2.7.egg
> removing 
> '/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg' (and 
> everything under it)
> creating 
> /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
> Extracting ReviewBoard-2.5.9-py2.7.egg to 
> /usr/local/lib/python2.7/dist-packages
> ReviewBoard 2.5.9 is already the active version in easy-install.pth
> Installing rbext script to /usr/local/bin
> Installing rbssh script to /usr/local/bin
> Installing rb-site script to /usr/local/bin
>
> Installed 
> /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
> Processing dependencies for ReviewBoard
> Finished processing dependencies for ReviewBoard
>
>
  it seems successful right? And then we run:

 rb-site upgrade /path/to/site


 After a while it says upgrade complete!
 Things are looking good. After these 2 steps, we restart Apache2 and 
 memcache.

 But finally when we visit our RB site, we get that error.

 Regards,
 Bill.

 在 2017年2月28日星期二 UTC+8下午1:19:44，Christian Hammond写道：
>
> 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 failed, below are the messages come from our RB web 
>> site 
>> after restart apache:
>>
>>
>>
>>> The version of Review Board running does not match the version the 
>>> site was last upgraded to. You are running *2.5.7* and the site was 
>>> last upgraded to *2.5.9*. 
>>>
>>> Please upgrade your site to fix this by running: 
>>>
>>> $ rb-site upgrade

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-02-28 Thread Christian Hammond

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 Python version issue can happen if you've done a big system upgrade or
transferred between systems. I'd check for that and make sure your system
is consistent with the versions of Python being used in the command line
and on Apache.

Christian


On Tue, Feb 28, 2017 at 02:50 Bill Hoo  wrote:

> 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 unless upgrade fails.
>
> --  --
> Creating tables ...
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
> No evolution required.
> ---  ---
>
> Resetting in-database caches.
>
> Upgrade complete!
>
>
>
>
>
> After the upgrade, we've checked the version of rb-site by typing "rb-site
> --v" and its already 2.5.9.
> But the web page keeps asking me to upgrade the site:
>
>
> The version of Review Board running does not match the version the site
> was last upgraded to. You are running *2.5.7* and the site was last
> upgraded to *2.5.9*.
>
> Please upgrade your site to fix this by running:
>
> $ rb-site upgrade /var/www/crisisgo_reviewboard
>
>
> It seems the ReviewBoard itself are not upgrade correctly not the site.
>
> Thanks,
> Bill.
>
>
>
> 在 2017年2月28日星期二 UTC+8下午6:19:09，Christian Hammond写道：
>
> 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:
>
>
> Searching for ReviewBoard
> Reading https://pypi.python.org/simple/ReviewBoard/
> Downloading
> https://pypi.python.org/packages/5a/62/fb2d4f199581aa33c1734595c0a85183b858034a22f8f1e2ff2a945617e5/ReviewBoard-2.5.9-py2.7.egg#md5=33efb523ebd43b35e178e141f713f362
> Best match: ReviewBoard 2.5.9
> Processing ReviewBoard-2.5.9-py2.7.egg
> removing
> '/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg' (and
> everything under it)
> creating /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
> Extracting ReviewBoard-2.5.9-py2.7.egg to
> /usr/local/lib/python2.7/dist-packages
> ReviewBoard 2.5.9 is already the active version in easy-install.pth
> Installing rbext script to /usr/local/bin
> Installing rbssh script to /usr/local/bin
> Installing rb-site script to /usr/local/bin
>
> Installed
> /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
> Processing dependencies for ReviewBoard
> Finished processing dependencies for ReviewBoard
>
>
>  it seems successful right? And then we run:
>
> rb-site upgrade /path/to/site
>
>
> After a while it says upgrade complete!
> Things are looking good. After these 2 steps, we restart Apache2 and
> memcache.
>
> But finally when we visit our RB site, we get that error.
>
> Regards,
> Bill.
>
> 在 2017年2月28日星期二 UTC+8下午1:19:44，Christian Hammond写道：
>
> 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 failed, below are the messages come from our RB web site
> after restart apache:
>
>
>
> The version of Review Board running does not match the version the site
> was last upgraded to. You are running *2.5.7* and the site was last
> upgraded to *2.5.9*.
>
> Please upgrade your site to fix this by running:
>
> $ rb-site upgrade /var/www/crisisgo_reviewboard
>
>
>
> What's the problem should it be? How can we fix it?
>
> Thanks.
> Bill.
>
>
>
>
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> --
> --
> Christian Hammond
> President/CEO of Beanbag

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-02-28 Thread Bill Hoo

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 unless upgrade fails.
>
> --  --
> Creating tables ...
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
> No evolution required.
> ---  ---
>
> Resetting in-database caches.
>
> Upgrade complete!
>




After the upgrade, we've checked the version of rb-site by typing "rb-site 
--v" and its already 2.5.9.
But the web page keeps asking me to upgrade the site:

The version of Review Board running does not match the version the site was 
> last upgraded to. You are running *2.5.7* and the site was last upgraded 
> to *2.5.9*. 
>
> Please upgrade your site to fix this by running: 
>
> $ rb-site upgrade /var/www/crisisgo_reviewboard
>
>
It seems the ReviewBoard itself are not upgrade correctly not the site.

Thanks,
Bill.



在 2017年2月28日星期二 UTC+8下午6:19:09，Christian Hammond写道：
>
> 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:
>>
>>
>> Searching for ReviewBoard
>>> Reading https://pypi.python.org/simple/ReviewBoard/
>>> Downloading 
>>> https://pypi.python.org/packages/5a/62/fb2d4f199581aa33c1734595c0a85183b858034a22f8f1e2ff2a945617e5/ReviewBoard-2.5.9-py2.7.egg#md5=33efb523ebd43b35e178e141f713f362
>>> Best match: ReviewBoard 2.5.9
>>> Processing ReviewBoard-2.5.9-py2.7.egg
>>> removing 
>>> '/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg' (and 
>>> everything under it)
>>> creating 
>>> /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
>>> Extracting ReviewBoard-2.5.9-py2.7.egg to 
>>> /usr/local/lib/python2.7/dist-packages
>>> ReviewBoard 2.5.9 is already the active version in easy-install.pth
>>> Installing rbext script to /usr/local/bin
>>> Installing rbssh script to /usr/local/bin
>>> Installing rb-site script to /usr/local/bin
>>>
>>> Installed 
>>> /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
>>> Processing dependencies for ReviewBoard
>>> Finished processing dependencies for ReviewBoard
>>>
>>>
>>  it seems successful right? And then we run:
>>
>> rb-site upgrade /path/to/site
>>
>>
>> After a while it says upgrade complete!
>> Things are looking good. After these 2 steps, we restart Apache2 and 
>> memcache.
>>
>> But finally when we visit our RB site, we get that error.
>>
>> Regards,
>> Bill.
>>
>> 在 2017年2月28日星期二 UTC+8下午1:19:44，Christian Hammond写道：
>>>
>>> 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 failed, below are the messages come from our RB web 
 site 
 after restart apache:



> The version of Review Board running does not match the version the 
> site was last upgraded to. You are running *2.5.7* and the site was 
> last upgraded to *2.5.9*. 
>
> Please upgrade your site to fix this by running: 
>
> $ rb-site upgrade /var/www/crisisgo_reviewboard
>
>

 What's the problem should it be? How can we fix it?

 Thanks.
 Bill.



  

 -- 
 Supercharge your Review Board with Power Pack: 
 https://www.reviewboard.org/powerpack/
 Want us to host Review Board for you? Check out RBCommons: 
 https://rbcommons.com/
 Happy user? Let us know! https://www.reviewboard.org/users/
 --- 
 You received this message because you are subscribed to the Google 
 Groups "reviewboard" group.

>>> To unsubscribe from this group and stop receiving emails from it, send 
 an email to reviewboard...@googlegroups.com.
>>>
>>>
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>>> -- 
>>> Christian Hammond
>>> President/CEO of Beanbag 
>>> Makers of Review Board 
>>>
>> -- 
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-02-28 Thread Christian Hammond

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:
>
>
> Searching for ReviewBoard
> Reading https://pypi.python.org/simple/ReviewBoard/
> Downloading
> https://pypi.python.org/packages/5a/62/fb2d4f199581aa33c1734595c0a85183b858034a22f8f1e2ff2a945617e5/ReviewBoard-2.5.9-py2.7.egg#md5=33efb523ebd43b35e178e141f713f362
> Best match: ReviewBoard 2.5.9
> Processing ReviewBoard-2.5.9-py2.7.egg
> removing
> '/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg' (and
> everything under it)
> creating /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
> Extracting ReviewBoard-2.5.9-py2.7.egg to
> /usr/local/lib/python2.7/dist-packages
> ReviewBoard 2.5.9 is already the active version in easy-install.pth
> Installing rbext script to /usr/local/bin
> Installing rbssh script to /usr/local/bin
> Installing rb-site script to /usr/local/bin
>
> Installed
> /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
> Processing dependencies for ReviewBoard
> Finished processing dependencies for ReviewBoard
>
>
>  it seems successful right? And then we run:
>
> rb-site upgrade /path/to/site
>
>
> After a while it says upgrade complete!
> Things are looking good. After these 2 steps, we restart Apache2 and
> memcache.
>
> But finally when we visit our RB site, we get that error.
>
> Regards,
> Bill.
>
> 在 2017年2月28日星期二 UTC+8下午1:19:44，Christian Hammond写道：
>
> 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 failed, below are the messages come from our RB web site
> after restart apache:
>
>
>
> The version of Review Board running does not match the version the site
> was last upgraded to. You are running *2.5.7* and the site was last
> upgraded to *2.5.9*.
>
> Please upgrade your site to fix this by running:
>
> $ rb-site upgrade /var/www/crisisgo_reviewboard
>
>
>
> What's the problem should it be? How can we fix it?
>
> Thanks.
> Bill.
>
>
>
>
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>
> --
-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-02-27 Thread Bill Hoo

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 
> https://pypi.python.org/packages/5a/62/fb2d4f199581aa33c1734595c0a85183b858034a22f8f1e2ff2a945617e5/ReviewBoard-2.5.9-py2.7.egg#md5=33efb523ebd43b35e178e141f713f362
> Best match: ReviewBoard 2.5.9
> Processing ReviewBoard-2.5.9-py2.7.egg
> removing 
> '/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg' (and 
> everything under it)
> creating /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
> Extracting ReviewBoard-2.5.9-py2.7.egg to 
> /usr/local/lib/python2.7/dist-packages
> ReviewBoard 2.5.9 is already the active version in easy-install.pth
> Installing rbext script to /usr/local/bin
> Installing rbssh script to /usr/local/bin
> Installing rb-site script to /usr/local/bin
>
> Installed 
> /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5.9-py2.7.egg
> Processing dependencies for ReviewBoard
> Finished processing dependencies for ReviewBoard
>
>
 it seems successful right? And then we run:

rb-site upgrade /path/to/site


After a while it says upgrade complete!
Things are looking good. After these 2 steps, we restart Apache2 and 
memcache.

But finally when we visit our RB site, we get that error.

Regards,
Bill.

在 2017年2月28日星期二 UTC+8下午1:19:44，Christian Hammond写道：
>
> 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 failed, below are the messages come from our RB web site 
>> after restart apache:
>>
>>
>>
>>> The version of Review Board running does not match the version the site 
>>> was last upgraded to. You are running *2.5.7* and the site was last 
>>> upgraded to *2.5.9*. 
>>>
>>> Please upgrade your site to fix this by running: 
>>>
>>> $ rb-site upgrade /var/www/crisisgo_reviewboard
>>>
>>>
>>
>> What's the problem should it be? How can we fix it?
>>
>> Thanks.
>> Bill.
>>
>>
>>
>>  
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to ReviewBoard 2.5.9 failed.

2017-02-27 Thread Christian Hammond

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 failed, below are the messages come from our RB web site
> after restart apache:
>
>
>
> The version of Review Board running does not match the version the site
> was last upgraded to. You are running *2.5.7* and the site was last
> upgraded to *2.5.9*.
>
> Please upgrade your site to fix this by running:
>
> $ rb-site upgrade /var/www/crisisgo_reviewboard
>
>
>
> What's the problem should it be? How can we fix it?
>
> Thanks.
> Bill.
>
>
>
>
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

Re: Upgrade to ReviewBoard 2.5.9 failed.

14 matches

Site Navigation

Mail list logo

Footer information