In theory, you should be able to upgrade from a 1.0rc2.1 install.
What you'd do is configure a new install to point to the same database, and
do 'rb-site upgrade' on the database. You can start this off by creating a
site (rb-site install), copying over your old site's settings_local.py
file, and then running 'rb-site upgrade' on the site.
In your case, BACK UP YOUR DATABASE FIRST! Can't stress this enough :)
Now, there is a bug some people have hit in the upgrade process for the
database, which you may be able to fix by installing the version of Django
Evolution from http://downloads.reviewboard.org/temp/django-evolution/
I'm still trying to figure out if we have all the right logic in there, and
are looking for people to test. Since you're likely to run into the issue,
you're a good candidate. So, on the new machine, install the appropriate
package from there, then do the above steps to migrate over your install.
(Note: This is where the backup comes in. If the upgrade fails, it's
possible that your database will be in a mixed state, and, depending on how
mixed, you may need to restore it. Hopefully this does not happen.)
The upgrade process may possibly tell you about a manual step or two you
have to make as well. If you got that far, the database upgrade, at least
in theory, went smoothly, though you'll need to spend some time
experimenting with aspects of the site to be sure.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Mar 11, 2013 at 9:55 AM, <justin.ha...@pgs.com> wrote:
> Hi there,
> At my office, a few of us have been using ReviewBoard 1.0rc2.1 for a few
> years without much complaint and recently had to upgrade the system it was
> running on. Needless to say, ReviewBoard wasn't too happy about this.
> We're desparately trying to resolve the situation so that we can either:
> a) get the same version of ReviewBoard working again, or
> b) get a slightly similar (but perhaps slightly newer) version working
> c) get the latest version working
> We successfully installed the newest version on a clean install, but don't
> expect to be able to migrate our data very easily - any suggestions?
> We've failed to get the same version installed again, because it seems
> that Debian wants everything to be Python 2.6 now, and the original version
> seems to be Python 2.5 (have I expressed that correctly?), at least in the
> egg file name.
> Any suggestions at all would be welcome...
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
> 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/groups/opt_out.
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.