Re: ReviewBorad integration with ClearCase

On Fri, Feb 8, 2013 at 7:47 AM, Sateesh Hegde wrote: > I am new to reviewboard. Just installed 1.7. I have a ClearCase repository > and mostly we use dynamic views. Can it work with the remote clearcase view > host ? Or Does it require me to install the clearcase client on the hosting > machine ?

Re: Error on 1.5 -> 1.7.1 upgrade: Model 'reviews.FileAttachmentComment' already has a field named 'extra_data'

Hi Sebastien, I know I haven't gotten back to you on this. The problem is, I have absolutely no clue what the problem is. I've been spending time on trying to figure out how evolutions break and what to do about it, and it's very unclear what will cause that to go wrong. I'm digging in deep into

Re: Error on 1.5 -> 1.7.1 upgrade: Model 'reviews.FileAttachmentComment' already has a field named 'extra_data'

I have something I'd like you to check. If you still have this broken database, try: $ rb-site manage /path/to/site shell >>> from django_evolution.models import Evolution >>> print Evolution.objects.get(label='file_attachment_comment_extra_data') See if that prints something, or if

Re: Error on 1.5 -> 1.7.1 upgrade: Model 'reviews.FileAttachmentComment' already has a field named 'extra_data'

On Fri, Feb 8, 2013 at 10:12 AM, Christian Hammond wrote: > See if that prints something, or if it errors. $ rb-site manage /srv/reviewboard shell Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48) [GCC 4.4.5] on linux2 Type "help", "copyright", "credits" or "license" for more information. (Interac

Re: Error on 1.5 -> 1.7.1 upgrade: Model 'reviews.FileAttachmentComment' already has a field named 'extra_data'

On Fri, Feb 8, 2013 at 9:52 AM, Christian Hammond wrote: > Hi Sebastien, Hi Christian > > I know I haven't gotten back to you on this. The problem is, I have > absolutely no clue what the problem is. Sad. > I'm digging in deep into django_evolution to see if anything stands out. I > have a repr

Cannot post-review using API with LDAP user on 1.7.4

This user is Staff and Admin, but is an LDAP user. User can authenticate to the web pages and perform all actions there. He cannot use the post-review client to post a review, getting HTTP/403, API/101: % post-review --debug -o >>> RBTools 0.4.3 >>> Python 2.7.2 (default, Oct 11 2012, 20:14:37

Re: Error on 1.5 -> 1.7.1 upgrade: Model 'reviews.FileAttachmentComment' already has a field named 'extra_data'

On Feb 8, 2013, at 7:16, Sebastien Douche wrote: > On Fri, Feb 8, 2013 at 9:52 AM, Christian Hammond wrote: >> Hi Sebastien, > > Hi Christian >> >> I know I haven't gotten back to you on this. The problem is, I have >> absolutely no clue what the problem is. > > Sad. > >> I'm digging in de

RB Server has many errors after upgrade

Hi, RB Server has been updated but many errors found: Upgrading site settings_local.py Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- -- Creating tables ... Creating table e

error 500 after running update

Hi. I have run the command easy_install -U ReviewBoard and it has broken the server. I have restarted Apache and still no joy. I was running 1.6.14 and the upgrade should have taken this to the current version. Can anyone help in re-establishing the server please? Thanks, Clive. -- W

Re: RB Server has many errors after upgrade

Hi Clive, You're suffering from a problem that has been some users. (Btw, you seem to have pasted the error output in your terminal and then pasted that to us, so there's a false sense of some of the errors.) Please do the following: 1) Back up your database, completely. 2) Run: $ rb-site

Re: Cannot post-review using API with LDAP user on 1.7.4

This has come up on occasion with LDAP, but we've never been able to track down the cause. Can you check your reviewboard.log file for any messages around the time of a post? Christian On Feb 8, 2013, at 10:14, Liam Reimers wrote: > This user is Staff and Admin, but is an LDAP user. User ca

Re: Can I archive ancient reviews?

Here's how I did it: 1) I created a brand new instance of ReviewBoard, updated to the latest version. Set that up and developers started using it. 2) based on a reply from this list (thanks again), I iterated over the review id (check the URL for it) and used wget to retrieve the individual review

Re: Cannot post-review using API with LDAP user on 1.7.4

Just this: 2013-02-07 22:44:04,478 - DEBUG - Attempting authentication on API for user On Friday, February 8, 2013 12:14:44 PM UTC-8, Christian Hammond wrote: > > This has come up on occasion with LDAP, but we've never been able to track > down the cause. > > Can you check your reviewboard.log

Re: error 500 after running update

Hi there Clive, I am not an expert but trying to share my experience. Did you take a back up of your ReviewBoard before the upgrade. Below are the steps I followed and our ReviewBoard test upgrade was successful. I think you have to do the 'rb-site upgrade' after 'easy_install -U ReviewBoard'.