What are the drawbacks of installing via easy_install on RHEL, instead of
installing as an RPM?
If RPMs are the preferred or mandatory approach, is this something that BeanBag
should be doing?
Terry
From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On
Behalf Of Stephen
It should be checking these permissions on startup. Maybe that’s happening
after it’s trying to install the extension. I’ll see what we can do about
that.
Glad it’s working!
Christian
On Tue, Mar 20, 2018 at 05:50 wrote:
> Thanks for the quick reply!
>
> From
Could you please help look into this error?
$ rbt post -d -g
>>> RBTools 0.7.11
>>> Python 2.7.10 (default, Oct 6 2017, 22:29:07)
[GCC 4.2.1 Compatible LLVM 9.0.0 (clang-900.0.31)]
>>> Running on Darwin-17.5.0-x86_64-i386-64bit
>>> Home =
>>> Current directory =
>>> Command line: rbt post -d
Hey everyone,
We have a new Review Board release for you today, featuring new support for
linking to Asana and Trello tasks, posting to Mattermost and I Done This,
connecting to Gerrit repositories, making use of the modern GitLab API and
its features, extension improvements, diff filtering
Thanks for the quick reply!
>From above, I did confirm that the ALLOWED_HOSTS matches the FQDN we're
using to load the site.
Next, I changed permissions on the directory you referenced:
sudo chown -R apache /var/www/reviewboard.ncbp.org/htdocs/static/ext/
And I set DEBUG = False and restarted
Sorry, wasn't thinking. Review Board 3.0 auto-enables the RBIntegrations
extension, and its media installation is what's failing. Apache is trying
to copy data from the extension into $sitedir/htdocs/static/ext/, and
that's failing. This might be a simple permissions/ownership issue (this
Hi Jamie,
I believe I just found the cause of the error, and unfortunately it's not
making the release that you'll see an announcement for tomorrow (er, later
today, at this point). However, it's possible this is extension-related. Do
you have any extensions enabled?
Can you also open the
I just built an instance of Review Board in a newly built instance of RHEL
7 in an AWS EC2 instance and hit this exact issue. Would one of you folks
be kind enough to provide enough detail for me to fix it? I can't tell from
Marcin's post what it was that they did to work around the problem.
So, I just ran into this. New Review Board instance, new RHEL 7 instance at
AWS. I have the same results as what Marcin posted above. Interestingly,
setting Debug=True in the settings_local.py allows the site to load as
expected. But that seems like a bad thing to leave permanently. Any advice