Re: Enable a use to mark other users' requests as submitted

I double checked this and Can change status does in fact enable to mark other users' requests as submitted. Clemens On 8 Feb 2011, at 00:23, Christian Hammond wrote: Hi, The Can change status should definitely be it. I didn't see anything requiring staff access, but maybe. Can you file

Re: Problem posting diff

Hi Jerry, Have you tried post-review or hg post-review? Can you try these (with debug mode on, which is --debug on post-review at least, dunno about hg post-review) and see if you still hit this problem? If so, the debug log would be helpful in identifying the problem. Christian -- Christian

Re: Problem posting diff

Thanks, Christian. I had tried hg postreview from mdelagra's fork (https://bitbucket.org/mdelagra/mercurial-reviewboard) first, and was unsuccessful, so I went to the GUI to try to eliminate that as a culprit. Is this the tool you are referring to? Here is the --debug result from that (I added

post-review with git-svn parent throwing error

Hi everyone, I'm working with git-svn and the post-review command is failing when working on branches. I'm using the --parent and there are differences between the branches and the master. My repo is like this: * master - The one that fetches from svn trunk mockito_refactor - Branched from

Issue Upgrading.

Hi Christian, Using the below command for upgrade, upgrades to the latest version (1.5.3) by default. Is there a way we can upgrade to an older version we prefer ? Like for example, we want to do install to RB1.5.1. Is it possible ? easy_install -U ReviewBoard Also, from the

Re: Issue Upgrading.

Hi Sapna, Going back to 1.5.1 from 1.5.3 unfortunately means removing the old version from the filesystem manually. At that point you can do: easy_install -U ReviewBoard==1.5.1 However, this won't fix the errors below. Those appear to me to be harmless. Are you hitting any real problems

Re: unable to save seach index path

My apologies, this wasn't sufficient due to another bug where it doesn't even save the entry. I've put out a hot-fix release (1.5.3.1) which you should be able to upgrade to in the normal manner. It will fix this. Christian -- Christian Hammond - chip...@chipx86.com Review Board -

Re: post-review with git-svn parent throwing error

Can you run with --output-diff and see if it gives you anything useful? Also with --debug to see which commands it executes. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Fri, Feb 11, 2011 at 9:55 AM,

Re: post-review with git-svn parent throwing error

Well, I started with two new branches, topic_a and topic_b, to avoid any commit interference The work was: $ git checkout -b topic_a $ vim doc/AUTHORS.rst $ commit $ git checkout -b topic_b $ vim doc/INSTALL.rst $ commit $ git checkout topic_a $ post-review --guess-summary --guess-description

Re: Problem posting diff

A 500. Interesting... So it's more than just a matter of not finding the right path in the repository. What version of Review Board is this? Can you enable logging on the Review Board end, repeat the process, and then find the accompanying error for this in the reviewboard.log file? Christian

Re: Problem posting diff

ReviewBoard version 1.5.3. I notice that for the review requests created by RBTools post-review, if I go to the web UI and try to select the review request, I also get a 500 error in my browser. OK, so here is the full output in reviewboard.log for a post-review command: - 2011-02-11

Re: Problem posting diff

Are you using a fully-qualified domain for the path, or just scm or something? It may matter. Also, try cloning the repository using that path on your server, just to see what happens. I assume you have an SSH key uploaded. Can you verify it's the right one in the Admin UI? Christian --

Re: Problem posting diff

Are you using a fully-qualified domain for the path, or just scm or something? It may matter. I was just using scm. I just put in the fully-qualified path and will try again (see below.). Also, try cloning the repository using that path on your server, just to see what happens. I am able to

Re: Issue Upgrading.

Thanks Christian. If the errors are just warnings, the issue is that we don't see a complete installation and upgrade. The RB servers still shows as 1.0.X. and not 1.5.3. Do you know how I could locate: cmemcache on the file system ? Thanks, Sapna On Fri, Feb 11, 2011 at 12:39 PM, Christian

Issue 1981 in reviewboard: Can't save General Settings after upgrade from 1.5.2

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1981 by bra...@gmail.com: Can't save General Settings after upgrade from 1.5.2 http://code.google.com/p/reviewboard/issues/detail?id=1981 What version are you running? 1.5.3, upgraded from 1.5.2 What's the URL of the page

Issue 1982 in reviewboard: HTTP 500 viewing graphics review with bug number (RB 1.5)

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1982 by enqueu...@gmail.com: HTTP 500 viewing graphics review with bug number (RB 1.5) http://code.google.com/p/reviewboard/issues/detail?id=1982 * NOTE: Do not post confidential information in this bug report. * *

Re: Issue 1982 in reviewboard: HTTP 500 viewing graphics review with bug number (RB 1.5)

Updates: Status: Confirmed Labels: -Priority-Medium Priority-Critical Milestone-Release1.5.x Comment #1 on issue 1982 by chip...@gmail.com: HTTP 500 viewing graphics review with bug number (RB 1.5) http://code.google.com/p/reviewboard/issues/detail?id=1982 We'll fix for

Re: Issue 1980 in reviewboard: User names with ' in the name don't display correctly when adding comment

Updates: Status: Confirmed Labels: Milestone-Release1.5.x Component-Reviews Comment #1 on issue 1980 by chip...@gmail.com: User names with ' in the name don't display correctly when adding comment http://code.google.com/p/reviewboard/issues/detail?id=1980 (No comment was