Re: Failed upgrade to RC2

2011-07-29 Thread Christian Hammond
I have a script now that can simulate various database upgrade scenarios, and have spent lots of time with it now. I've yet to be able to reproduce this. I've tried sqlite and MySQL, Python versions 2.4 through 2.6, and various combinations of Review Board versions. I am curious about the Hinted

Re: Failed upgrade to RC2

2011-07-29 Thread Tucker
I don't quite think I'm groking your request. You want screen caps of Home › Django_evolution › Versions › Hinted version, updated on 2011-06-30 20:16:00 and Home › Django_evolution › Versions › Stored version, updated on 2011-06-30 20:16:00? I just looked at those and they look rather

Upgrading from 1.6RC1 to 1.6RC2: There are unapplied evolutions for diffviewer.

2011-07-29 Thread Joe Lencioni
I just upgraded from 1.6RC1 to 1.6RC2 and when I ran rb-site upgrade, I got the following output: Rebuilding directory structure Updating database. This may take a while. Creating tables ... Upgrading Review Board from 1.6 RC1 to 1.6 RC2 There are unapplied evolutions for diffviewer. Installing

Re: Failed upgrade to RC2

2011-07-29 Thread Christian Hammond
For the screenshots, I was interested in a field that it turns out isn't shown in the admin UI. So nevermind on that. Feel free to send the raw dumps to me directly. They don't contain any identifying information, just database table schema data, but no need to attach them publicly either.

Re: Upgrading from 1.6RC1 to 1.6RC2: There are unapplied evolutions for diffviewer.

2011-07-29 Thread Christian Hammond
Hi Joe, Nothing in there looks problematic to me. What concerned you? Just things like No fixtures found and There are unapplied evolutions? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Fri, Jul 29,

Re: Upgrading from 1.6RC1 to 1.6RC2: There are unapplied evolutions for diffviewer.

2011-07-29 Thread Joe Lencioni
Specifically There are unapplied evolutions for diffviewer. It appeared in a red color which made me think it might be a problem. On Fri, Jul 29, 2011 at 3:51 PM, Christian Hammond chip...@chipx86.com wrote: Hi Joe, Nothing in there looks problematic to me. What concerned you? Just things

Re: Upgrading from 1.6RC1 to 1.6RC2: There are unapplied evolutions for diffviewer.

2011-07-29 Thread Christian Hammond
Yeah, that's just a third-party thing. At that point in the process, we've done a database sync, and we found out that an evolution needed to be applied. The Evolutions were successful below indicates that when we got to that point in the process, it went fine. Maybe I can get a patch in to

Re: Issue 2195 in reviewboard: Perforce support is broken with Python 2.4 in RC2

2011-07-29 Thread reviewboard
Updates: Status: PendingReview Owner: chip...@gmail.com Comment #1 on issue 2195 by chip...@gmail.com: Perforce support is broken with Python 2.4 in RC2 http://code.google.com/p/reviewboard/issues/detail?id=2195 (No comment was entered for this change.) -- You received this

Re: Issue 2154 in reviewboard: Published comments include every edited version instead of the latest one.

2011-07-29 Thread reviewboard
Updates: Owner: chip...@gmail.com Comment #9 on issue 2154 by chip...@gmail.com: Published comments include every edited version instead of the latest one. http://code.google.com/p/reviewboard/issues/detail?id=2154 (No comment was entered for this change.) -- You received this

Re: Issue 2002 in reviewboard: linkified URL has succeeding parenthesis included in link's target URL

2011-07-29 Thread reviewboard
Updates: Labels: -Milestone-Release1.6 Milestone-Release1.6.x Comment #7 on issue 2002 by chip...@gmail.com: linkified URL has succeeding parenthesis included in link's target URL http://code.google.com/p/reviewboard/issues/detail?id=2002 (No comment was entered for this change.) --

Re: Issue 2186 in reviewboard: Upgrading site on 1.6 RC2 gives evolution errors

2011-07-29 Thread reviewboard
Comment #5 on issue 2186 by chip...@gmail.com: Upgrading site on 1.6 RC2 gives evolution errors http://code.google.com/p/reviewboard/issues/detail?id=2186 I have spent a considerable amount of time on this and can't find anything on our end that could cause it. I have a new script that can

Issue 2199 in reviewboard: Perforce connection is broken in case of using a password 1.6rc2

2011-07-29 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2199 by faller.g...@gmail.com: Perforce connection is broken in case of using a password 1.6rc2 http://code.google.com/p/reviewboard/issues/detail?id=2199 * NOTE: Do not post confidential information in this bug report. *

Re: Issue 2195 in reviewboard: Perforce support is broken with Python 2.4 in RC2

2011-07-29 Thread reviewboard
Comment #2 on issue 2195 by greg.es...@gmail.com: Perforce support is broken with Python 2.4 in RC2 http://code.google.com/p/reviewboard/issues/detail?id=2195 I think this issue may be what is causing the following error when I try to bring up the add repository page. = [[ stack

Re: Issue 2195 in reviewboard: Perforce support is broken with Python 2.4 in RC2

2011-07-29 Thread reviewboard
Comment #3 on issue 2195 by chip...@gmail.com: Perforce support is broken with Python 2.4 in RC2 http://code.google.com/p/reviewboard/issues/detail?id=2195 Tonight's nightly build will have the fix. -- You received this message because you are subscribed to the Google Groups