Yes. And I agree. :)
- sent from my Galaxy Nexus Android phone.
On Jun 18, 2012 3:23 PM, "Christian Hammond" wrote:
> Ah, that makes sense.
>
> Was that the only option you needed then? It'd be nice to have some docs
> on this somewhere.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx8
Ah, that makes sense.
Was that the only option you needed then? It'd be nice to have some docs on
this somewhere.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Jun 18, 2012 at 4:51 AM, Dan Dumont wr
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
Could you try just repo-url:/path/to/repo for the 'Path:' field and
username, password on the respective fields and update this thread, thanks.
On Saturday, June 16, 2012 3:45:51 AM UTC-5, Augba wrote:
>
> I too facing the same issue. Please let me know if you have the steps
> working.
>
> On F
I set https, but it never seemed to stick.
Not sure if you've ever tested this deployment, but our server sits behind
a reverse proxy and ssl is terminated at the proxy, so the review site
machine never gets requests in on https.
It always sees http, and I think that's what's confusing whatever is
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
Hi Dan,
Glad you got it working. I haven't really been available much this weekend.
Thanks for the bug report. Should be an easy fix. However, I haven't seen
that or the need for the SetEnv come up yet. Does your Server URL in the
admin settings page use https or http? Setting that to https *shou
10 matches
Mail list logo
