Comment #9 on issue 1545 by gavin.mc...@gmail.com: Upgrade from 1.0.5.1 to
1.5beta1 fails evolution
http://code.google.com/p/reviewboard/issues/detail?id=1545
Yeah, I can't say that I've tried to get that working.
One thing that strikes me as possible is to repeat the process of generating
Comment #5 on issue 1545 by yanghatespam: Upgrade from 1.0.5.1 to 1.5beta1
fails evolution
http://code.google.com/p/reviewboard/issues/detail?id=1545
Thanks, Gavin - manually generating and running the evolution SQL also
worked for me.
--
You received this message because you are
Comment #3 on issue 1545 by gavin.mcquillan: Upgrade from 1.0.5.1 to
1.5beta1 fails evolution
http://code.google.com/p/reviewboard/issues/detail?id=1545
I'm also having this problem upgrading from the 1.0.X series to 1.5 stable.
Running postgres 8.3, django 1.2.3. Is there a simple fix for
Comment #4 on issue 1545 by gavin.mcquillan: Upgrade from 1.0.5.1 to
1.5beta1 fails evolution
http://code.google.com/p/reviewboard/issues/detail?id=1545
Okay -- update -- I got it working by manually running the migration.
Basically, I symlinked my local_settings.py into the reviewboard egg
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 1545 by Karrde712: Upgrade from 1.0.5.1 to 1.5beta1 fails
evolution
http://code.google.com/p/reviewboard/issues/detail?id=1545
*NOTE: Do not post confidential information in this bug report.*
What version are you running?
Comment #1 on issue 1545 by Karrde712: Upgrade from 1.0.5.1 to 1.5beta1
fails evolution
http://code.google.com/p/reviewboard/issues/detail?id=1545
My suspicion is that I'm hitting this bug from Django/PostgreSQL:
http://code.google.com/p/django-evolution/issues/detail?id=74
--
You received
