Hi Christian,
Using the below command for upgrade, upgrades to the latest version (1.5.3)
by default. Is there a way we can upgrade to an older version we prefer ?
Like for example, we want to do install to RB1.5.1. Is it possible ?
easy_install -U ReviewBoard
Also, from the releas
Hi Sapna,
Going back to 1.5.1 from 1.5.3 unfortunately means removing the old version
from the filesystem manually. At that point you can do:
easy_install -U ReviewBoard==1.5.1
However, this won't fix the errors below. Those appear to me to be harmless.
Are you hitting any real problems with
Thanks Christian.
If the errors are just warnings, the issue is that we don't see a complete
installation and upgrade. The RB servers still shows as 1.0.X. and not
1.5.3.
Do you know how I could locate: cmemcache on the file system ?
Thanks,
Sapna
On Fri, Feb 11, 2011 at 12:39 PM, Christian H
Hi Sapna,
Review Board is going to show the version of the Review Board code being run
in the Python interpreter for your site. This should be the latest version.
If it's showing 1.0.x, then it sounds like either Review Board 1.5.x wasn't
installed, or it's installed in some non-standard location
Hi Christian,
We used "easy_install -U ReviewBoard"
Thanks,
Sapna
On Sat, Feb 12, 2011 at 12:33 AM, Christian Hammond wrote:
> Hi Sapna,
>
> Review Board is going to show the version of the Review Board code being
> run in the Python interpreter for your site. This should be the latest
> versio
The thing to check, then, is that you don't have multiple versions of Python
with different versions of Review Board installed.
Search the filesystem for ReviewBoard*.egg, and see what directories you
find. Look at the Python directories they're in. Make sure they're all the
Python version you ex
Hi!
We are currently on 1.7.14 and I am looking to upgrade us to 2.0.2.
I've tried 3 paths to upgrade (all following the RB instructions - upgrade
RB, upgrade site, restart apache and memcached):
1.7.14 -> 2.0.2
1.7.14 -> 1.7.26 -> 2.0.2
1.7.14 -> 2.0.1 -> 2.0.2
*I didn't go from 1.7.14 to
What about the apache error logs?
-David
> On Jun 27, 2014, at 8:24 AM, sagar wrote:
>
> Hi!
>
> We are currently on 1.7.14 and I am looking to upgrade us to 2.0.2.
>
> I've tried 3 paths to upgrade (all following the RB instructions - upgrade
> RB, upgrade site, restart apache and memcached
There are three log files for apache:
*other_vhosts_access.log*:
codereview.nyab-tds:80 149.244.179.118 - - [27/Jun/2014:19:03:44 +] "-"
> 408 0 "-" "-"
> codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +]
> "GET /dashboard/ HTTP/1.1" 200 4318 "http://codereview.nyab-td
It looks like your table charsets aren't set properly in MySQL. I'd go in with
the MySQL client and set them all to utf-8.
-David
> On Jun 27, 2014, at 12:08 PM, sagar wrote:
>
> There are three log files for apache:
>
> other_vhosts_access.log:
>
>> codereview.nyab-tds:80 149.244.179.118 -
I hadn't change anything in mysql, so that's weird.
I'll try this and post in a bit.
On Friday, 27 June 2014 15:01:43 UTC-5, David Trowbridge wrote:
> It looks like your table charsets aren't set properly in MySQL. I'd go in
> with the MySQL client and set them all to utf-8.
>
> -David
>
> On Ju
So I changed my.cnf and set the default character set to utf8.
the apache log still shows:
codereviewtest.nyab-tds:80 127.0.0.1 - - [30/Jun/2014:20:01:32 +] "GET
/admin/ HTTP/1.1" 500 551 "-" "Mozilla/5.0 (X11; Ubuntu; Linux i686;
rv:24.0) Gecko/20100101 Firefox/24.0"
On Monday, 30 Jun
The my.cnf settings affect new databases and tables. You'll also need to
run some commands in the console to change the existing tables.
-David
On Mon, Jun 30, 2014 at 1:50 PM, sagar wrote:
>
> So I changed my.cnf and set the default character set to utf8.
>
> the apache log still shows:
>
> c
13 matches
Mail list logo
