I've tried to work around this problem so that I can evaluate the product. I created a local clone of the Mercurial repository and have added that to ReviewBoard instead of the kerberized remote one.
When I clone that repository, make a change, and try to create a review I get the following cryptic error message: pburka@reviewboard:~/repo$ rbt post --server=http://reviewboard.example.com/ ERROR: Error uploading diff The file was not found in the repository (HTTP 400, API Error 207) Your review request still exists, but the diff is not attached. There are no error messages in /var/log/apache2/error.log, and logs/reviewboard.log includes only the following messages: 2014-05-14 15:04:17,675 - DEBUG - - DiffParser.parse: Beginning parse of diff, size = 437 2014-05-14 15:04:17,675 - DEBUG - - DiffParser.parse: Finished parsing diff. 2014-05-14 15:04:17,715 - DEBUG - - Using rbssh for mercurial What does this error (207) mean? What is "the file" that the error message refers to? /peter On Monday, May 12, 2014 4:33:16 PM UTC-4, Peter Burka wrote: > > I've installed Reviewboard and configured it with a Mercurial repository > through the Admin dashboard. Our Mercurial servers use Kerberos > authentication, and not all users have access to all repositories. > > When I try to post a review, rbt reports: > > ERROR: Error uploading diff > > > > The file was not found in the repository (HTTP 400, API Error 207) > > Your review request still exists, but the diff is not attached. > > > And /var/log/apache2/error.log includes the following error: > > [Mon May 12 18:40:08 2014] [error] ERROR:root:HTTP error code 401 when > fetching file from > https://hg.example.com/repos/main/.../hg-history/344a0cddd514/.../Foo.java: > HTTP Error 401: Authorization Required > > > It appears that the Reviewboard server is attempting to contact the Hg > server through https, and that it's being denied. > > I'm surprised that the server is doing this - I would have expected the > client to be responsible for fetching the appropriate files so that the > user's permissions could be enforced. > > How can I configure Reviewboard so that this will work? Do I have to grant > the www-data user permission to read all of our Mercurial repositories? > Even if I do that, will reviewboard correctly negotiate with the server? > > -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- 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/d/optout.
