Hi Christian, Thanks for the quick reply. I tried taking applying the fix you mentioned and it allowed the db migration to go through. I'm getting two small errors now, which I'm not sure if it's related to the fix or not. The first is:
[Tue Aug 13 18:28:13 2013] [error] File "/usr/lib64/python2.6/logging/__init__.py", line 779, in emit [Tue Aug 13 18:28:13 2013] [error] msg = self.format(record) [Tue Aug 13 18:28:13 2013] [error] File "/usr/lib64/python2.6/logging/__init__.py", line 657, in format [Tue Aug 13 18:28:13 2013] [error] return fmt.format(record) [Tue Aug 13 18:28:13 2013] [error] File "/usr/lib64/python2.6/logging/__init__.py", line 442, in format [Tue Aug 13 18:28:13 2013] [error] s = self._fmt % record.__dict__ [Tue Aug 13 18:28:13 2013] [error] KeyError: 'request_info' which occurs when clicking around the ui on things like All Review Requests. The other error happens when trying to load the admin page for adding new groups and adding new repositories. The page freezes because /static/admin/js/SelectBox.37509c7e5ad5.js:16 becomes unresponsive. On Monday, August 12, 2013 11:25:38 AM UTC-7, Christian Hammond wrote: > > It should be this week. We've been working on a couple other changes that > needed to go in, and the last of it are up for review now. > > You can also try applying this patch: > https://reviews.reviewboard.org/r/4420/ > > Christian > > -- > Christian Hammond - chi...@chipx86.com <javascript:> > Review Board - http://www.reviewboard.org > Beanbag, Inc. - http://www.beanbaginc.com > > > On Mon, Aug 12, 2013 at 10:59 AM, Alvin .Feng <alvin...@yahoo.com<javascript:> > > wrote: > >> Hi Christian, >> >> Thanks for the response. Is there any updates or eta on the fix yet? >> >> Thanks, >> Alvin >> >> >> On Tuesday, August 6, 2013 2:05:43 AM UTC-7, Christian Hammond wrote: >> >>> Hi Alvin, >>> >>> This was reported recently, and I've been trying to figure out the best >>> course of action. I expect to put out a release later this week with a fix. >>> I recommend sticking to 1.5 for now, and upgrading once the new 1.7 is out. >>> >>> Christian >>> >>> -- >>> Christian Hammond - chi...@chipx86.com >>> >>> Review Board - http://www.reviewboard.org >>> Beanbag, Inc. - http://www.beanbaginc.com >>> >>> >>> On Mon, Aug 5, 2013 at 6:52 PM, Alvin .Feng <alvin...@yahoo.com> wrote: >>> >>>> Hi there, >>>> >>>> I currently have a Review Board 1.5 setup, and I'm trying to upgrade to >>>> 1.7. When I try to run the rb-site upgrade part to upgrade the database, I >>>> get the following error: >>>> >>>> File "lib64/reviewboard/MySQL_**python-1.2.4-py2.6-linux-x86_** >>>> 64.egg/MySQLdb/connections.py"**, line 36, in defaulterrorhandler >>>> raise errorclass, errorvalue >>>> django.db.utils.DatabaseError: (1071, 'Specified key was too long; max >>>> key length is 1000 bytes') >>>> >>>> I think the sql statement it is trying to execute is: >>>> >>>> CREATE TABLE `hostingsvcs_**hostingserviceaccount` ( >>>> `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY, >>>> `service_name` varchar(128) NOT NULL, >>>> `hosting_url` varchar(255), >>>> `username` varchar(128) NOT NULL, >>>> `data` longtext NOT NULL, >>>> `visible` bool NOT NULL, >>>> `local_site_id` integer, >>>> UNIQUE (`service_name`, `hosting_url`, `username`, `local_site_id`) >>>> ) >>>> ; >>>> >>>> I clean install reviewboard 1.7 on one host, and I try to connect it to >>>> the db host that was running with 1.5. Is there a way to just migrate the >>>> mysql db across versions? Any help would be appreciated. Thanks. >>>> >>>> -- >>>> Want to help the Review Board project? Donate today at >>>> http://www.reviewboard.org/**donate/<http://www.reviewboard.org/donate/> >>>> Happy user? Let us know at >>>> http://www.reviewboard.org/**users/<http://www.reviewboard.org/users/> >>>> -~----------~----~----~----~--**----~----~------~--~--- >>>> To unsubscribe from this group, send email to reviewboard...@** >>>> googlegroups.com >>>> >>>> For more options, visit this group at http://groups.google.com/** >>>> group/reviewboard?hl=en<http://groups.google.com/group/reviewboard?hl=en> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "reviewboard" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to reviewboard...@**googlegroups.com. >>>> >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>>> >>>> >>> >>> -- >> Want to help the Review Board project? Donate today at >> http://www.reviewboard.org/donate/ >> Happy user? Let us know at http://www.reviewboard.org/users/ >> -~----------~----~----~----~------~----~------~--~--- >> To unsubscribe from this group, send email to >> reviewboard...@googlegroups.com <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/reviewboard?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "reviewboard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to reviewboard...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
