I wanted to thank you for the summary of all the problems you hit. I'm
putting out a release right now that should solve these issues for new
upgrades. At least some good came out of the upgrade headache :/
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Dec 18, 2012 at 2:17 PM, Christian Hammond <chip...@gmail.com>wrote:
> Hi Jeff,
> I'm really sorry about that and I wish it could have been smoother.
> The static media change was forced on us by Django. The upgrade script
> couldn't make the necessary changes, due to both not knowing the right
> details during upgrade and the variety of server configurations. I tried to
> make sure it explained the changes needed, and have it make sure you had to
> acknowledge before using the site again on order to be sure changes were
> made. I guess the Location stuff was missing. Sorry about that, and we'll
> get it into the next release. I'll also document it today.
> We perform database config upgrading, but my guess is maybe the old
> settings file didn't have something in an upgradable format that we'd
> recognize. I can work to make this smoother too, though I'd need to know
> more about when your settings_local.py file was created.
> I know it wasn't the smoothest upgrade, and I wish it worked better. We
> really fought to make Django's mandatory changes less of a pain, but there
> are things that just require manual intervention, and there are clearly
> corner cases. Believe me when I say, it could have been worse.
> All I can say is, we'll try to make this smoother for new users, write up
> some docs, and that the hard part is over. Future upgrades should work a
> lot better.
> On Dec 18, 2012, at 13:02, Jeff <jflamb...@newtrax.com> wrote:
> Love ReviewBoard but upgrading to 1.7 was a real pain.
> First I had to modify the database backend
> to django.db.backends.postgresql_psycopg2
> I'm far from a power python user so it took quite a bit of time to get
> this right.
> Then rb-site upgrade went through but with many red error messages that I
> unfortunately couldn't copy. No clear text instructions on the new media
> I got the same broken look as Joe Attardi, and the extra Location+Alias
> solved the issue.
> I was just following the regular update steps I've been doing for a year,
> last I checked they didn't change.
> As of now I'm up and running, but it took about an hour.
> On Tuesday, December 18, 2012 1:02:53 AM UTC-5, Christian Hammond wrote:
>> Hi Joe,
>> Sorry for the late response. Looks like gmail flagged this as spam. Odd.
>> You may need to add a <Location "/static"> that works just like the media
>> one. The static files are probably going through Review Board, which won't
>> know how to serve them.
>> As for the "Couldn't find manual update check" error, we just have a bug
>> where a second resolve-check prints that. I assume it worked the first time.
>> If the <Location> doesn't fix things, we'll do some debugging with your
>> setup and see what we can find.
>> Christian Hammond - chi...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> VMware, Inc. - http://www.vmware.com
>> On Mon, Dec 17, 2012 at 8:15 PM, Joe Attardi <jatt...@gmail.com> wrote:
>>> I updated my site to 184.108.40.206-py2.7 and I'm still getting 404 errors for
>>> anything under /static
>>> I added the alias for /static and restarted Apache 2, but it seems to
>>> have no effect. Am I missing something obvious?
>>> My Apache 2 configuration:
>>> <VirtualHost *:80>
>>> ServerName uxworks-reviewboard.mysite.com
>>> DocumentRoot "/var/www/uxworks-reviewboard/**htdocs"
>>> # Error handlers
>>> ErrorDocument 500 /errordocs/500.html
>>> # Serve django pages
>>> <Location "/">
>>> PythonPath "['/var/www/uxworks-**reviewboard/conf'] +
>>> SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings
>>> SetEnv PYTHON_EGG_CACHE "/var/www/uxworks-reviewboard/**
>>> SetEnv HOME "/var/www/uxworks-reviewboard/**data"
>>> SetHandler mod_python
>>> PythonHandler django.core.handlers.modpython
>>> PythonAutoReload Off
>>> PythonDebug Off
>>> # Used to run multiple mod_python sites in the same
>>> PythonInterpreter reviewboard_uxworks-**reviewboard
>>> # Serve static media without running it through mod_python
>>> # (overrides the above)
>>> <Location "/media">
>>> SetHandler None
>>> <Location "/errordocs">
>>> SetHandler None
>>> <Directory "/var/www/uxworks-reviewboard/**htdocs">
>>> AllowOverride All
>>> # Alias static media requests to filesystem
>>> Alias /media "/var/www/uxworks-reviewboard/**htdocs/media"
>>> Alias /errordocs "/var/www/uxworks-reviewboard/**
>>> Alias /static "/var/www/uxworks-reviewboard/**htdocs/static"
>>> I tried running rb-site manage /var/www/uxworks-reviewboard
>>> resolve-check static-media but it gave me an error: Couldn't find
>>> manual update check 'static-media'
>>> Any help would be appreciated. Thanks!
>>> Want to help the Review Board project? Donate today at
>>> Happy user? Let us know at
>>> To unsubscribe from this group, send email to reviewboard...@**
>>> For more options, visit this group at http://groups.google.com/**
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at