Hi Eric,
Yeah, it's cyclical. rbintegrations needs the Review Board source to build
(which is why Review Board does *not* depend on rbintegrations at `setup.py
develop` time), but we want to auto-install rbintegrations when installing
Review Board, which is why Review Board has a dependency on
Hi Stephen,
On Tue, Jun 4, 2019 at 1:12 PM Stephen Gallagher
wrote:
> On Tue, Jun 4, 2019 at 1:31 PM 'Eric Johnson' via Review Board
> Community wrote:
> > The one challenge I observed with the ReviewBoard packages was that
> rbintegrations included a small handfule of binary files that I
On Tue, Jun 4, 2019 at 1:31 PM 'Eric Johnson' via Review Board
Community wrote:
>
> Hi Christian,
>
> Thanks so much for the response! As near as I can tell, ReviewBoard "just
> works" for the teams that use it here, so we're grateful for the quality work.
>
> The issue appears to be solved at
Hi Christian,
Thanks so much for the response! As near as I can tell, ReviewBoard "just
works" for the teams that use it here, so we're grateful for the quality
work.
The issue appears to be solved at this point, and it looks like operator
error. More details below.
On Friday, May 31, 2019
Hi Eric,
Can you verify that rbintegrations was also packaged and that its extension
is enabled?
We really don't advise installing from our tarballs, as we build the eggs
and wheels with a particular setup to ensure they're packaged just right.
It is of course possible to build with tarballs,
Mostly, I've managed to get quite far with packaging ReviewBoard for Linux.
Although I don't know much about the Gentoo packaging system, it has turned
out to be easier than I feared.
We're currently running ReviewBoard 2.5.18, installed using the portage
package manager. So we have done this
