Re: Review Board version mismatch

2013-12-06 Thread tu1953
I'm having this same error trying to upgrade 1.6.15 to 1.7.19 on Redhat. In the error logs I get the message that [Fri Dec 06 14:03:06 2013] [error] [client 192.168.168.22] File does not exist: /var/www/html/rbtesting/htdocs/media/rb Reviewboard isn't upgrading the site correctly I downloaded

Re: Review Board version mismatch

2013-12-06 Thread Christian Hammond
SVN trunk is many years old. You won't find anything modern there. How did you install Review Board? It's quite likely the version of Python you used to install Review Board and the version Apache is using are different as well. Christian -- Christian Hammond - chip...@chipx86.com Review Board

Re: Review Board version mismatch

2013-12-06 Thread Ian
Hey, I originally installed Reviewboard using an egg to get a certain version to migrate an existing Reviewboard server to our new one. Now we need to upgrade the new servers Reviewboard version. I've tried using the easy_install -U upgrade way. I've tried installing manually from a tar.gz fil

Re: Review Board version mismatch

2013-12-06 Thread Christian Hammond
Hi Ian, Can you define "nothing happens?" It should at least output something. You shouldn't be touching anything under htdocs. That's rb-site's playground, and it will maintain it appropriately. The problem you're having more than likely is a difference between the version of Python used on the

Re: Review Board version mismatch

2013-12-06 Thread Ian
I shouldn't say nothing happens. It goes through and says that the upgrade was successful, the DB was upgraded successfully. It prompts me to adjust the apache config to add the following - SetHandler None Alias Static /var/www/html/reviewboard/htdocs/media/static Then to do rb-site manage

Re: Review Board version mismatch

2013-12-06 Thread David Trowbridge
That find command will only find things named "ReviewBoard1.6.15". I'd suggest something like: find / -name ReviewBoard\*.egg -type d -David On Fri, Dec 6, 2013 at 8:50 PM, Ian wrote: > I shouldn't say nothing happens. It goes through and says that the upgrade > was successful, the DB was up