This fixed it. Thanks!
On Jun 19, 3:41 am, Christian Hammond wrote:
> In the meantime, good news! There is a fix. If you can reach the Django
> admin UI, go into the Database -> Django Evolutions -> Versions area and
> delete the "Hinted version" you have there. Then repeat the rb-site
> upgrade
Hi Christian,
Here are the results from my particular case ( for both dump and rb_site
manage evolve -- --hint ):
1) mysqldump of django_evolution table
Note that there are no other tables in mysql that starts with
django_evolution in the reviewboard database ( see "show tables" output
below
Can you also show me:
rb-site manage /path/to/site evolve -- --hint
(Note the double --)
Christian
On Jun 18, 2012, at 10:54, TP wrote:
> Got the same issue with 1.6.7.1 to 1.6.9
>
> # rb-site upgrade /var/www/site
> Rebuilding directory structure
> Updating database. This may take a wh
If you can give me an SQL dump if the django_evolution_* tables, that would
help me diagnose.
Christian
On Jun 18, 2012, at 3:07, jms wrote:
>
> What can / should I do next ?
>
>
> On Friday, June 15, 2012 7:46:00 PM UTC+10, jms wrote:
>
> Oh sorry ... I can see I have django-evolution a
Can you provide me with an SQL dump of the django_evolution_* tables?
Christian
On Jun 18, 2012, at 10:54, TP wrote:
> Got the same issue with 1.6.7.1 to 1.6.9
>
> # rb-site upgrade /var/www/site
> Rebuilding directory structure
> Updating database. This may take a while.
> Creating tables .
Got the same issue with 1.6.7.1 to 1.6.9
# rb-site upgrade /var/www/site
Rebuilding directory structure
Updating database. This may take a while.
Creating tables ...
Upgrading Review Board from 1.6.7.1 to 1.6.9
Project signature has changed - an evolution is required
Installing custom SQL ...
Inst
What can / should I do next ?
On Friday, June 15, 2012 7:46:00 PM UTC+10, jms wrote:
>
>
> Oh sorry ... I can see I have django-evolution at django-evolution==0.6.6.
> I did not see that earlier as I was looking at what's just on top or just
> below the line "Django==1.3.1".
>
> Can I just ins
Can you tell me what version of django-evolution is installed?
What version of RB did you start with?
Christian
On Jun 14, 2012, at 22:20, jms wrote:
> Hi,
>
> I got the same or similar problem when upgrading reviewboard site ( rb-site
> upgrade ) from 1.6.7.1 to 1.6.9.
>
> easy_install wo
Hi,
I got the same or similar problem when upgrading reviewboard site ( rb-site
upgrade ) from 1.6.7.1 to 1.6.9.
easy_install worked OK, but it was rb-site upgrade that failed:
# easy_install -U ReviewBoard
Searching for ReviewBoard
Reading http://pypi.python.org/simple/ReviewBoard/
Reading htt
On Tuesday, 12 June 2012 10:59:38 UTC+2, Christian Hammond wrote:
Was there ever any point that you manually ran an evolve command prior to
> this? Or any point where you've hand-modified the database, either through
> MySQL or through the Database viewer in the admin UI?
>
If I recall correct
Hi,
Ignore the "manage.py evolve" thing. That's the underlying evolution
logging complaining, and rb-site does that automatically.
Here's what concerns me about the errors you're seeing.
Each of those fields it complains about was available in 1.6.0. Actually,
in the betas. So your database is i
11 matches
Mail list logo
