> On Jun 7, 2018, at 14:24, Alfred von Campe wrote:
>
> I’m not sure what is going on: the initial “easy_install -U ReviewBoard” did
> return an error, but after forcing the install of version 3.0.3 where I was
> upgrading from, another easy_install -U ReviewBoard su
I’m not sure what is going on: the initial “easy_install -U ReviewBoard” did
return an error, but after forcing the install of version 3.0.3 where I was
upgrading from, another easy_install -U ReviewBoard succeeded, as did the
rb-site upgrade. I can add users again to review groups (which is
On Apr 27, 2018, at 17:45, David Trowbridge wrote:
>
> I can reproduce this. We'll get a fix in for the next 3.0.x release.
Great, thanks for the quick response.
Alfred
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for
Trying to access some, but not all, of my review groups in the Web UI result in
a "Something broke! (Error 500)” error, and I get the (slightly sanitized)
traceback included below. Any ideas what may be causing this?
Alfred
Traceback (most recent call last):
File
gt; access"
>
> -David
>
> On Wed, Mar 7, 2018 at 12:01 PM Alfred von Campe <alf...@von-campe.com
> <mailto:alf...@von-campe.com>> wrote:
> Is there a way to prevent users from getting access to review requests unless
> they are logged in? It’s bee
Is there a way to prevent users from getting access to review requests unless
they are logged in? It’s been brought to my attention that you can see review
requests and their associated code diffs even when you are not logged in, and
we are trying to prevent that.
Thanks,
Alfred
--
this for 3.0.4.
>
> Christian
>
> On Wed, Feb 21, 2018 at 4:32 AM, Alfred von Campe <alf...@von-campe.com
> <mailto:alf...@von-campe.com>> wrote:
> Christian:
>
> The original domain controller configured in ReviewBoard is still down, but
> I’ve reconfigured
t have logging centered around that.
>
> If you do get locked out of the server due to the backend failing and session
> expiring, you can always use `rb-site manage /path/to/sitedir
> createsuperuser` to create a new local administration account.
>
> Christian
>
> On Tue,
Our ReviewBoard server is configured to use Active Directory for
authentication. The Domain Controller it was configured to use for
authentication had a catastrophic HW failure so users can no longer log in to
ReviewBoard. Fortunately I had an existing ReviewBoard session open in a
browser
When I created the repositories on our ReviewBoard server, I originally left
the Bug Tracker information blank. I would now like to update all repos to
include the URL to our Jira server, and was wondering if there was a quick way
to do it either via the command line or with MySQL commands?
;
> It looks like the "rbslack" extension was installed and activated. You can
> fix these errors by going to "Extensions" in the admin UI and disabling it.
>
> -David
>
> On Mon, Nov 21, 2016 at 6:44 AM Alfred von Campe <alf...@von-campe.com
>
I was browsing through the reviewboard.log file while debugging an unrelated
issue when I came across a bunch of errors that all look like this:
2016-11-21 14:07:55,959 - ERROR - - Failed to send notification to slack.com:
unknown url type:
Traceback (most recent call last):
File
On Aug 15, 2016, at 18:03, Christian Hammond wrote:
>
> To check, was Apache restarted after installing the new module?
No, but it occurred to me to do that just before I saw your post, and now it’s
working! It appears to be a bit slower than our previous instance,
On Aug 15, 2016, at 17:31, Christian Hammond wrote:
>
> What version of ldap do you have? It sounds like it may be too old. Sometimes
> the distro-provided packages are too stale to rely upon.
>
> I'd recommend uninstalling the RPM and instead installing using pip:
On Aug 15, 2016, at 16:21, Christian Hammond wrote:
> The Review Board log files ($sitedir/logs) should include some information.
> Failing that, the Apache error log.
>
> You may have to install the appropriate Python modules for Active Directory
> again. (I
On Aug 14, 2016, at 19:55, Christian Hammond wrote:
> This looks like a MyISAM vs. InnoDB table format issue. You'll need to either
> make sure all your tables are converted to InnoDB (you can replace "MyISAM"
> with "InnoDB" in the database dump when you go to load
> On Aug 11, 2016, at 19:41, Christian Hammond wrote:
>
> There's a draft of a document on my computer, but nothing online yet. I need
> to finish it.
If you want me to review/edit it as I’m doing the migration, I will be glad to.
Just let me know.
> The database
I must be missing a simple step somewhere. I’m trying to migrate a ReviewBoard
version 1.7.27 instance running on CentOS 6 to version 2.5.6.1 on CentOS 7.
I’ve installed ReviewBoard (via EPEL RPM) on the new server, installed MySQL
and created the reviewboard database, loaded the SQL dump
This is what I do on the CentOS 6 systems I mange:
# Install repo file and then Python itself
rpm -ivh
http://dl.iuscommunity.org/pub/ius/stable/Redhat/6/i386/ius-release-1.0-14.ius.el6.noarch.rpm
yum install -y python27 python27-virtualenv
Alfred
> On Nov 2, 2015, at 17:31, Zachary Gallagher
David:
Can you check the result of `rb-site manage /var/www/html/rb/ get-siteconfig
-- --key=site_media_url` ?
My guess is that it will say /rb/htdocs/media/
If so, run this:
`rb-site manage /var/www/html/rb/ set-siteconfig -- --key=site_media_url
--value=/media/
And it should
Does anyone have any idea what could be causing the problem described below?
Alfred
On Feb 24, 2015, at 10:05, Alfred von Campe alf...@von-campe.com wrote:
We are using ReviewBoard 1.7.27 on CentOS 6 (I would love to update to 2.X
but that’s still not easy on CentOS 6 as far as I know
On Feb 25, 2015, at 16:30, David Trowbridge trowb...@gmail.com wrote:
What does the web server configuration look like?
VirtualHost *:80
ServerName hepdsw-rb.bose.com
DocumentRoot /var/www/html/rb/htdocs
# Error handlers
ErrorDocument 500 /errordocs/500.html
We are using ReviewBoard 1.7.27 on CentOS 6 (I would love to update to 2.X but
that’s still not easy on CentOS 6 as far as I know). Reviews re working fine,
but today a user tried to add a screenshot to a review, and while the file got
uploaded (I can see it under htdocs/media/uploaded/files/…
We have been using ReviewBoard with our Subversion repos using svn+ssh://
access, and while functional, it’s been a little slow. Performance with
https:// access to our Subversion servers is noticeably faster, but when I
configure the Repository in ReviewBoard and specify the username and
Christian:
If you upgrade to the 2.0 releases, all passwords will be encrypted. I know
it's not trivial, and maybe we can backport that to a 1.7 release, but as
we're about to start on the 2.5 betas, we're unlikely to continue making
major changes to 1.7 from here on out. We'll see what we
Stephen:
Review Board 2.0.11 packages for Fedora 21 and EPEL 7 are now on their
way to their respective testing repositories.
Any update on Review Board 2.X packages for RHEL 6? I know that you were
working on it a few months ago.
Alfred
--
Get the Review Board Power Pack at
On Oct 28, 2014, at 15:15, Stephen Gallagher step...@gallagherhome.com wrote:
No progress has been made on that, I'm afraid. It's a bigger undertaking
than it seems and I've frankly been swamped with other work
(particularly the Fedora 21 release). I'd love to have someone help with
this…
I
Bump! Just refreshing this thread to see if anyone has any ideas why I still
can't download attachments.
Alfred
On Aug 26, 2014, at 20:22, Christian Hammond christ...@beanbaginc.com wrote:
Can you try changing the media URL to have a '/' as a suffix? So:
/rb/htdocs/media/, instead of
On Aug 26, 2014, at 20:22, Christian Hammond christ...@beanbaginc.com wrote:
Can you try changing the media URL to have a '/' as a suffix? So:
/rb/htdocs/media/, instead of /rb/htdocs/media.
I did that and reported back that it still wasn't working (although it appears
that the web server is
On Aug 25, 2014, at 10:25, I wrote:
I've successfully migrated a ReviewBoard instance from version 1.6 running on
CentOS 5 to version 1.7.25 running on CentOS 6. Well, almost successfully:
we can't download attachments from the new instance. The apache logs show
that it is looking for
I recently had to migrate a ReviewBoard instance from one server to another. I
have the new instance running, and everything seems to be OK except that emails
sent by the new instance contain URLs that point to the old server. When I log
into the Admin interface and try to change the Server
On Jul 8, 2014, at 15:12, Christian Hammond christ...@beanbaginc.com wrote:
Which version of Review Board is this? I remember an old bug about this, but
it has since been fixed.
The latest available via the EPEL repo: 1.7.25
Alfred
--
Get the Review Board Power Pack at
On Aug 23, 2013, at 16:29, David Trowbridge trowb...@gmail.com wrote:
Let's try this--after creating the new site, but before loading the database
dump, delete the new database that rb-site created.
This seems to have worked. Because I had tried to install ReviewBoard 1.6.6
via
On Aug 27, 2013, at 11:07, I wrote:
But now I have another problem. During this upgrade, the paths to the RB
site have changed slightly, and after the installation I get a message about
a missing htdocs/media/uploaded directory using he old path. So I guess that
somewhere in the database
I'm trying to upgrade a REviewBoard instance from 1.6.6 to 1.7.13. I've
created a dump of the existing database and am running the following script on
the new server:
#!/bin/sh
RB_SITE=/var/www/html/rb
RB_USER=admin
RB_EMAIL=
RB_DOMAIN=
RB_PASSWORD=
# Delete and create empty rb
On Aug 23, 2013, at 16:14, David Trowbridge trowb...@gmail.com wrote:
What's happening is that rb-site install is creating a bunch of tables, and
then you're importing in the database dump but it's ending up with a mix of
old and new.
I'd recommend installing 1.6.6 on the new server,
On Aug 23, 2013, at 16:29, David Trowbridge trowb...@gmail.com wrote:
Let's try this--after creating the new site, but before loading the database
dump, delete the new database that rb-site created.
Sigh, I started playing with installing ReviewBoard 1.6 with easy install, and
seems to have
On Apr 24, 2013, at 10:55, I wrote:
We are running ReviewBoard 1.6.6 installed via easy-install on an old CentOS
5.9 server with apache-modpython, and I would like to migrate this to a new
server running CentOS 6.4 and apache-wsgi and the latest ReviewBoard version
installed via yum from
We are running ReviewBoard 1.6.6 installed via easy-install on an old CentOS
5.9 server with apache-modpython, and I would like to migrate this to a new
server running CentOS 6.4 and apache-wsgi and the latest ReviewBoard version
installed via yum from epel-testing repo.
Are the steps to do
On Apr 14, 2013, at 18:06, Stephen Gallagher wrote:
After much blood, sweat and tears, I have finally managed to land
ReviewBoard 1.7.6 in the EPEL 6 add-on repository for Red Hat Enterprise
Linux 6 (and its clones). The update should filter out to the
[epel-testing] mirrors in the next 24-48
We are using RB 1.6.6 and LDAP for authentication. We recently had a
contractor become a permanent employee and because of this his userid changed.
So he is in the database twice now, once with the old userid and once with the
new one. I can't delete the old userid as it will delete all the
On Sep 12, 2012, at 17:32, Christian Hammond wrote:
An admin should be able to go into the database and just rename the username
for that user.
I'm the admin, but my SQL is a bit rusty and I'm also not very familiar with
the schema. I may be able to figure it out, but any examples/hints
On Sep 12, 2012, at 18:10, Christian Hammond wrote:
You don't need to touch SQL. Just go into the Review Board admin UI, then
click Users, find the username, and rename it there.
Doh! I didn't try that. But I just did and it tells me User with this
Username already exisits. Which makes
On Sep 12, 2012, at 21:00, Christian Hammond wrote:
So the new one has review requests associated with it now? Otherwise, I'd say
just delete the new one and update the old.
Yes, the new one has reviews and comments, etc. associated with it (actually
more than the old user does).
If there
On May 7, 2012, at 16:56, Christian Hammond wrote:
Memory and how much of it that memcached can use is crucial. We cache a
*lot*, since fetching files from the repository, patching them, and
generating diffs is all very expensive. So the more that memcached can hold
at once, the faster
On Apr 25, 2012, at 5:50, Christian Hammond wrote:
Review Board 1.6.6 is out, and adds support for getting GitHub API tokens for
private repos.
I'm running ReviewBoard 1.5.4 on Centos 5.8, and would like to upgrade to
something more recent (i.e., 1.6.6). However, I've only upgraded once
Can you tell me more about your setup (server-side)? In particular:
* OS/distro
* Review Board version
* Memory
* CPU
* Python version
Sure, here is our server data:
CentOS 5.5
ReviewBoard 1.5
Memory 2GB
3.06GHz Intel Xeon
Python 2.4.3
Strange. When this happens, can you check
We are experiencing a strange hang when viewing one particular review. When we
click on the View DIff we get a new web page and the Files Changed: section
lists all the files that have changed in this particular request. There are 20
files, and the information for the first 6 is updated in a
Yes, and if you use sqlite especially, you're certain to hit this.
Alfred, what are you using for a database?
We are using MySQL.
2. complex diffs being slow to generate diffs, this is a feature of
the batteries includes difflib in python.
So actually, we don't use difflib. We
Did something change in the way Subversion repositories that are accessed via
ssh are handled in RB 1.5? Our setup is as follows:
1. Our web server runs on a Linux server as our build account (not apache)
2. The build account is configured to allow password-less ssh access to any
other
On Oct 16, 2009, at 3:55, Christian Hammond wrote:
Is it literally /logs? Whatever directory you specify must exist
and be writable by the web server. It will also likely take a
server restart for logging to kick in.
Well, the rb-site script created a logs directory at the same level
On Oct 14, 2009, at 18:49, Christian Hammond wrote:
We use Django's e-mail functionality which unfortunately doesn't
give us any sort of debugging information.
What mail server are you using? And is it on the same host? Do you
have anything like DKIM turned on?
Sorry for not replying
On Oct 13, 2009, at 17:00, Christian Hammond wrote:
The 1.0.x releases don't support svn+ssh, but the 1.1 in-
development releases do. I would not suggest using 1.1 in
production yet though, as there will be bugs.
I'm still in the process of setting up our ReviewBoard server, but
I've
On Oct 14, 2009, at 9:45, Thilo-Alexander Ginkel wrote:
That's actually the standard behavior. Did you maintain an SMTP server
in the settings?
It was set to the same host name as the RB server itself and the
Send e-mails... checkbox was disabled. I changed it to use our
internal SMTP
On Oct 14, 2009, at 13:23, Thilo-Alexander Ginkel wrote:
Did you try without setting the credentials?
I tried to, but it won't let me. That is, I clear the Username and
Password fields in the E-Mail Settings screen and click on Save. But
when the screen refreshes, the fields are filled
On Oct 14, 2009, at 17:56, Christian Hammond wrote:
It's possible that your browser is filling in these fields, and
that they're not actually being saved in the database. It's really
annoying. I've been meaning to look into whether or not the browser
can be told not to provide
On Oct 12, 2009, at 11:42, Alfred von Campe wrote:
The error I posted yesterday is suddenly gone today; that is, I ran
post-review again in the same sandbox and the review posted without
errors. I have not changed a thing on the server. Furthermore, when
I went into the web interface
Hi Christian:
Also, when you saw ClientError from post-review, that was output
from the server. So it's the same problem. I'd recommend restarting
Apache just in case it is an issue with one or two threads not
having imported it successfully.
I thought I had restarted Apache, but
I've gotten the AD integration to work. It was a lot easier than I
expected and users can log in to ReviewBoard with their regular
usernames and passwords. This is great, but I've run into a few issues:
1. I can not add a user to a review group unless that user has
logged in to RB at
On Oct 12, 2009, at 11:27, David Trowbridge wrote:
If you run post-review with --debug, it'll spit out a bunch of output
which should hopefully tell you the real error.
I must be going bling; I didn't see that option in the output of
post-review -h but it's right there at the bottom.
I'm still in the process of setting up out ReviewBoard server
(struggling with LDAP/AD integration at the moment), but I'm looking
slightly ahead. It appears that post-review is the recommended way to
create a review (we're using Subversion if that matters), and I can
see that post-review
I reluctantly used easy_install to get ReviewBoard 1.0 installed on
my CentOS 5.3 server (I would have preferred to use an RPM based
install, but that is not available). I actually started to install
when 1.0rc2 was the latest but had problems back then as well. At
the moment I don't
62 matches
Mail list logo