Re: Digest for reviewboard@googlegroups.com - 16 updates in 3 topics
It is possible to get Review Board to work with a remote Git server, if the Git server also runs a web server. Write a CGI script that takes a repo name and SHA-1 checksum as parameters, chdir into the bare repo on the Git server, and run git cat-file blob SHA-1 using a text/plain content type. Then configure the repo in Review Board with a Raw file URL mask set to invoke the CGI script, hard-coding the repo name and replacing revision with the SHA-1 checksum. - If you drive fast enough, every traffic light turns green. Paul Sander Principal Member of Technical Staff, ScaleArc 2901 Tasman Dr., Santa Clara, CA 95054 paul.san...@scalearc.commailto:paul.san...@scalearc.com From: reviewboard@googlegroups.commailto:reviewboard@googlegroups.com reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Reply-To: reviewboard@googlegroups.commailto:reviewboard@googlegroups.com reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Date: Saturday, February 14, 2015 at 2:01 AM To: reviewboard@googlegroups.commailto:reviewboard@googlegroups.com reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Subject: Digest for reviewboard@googlegroups.commailto:reviewboard@googlegroups.com - 16 updates in 3 topics -Original Message- From: Liam Reimers liam.reim...@gmail.commailto:liam.reim...@gmail.com Reply: Liam Reimers liam.reim...@gmail.commailto:liam.reim...@gmail.com Date: February 13, 2015 at 1:22:57 PM To: reviewboard@googlegroups.commailto:reviewboard@googlegroups.com reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Cc: liam.reim...@gmail.commailto:liam.reim...@gmail.com liam.reim...@gmail.commailto:liam.reim...@gmail.com, christ...@beanbaginc.commailto:christ...@beanbaginc.com christ...@beanbaginc.commailto:christ...@beanbaginc.com Subject: Re: The specified diff file could not be parsed. Liam Reimers liam.reim...@gmail.commailto:liam.reim...@gmail.com: Feb 13 03:40PM -0800 Ah, I just saw part of your error: Not a git repository: 'None.' How is your repository configured in Review Board? Name - Repository Hosting - None (custom) Type - Git Path - git@server:path/repo.git However, note that the client can post a review request using one invocation (with HEAD~) and not the other, so it would seem that the repo is configured correctly? Christian Hammond christ...@beanbaginc.commailto:christ...@beanbaginc.com: Feb 14 12:26AM -0800 Unfortunately, that configuration can't work, unless there's also a raw file URL field that's filled out. Git's protocol has no ability to fetch the kind of information we need remotely, including individual files. For Git, it's a requirement to either host the repository on the Review Board server (or through something like an NFS mount), or to use a service like GitWeb. GitWeb is the recommended route right now (though we're working on a service to help make all this easier). If the other changes were successfully posting, my guess is that they were introducing new files, which doesn't require communication with the repository. Otherwise, there's no way that the file verification could have worked with a remote Git path. Christian -- Christian Hammond - christ...@beanbaginc.commailto:christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com -Original Message- From: Liam Reimers liam.reim...@gmail.commailto:liam.reim...@gmail.com Reply: Liam Reimers liam.reim...@gmail.commailto:liam.reim...@gmail.com Date: February 13, 2015 at 3:40:54 PM To: reviewboard@googlegroups.commailto:reviewboard@googlegroups.com reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Cc: liam.reim...@gmail.commailto:liam.reim...@gmail.com liam.reim...@gmail.commailto:liam.reim...@gmail.com, christ...@beanbaginc.commailto:christ...@beanbaginc.com christ...@beanbaginc.commailto:christ...@beanbaginc.com Subject: Re: The specified diff file could not be parsed. Back to top You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership pagehttps://groups.google.com/forum/?utm_source=digestutm_medium=email#!forum/reviewboard/join. To unsubscribe from this group and stop receiving emails from it send an email to reviewboard+unsubscr...@googlegroups.commailto:reviewboard+unsubscr...@googlegroups.com. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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.
Directory Permissions CodeReview Fedora Fresh Install
Just installed CodeReview on a Fedora AWS instance. And I'm getting the permissions problem issue splash page (The data directory must be writable by the web server. On Linux/Unix/Mac, you can fix this by typing:). But I think the permissions are set correctly. eg [fedora@ip-172-31-20-148 ~]$ sudo chown -R apache /var/www/reviews.example.com/data [fedora@ip-172-31-20-148 ~]$ ls -lh /var/www/reviews.example.com/data total 336K -rw-r--r--. 1 apache root 333K Feb 15 23:15 reviewboard.db [fedora@ip-172-31-20-148 ~]$ sudo service httpd restart Redirecting to /bin/systemctl restart httpd.service But the splash page isn't fixed. What else am I supposed to run? -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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.
Re: RBtools 0.7 - issue posting a review
After some investigation we found the following:
# TODO: This can break on systems that don't have the en_US local
# installed (which isn't very many). Ideally in this case, we could
# put something in the config file, but that's not plumbed through to here.
env['LC_ALL'] = 'en_US.UTF-8'
env['LANGUAGE'] = 'en_US.UTF-8'
We can confirm that it does break things!
With the 'en_US.UTF-8' locale installed the problem goes away - is there a
way to check this locale is installed and error nicely rather than breaking?
Cheers
Dan
On Saturday, 31 January 2015 18:49:02 UTC, David Trowbridge wrote:
Hi Daniel,
Do you think you could add some code to print out the contents of 'log'
inside _convert_symbolic_revision before we try to construct the etree?
Thanks,
-David
On Fri Jan 30 2015 at 4:48:37 AM Daniel Laird daniel@googlemail.com
javascript: wrote:
We have a shared Debian server and we have updated RBtools to 0.7.
When we try to post a review we get the following:
SERVER_NAME rbt post -d NUM
RBTools 0.7
Python 2.7.3 (default, Mar 13 2014, 11:03:55)
[GCC 4.7.2]
Running on Linux-3.2.0-4-amd64-x86_64-with-debian-7.8
Home = /v/home/rad/USERNAME
Current directory = /v/space/SERVER_NAME/USERNAME/
wc/memory_corruption
Checking for a Subversion repository...
Running: svn info --non-interactive
Running: diff --version
repository info: Path: https://SVN_SERVER/svn-restricted/PROJNAME,
Base path: /branches/users/bob/memory_corruption, Supports changesets:
False
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
HTTP GET request to http://REVIEWBOARD_SERVER/api/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/
HTTP GET request to http://REVIEWBOARD_SERVER/api/repositories/
cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/?max-results=25start=25
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/?max-results=25start=25 cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/1/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/1/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/2/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/2/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/3/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/3/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/4/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/4/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/5/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/5/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/6/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/6/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/7/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/7/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/8/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/8/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/9/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/9/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/10/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/10/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/11/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/11/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/12/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/12/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/13/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/13/info/ cannot be cached
Making HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/14/info/
HTTP GET request to http://REVIEWBOARD_SERVER/api/
repositories/14/info/ cannot be cached
repository info: Path: https://SVN_SERVER/svn-restricted/PROJNAME,
Base path: /branches/users/bob/memory_corruption, Supports changesets:
False
Running: svn log -r REVNUM -l 1 --xml
Traceback (most recent call last):
File /v/home/rad/USERNAME/.local/bin/rbt, line 9, in module
load_entry_point('RBTools==0.7', 'console_scripts', 'rbt')()
File /v/home/rad/USERNAME/.local/lib/python2.7/site-packages/
RBTools-0.7-py2.7.egg/rbtools/commands/main.py, line 133, in main
command.run_from_argv([RB_MAIN,
Re: Authentication failed while adding svn repository
Good day Alexis! Do you mind sharing the fix for this issue? You just downloaded version 2.0.5 and it worked? please do share the link thanks :) On Thursday, July 31, 2014 at 8:36:41 AM UTC+8, Alexis wrote: Hi Christian, It worked! No hitch. No need to install the patch. Thanks, Alexis On Wed, Jul 30, 2014 at 6:09 PM, Christian Hammond chri...@beanbaginc.com javascript: wrote: Hi Alexis, So, Review Board 2.0.2 is busted with SVN. That’s the primary cause of your problems. You need 2.0.3 or higher to have a working setup with a self-signed cert. (You should install 2.0.5 though.) When trying to verify the issue, though, I hit some other problems with accepting a certificate. I’ve attached a patch that should smooth out another rough edge (though I don’t believe it’s required for this case, but may help if you hit any errors with a newer release.) Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 30, 2014 at 3:09:37 PM, Alexis Denis (alexi...@gmail.com javascript:) wrote: Hi Christian, It is the original save: it fails even before asking to accept the SSL certificate (as mine is not signed by an authority, I have to accept it). Alexis On Wed, Jul 30, 2014 at 4:42 PM, Christian Hammond chri...@beanbaginc.com javascript: wrote: Hi Alexis, From the code I’m seeing, it does look like we’re passing in the credentials. I am, however, seeing that we don’t pass in credentials when confirming an HTTPS certificate. Is that the point where things go wrong, or is it on the initial save? Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 30, 2014 at 2:34:26 PM, Alexis Denis (alexi...@gmail.com javascript:) wrote: Christian: Personally, I am running ReviewBoard 2.0.2 and I believe I am using the default which is PySVN. I still think it's the wrapper tools trying to access the repository without a username or password at first. The setup is simple and easy to reproduce: VisualSVN server with no public access and a user. Holger: I am glad I am not the only one with this issue. I was starting to feel a little lonely. Glad to see you found your own workaround. Alexis On Wed, Jul 30, 2014 at 1:10 PM, Christian Hammond chi...@chipx86.com javascript: wrote: Hi, What version of Review Board? Are you using PySVN or Subvertpy? Christian On Wednesday, July 30, 2014, Holger hkr...@gmail.com javascript: wrote: My Workaround: I have the same problem but found a workaround inspired by Alexis' debug information: Add the new repository with Show this repository option unchecked. Afterwards got directly to the database and change the visible flag for the repository in the table scmtools_repository to 1. On Tuesday, July 8, 2014 11:25:40 AM UTC+2, shravanthi s wrote: Hi, I have installed Review Board 2.0.2 on RHEL 6.5 machine. I installed subversion 1.6.11 and pysvn version 1.7.8. However when i tried to add a repository, even though my login credentials are correct, am unable to add it. It gives an error 'Authentication failed' . So currently review board is unusable. The reviewboard log shows error as below ERROR - - SVN: Failed to get repository information for https://test.com/svn/myfolder/Phoenix: callback_get_login required Am not sure what is going wrong here. Anything to do with my pysvn version? -- 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. -- -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com -- 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 a topic in the Google Groups reviewboard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/reviewboard/r3Z_w3nJbkU/unsubscribe. To unsubscribe from this group and all its topics, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at
