On 28 May 2014 21:07, Stephen Gallagher step...@gallagherhome.com wrote:
On 05/26/2014 09:31 PM, Christian Hammond wrote:
Hi everyone,
Review Board 2.0.1 is out. It fixes a number of bugs that have been
reported to us since last week's 2.0 release.
A big thanks to everyone who's
On 29 May 2014 19:24, Stephen Gallagher step...@gallagherhome.com wrote:
On 05/29/2014 07:19 AM, Cian Mc Govern wrote:
On 28 May 2014 21:07, Stephen Gallagher step...@gallagherhome.com
mailto:step...@gallagherhome.com wrote:
On 05/26/2014 09:31 PM, Christian Hammond wrote:
Hi
Thanks Stephen!
I've attempted to install this in the CentOS 7 Docker container and I hit
the following dependency issues:
Error: Package: ReviewBoard-2.0.5-1.el7.1.noarch (epel)
Requires: httpd = 2.4.7-5
Available: httpd-2.4.6-17.el7.centos.1.x86_64 (base)
On 18 August 2014 14:19, Stephen Gallagher step...@gallagherhome.com
wrote:
On 08/13/2014 04:47 AM, Stephen Gallagher wrote:
Crud; ok, I see the problem. Unfortunately I'm sitting in an airport
right now with insufficient Internet access to fix it. I'll try to get
it fixed up on Friday.
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 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
Hi,
There's a mistake in the ReviewBoard documentation here:
https://www.reviewboard.org/docs/manual/2.0/admin/configuration/repositories/#raw-file-urls
The gitweb url is incorrect and should be:
http://git.kernel.org/?p=bluetooth/bluez-gnome.git;a=blob_plain;f=
filename;h=revision
Instead of:
On 16 December 2015 at 20:02, Christian Hammond
wrote:
> That certainly shouldn't be necessary. Sounds like maybe there was a bad
> package?
>
> If it ever happens again, please let me know. I want to be sure we figure
> out what's causing that.
>
> Christian
>
> --
>
rsions so I run
it as part of my upgrade process for every version. I'll stop doing it if
it can cause issues though.
> On Tue, Dec 15, 2015 at 1:09 AM, Cian Mc Govern <c...@cianmcgovern.com>
> wrote:
>
>> On 4 December 2015 at 16:18, Stephen Gallagher <step...@gallagherhome.