Hi Florian,
You just need a database containing the older schema, along with the old
site directory (or a copy) on the server using Review Board 3.0. You can
then run rb-site upgrade, as usual.
The reason it failed before is that you had a mix of Review Board versions
running. There was an
I tried to make a fresh install over 3 beta version and now I'm trying to
configure the ReviewBot-Extension which is crucial for us.
Do you have any tips on how to migrate the database content of the old
installation in the v3 sql database ?
thanks,
Florian.
miercuri, 26 iulie 2017, 23:27:28
Looks like while you have 3.0 installed, your rb-site script is still for
2.5.12, so it's attempting a downgrade. It's likely you have two copies
installed, one provided perhaps by an RPM, and another (probably in
/usr/local/bin) provided by the Python packages.
It's going to be important to
[root@reviews ~]# which rb-site
/usr/bin/rb-site
[root@reviews ~]# head `which rb-site`
#!/usr/bin/python
# EASY-INSTALL-ENTRY-SCRIPT:
'ReviewBoard==2.5.12','console_scripts','rb-site'
__requires__ = 'ReviewBoard==2.5.12'
import re
import sys
from pkg_resources import load_entry_point
if
Hi,
Is this on a test server? Do you have a backup of the database? If not,
make one right now before you proceed any further.
I suspect you have two copies of Review Board installed. That error log
looks like it's trying to go from Review Board 3.0 beta 1 to 2.5.12 again.
Can you show me what
