Review Board's treatment of repositories shouldn't have any influence on
how you choose to lay out your code within those repositories. Each
perforce server should be configured as a repository in review board, and
then any separate depots and directories within that server use that same
To the professionals who work with Review Board
I'm eager to get started with Review Board, but it's not working out of
the box. I have Fedora 20 installed, with RB 1.7.26 with httpd 2.4.10.
I can only work ReviewBoard if I turn off selinux, i.e. setenforce off.
We cannot do this on
On 08/21/2014 05:12 PM, Matthew Woehlke wrote:
On 2014-08-21 16:53, Tyler Mace wrote:
I'm eager to get started with Review Board, but it's not working out of the
box. I have Fedora 20 installed, with RB 1.7.26 with httpd 2.4.10.
I can only work ReviewBoard if I turn off selinux, i.e.
On 08/22/2014 07:04 AM, Cian Mc Govern wrote:
To the professionals who work with Review Board
I'm eager to get started with Review Board, but it's not working out
of the box. I have Fedora 20 installed, with RB 1.7.26 with httpd
2.4.10.
I can only work ReviewBoard if
On 22 August 2014 13:50, Stephen Gallagher step...@gallagherhome.com
wrote:
On 08/22/2014 07:04 AM, Cian Mc Govern wrote:
To the professionals who work with Review Board
I'm eager to get started with Review Board, but it's not working out
of the box. I have Fedora 20
I am attaching the result of audit2why.txt. This is great stuff, and
clarifies potential solutions. Phew!
But doing this on the .rpm or on the installer would be way more helpful.
Users like me have no knowledge of audit2why or audit2allow.
-Tyler
On Thursday, August 21, 2014 5:12:06 PM
Hi Franck,
Git has no form of fine-grained remote access for repositories, which Review
Board needs in order to fetch individual files, given a path and revision, for
display in the diff viewer. Because of this, you can’t just use a URL and have
things work. What you need instead is a piece of
