Thank you for your reply. I create a thread
at https://groups.google.com/forum/#!topic/reviewboard/EVEDKKQ2b78
On Sunday, December 6, 2015 at 12:27:20 PM UTC-8, Christian Hammond wrote:
>
> Hi Kevin,
>
> Given how long ago that was, and how many releases ago, can you start a
> new thread with
Hi Daniel,
I ran into the same problem here. Did you ever figure out? Thanks!
Kevin
On Saturday, May 10, 2014 at 5:14:27 AM UTC-7, Daniel Laird wrote:
>
> My original email was not very clear.
> On my backup server I want to remove the 2.0RC2 installation and get a
> 1.7.x installation
Hi Kevin,
Given how long ago that was, and how many releases ago, can you start a new
thread with the issue you're hitting, including versions and all error
output? That'll help keep discussion focused on your problem, and help us
offer recommendations.
Thanks,
Christian
--
Christian Hammond
My original email was not very clear.
On my backup server I want to remove the 2.0RC2 installation and get a
1.7.x installation running.
However I removed all the RB2.0RC2 files and then dropped the reviewboard
table from mysql database.
I then did a clean installation of 1.7.25.
I then imported
All,
Due to various issue my development server has to be re-purposed as the
main server.
This has meant I have to revert from 2.0RC2 - 1.7.25 (the latest stable
version).
At this point I usually import the database and media files and all works
ok.
However I get the following:
Traceback
Hi Dan,
There are many reasons why a 2.0 database will not cleanly turn into a
1.7.x database. We stick certain data in new tables/columns that don't
exist in 1.7. We've migrated data from those older columns.
Django-Evolution has no concept of a downgrade and will likely just break
every future
