RE: Issue with Alpha 1.0 r 4 on Debian
Hi Christian,
Thank you for the very speedy response. There was a default configuration that
I needed to alter, but it's all happy now.
Thanks again!
--- Bill.
From: reviewboard@googlegroups.com [mailto:reviewbo...@googlegroups.com] On
Behalf Of Christian Hammond
Sent: Thursday, February 19, 2009 4:30 PM
To: reviewboard@googlegroups.com
Subject: Re: Issue with Alpha 1.0 r 4 on Debian
You may have a "default.conf" or something in your sites-enabled directory
that's creating a site for /var/www and taking precedence over the Review Board
one. If so, delete that file and see if it works.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com
On Thu, Feb 19, 2009 at 3:20 PM, Bill DeVoe wrote:
Hello all,
This got accidentally posted to the reviewboard-issues list, so I apologize to
those getting it twice.
I've been trying to get ReviewBoard working on a Debian 5 installation. I've
got apache2 and the required utilities installed (I believe), but when I go to
the directory where ReviewBoard should be accessed I only see a directory list.
I've looked through the mailing list archive but the info there hasn't seemed
to pinpoint the problem. I've looked through the httpd.conf and the
apache2.conf files (which are below) but I'm not seeing any issues and hope
someone out there can help.
I installed ReviewBoard to /var/www/reviews. I'm not using a fully qualified
domain name (it's all internal), so the domain was just 'xyzzy'. I upgraded to
Alpha 1.0 release 4 just today, but now I just see an additional "tmp/"
directory in the list - the directory list is still the only thing visible.
The reported configuration is: Apache/2.2.9 (Debian) mod_ssl/2.2.9
OpenSSL/0.9.8g mod_python/3.3.1 Python/2.5.2 Server at xyzzy Port 443
Here's my httpd.conf:
# This is here for backwards compatability reasons and to support
# installing 3rd party modules directly via apxs2, rather than
# through the /etc/apache2/mods-{available,enabled} mechanism.
#
#LoadModule mod_placeholder /usr/lib/apache2/modules/mod_placeholder.so
LoadModule python_module /usr/lib/apache2/modules/mod_python.so
# End of httpd.conf --
Here's the apache2.conf:
#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so
"/var/log/apache2/foo.log"
# with ServerRoot set to "" will be interpreted by the
# server as "//var/log/apache2/foo.log".
#
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/etc/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#
#
LockFile /var/lock/apache2/accept.lock
#
#
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}
#
# Timeout: The number of seconds before receives and sends
Re: Issue with Alpha 1.0 r 4 on Debian
You may have a "default.conf" or something in your sites-enabled directory
that's creating a site for /var/www and taking precedence over the Review
Board one. If so, delete that file and see if it works.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com
On Thu, Feb 19, 2009 at 3:20 PM, Bill DeVoe wrote:
> Hello all,
>
> This got accidentally posted to the reviewboard-issues list, so I apologize
> to those getting it twice.
>
> I've been trying to get ReviewBoard working on a Debian 5 installation.
> I've got apache2 and the required utilities installed (I believe), but when
> I go to the directory where ReviewBoard should be accessed I only see a
> directory list. I've looked through the mailing list archive but the info
> there hasn't seemed to pinpoint the problem. I've looked through the
> httpd.conf and the apache2.conf files (which are below) but I'm not seeing
> any issues and hope someone out there can help.
>
> I installed ReviewBoard to /var/www/reviews. I'm not using a fully
> qualified domain name (it's all internal), so the domain was just 'xyzzy'. I
> upgraded to Alpha 1.0 release 4 just today, but now I just see an additional
> "tmp/" directory in the list - the directory list is still the only thing
> visible.
>
> The reported configuration is: Apache/2.2.9 (Debian) mod_ssl/2.2.9
> OpenSSL/0.9.8g mod_python/3.3.1 Python/2.5.2 Server at xyzzy Port 443
>
>
>
> Here's my httpd.conf:
>
> # This is here for backwards compatability reasons and to support
>
> # installing 3rd party modules directly via apxs2, rather than
>
> # through the /etc/apache2/mods-{available,enabled} mechanism.
>
> #
>
> #LoadModule mod_placeholder /usr/lib/apache2/modules/mod_placeholder.so
>
> LoadModule python_module /usr/lib/apache2/modules/mod_python.so
>
> # End of httpd.conf --
>
>
>
> Here's the apache2.conf:
>
> #
>
> # Based upon the NCSA server configuration files originally by Rob McCool.
>
> #
>
> # This is the main Apache server configuration file. It contains the
>
> # configuration directives that give the server its instructions.
>
> # See http://httpd.apache.org/docs/2.2/ for detailed information about
>
> # the directives.
>
> #
>
> # Do NOT simply read the instructions in here without understanding
>
> # what they do. They're here only as hints or reminders. If you are
> unsure
>
> # consult the online docs. You have been warned.
>
> #
>
> # The configuration directives are grouped into three basic sections:
>
> # 1. Directives that control the operation of the Apache server process as
> a
>
> # whole (the 'global environment').
>
> # 2. Directives that define the parameters of the 'main' or 'default'
> server,
>
> # which responds to requests that aren't handled by a virtual host.
>
> # These directives also provide default values for the settings
>
> # of all virtual hosts.
>
> # 3. Settings for virtual hosts, which allow Web requests to be sent to
>
> # different IP addresses or hostnames and have them handled by the
>
> # same Apache server process.
>
> #
>
> # Configuration and logfile names: If the filenames you specify for many
>
> # of the server's control files begin with "/" (or "drive:/" for Win32),
> the
>
> # server will use that explicit path. If the filenames do *not* begin
>
> # with "/", the value of ServerRoot is prepended -- so
> "/var/log/apache2/foo.log"
>
> # with ServerRoot set to "" will be interpreted by the
>
> # server as "//var/log/apache2/foo.log".
>
> #
>
>
>
> ### Section 1: Global Environment
>
> #
>
> # The directives in this section affect the overall operation of Apache,
>
> # such as the number of concurrent requests it can handle or where it
>
> # can find its configuration files.
>
> #
>
>
>
> #
>
> # ServerRoot: The top of the directory tree under which the server's
>
> # configuration, error, and log files are kept.
>
> #
>
> # NOTE! If you intend to place this on an NFS (or otherwise network)
>
> # mounted filesystem then please read the LockFile documentation (available
>
> # at http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>);
>
> # you will save yourself a lot of trouble.
>
> #
>
> # Do NOT add a slash at the end of the directory path.
>
> #
>
> ServerRoot "/etc/apache2"
>
>
>
> #
>
> # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
>
> #
>
> #
>
> #
>
> LockFile /var/lock/apache2/accept.lock
>
> #
>
> #
>
>
>
> #
>
> # PidFile: The file in which the server should record its process
>
> # identification number when it starts.
>
> # This needs to be set in /etc/apache2/envvars
>
> #
>
> PidFile ${APACHE_PID_FILE}
>
>
>
> #
>
> # Timeout: The number of seconds before receives and sends time out.
>
> #
>
> Timeout 300
>
>
>
> #
>
> # KeepAlive: Whether or not to allow persistent connections (more than
>
> # one request per connection). Set to "Off" to deactivate.
>
> #
>
> KeepAlive On
>
>
>
Issue with Alpha 1.0 r 4 on Debian
Hello all,
This got accidentally posted to the reviewboard-issues list, so I
apologize to those getting it twice.
I've been trying to get ReviewBoard working on a Debian 5 installation.
I've got apache2 and the required utilities installed (I believe), but
when I go to the directory where ReviewBoard should be accessed I only
see a directory list. I've looked through the mailing list archive but
the info there hasn't seemed to pinpoint the problem. I've looked
through the httpd.conf and the apache2.conf files (which are below) but
I'm not seeing any issues and hope someone out there can help.
I installed ReviewBoard to /var/www/reviews. I'm not using a fully
qualified domain name (it's all internal), so the domain was just
'xyzzy'. I upgraded to Alpha 1.0 release 4 just today, but now I just
see an additional "tmp/" directory in the list - the directory list is
still the only thing visible.
The reported configuration is: Apache/2.2.9 (Debian) mod_ssl/2.2.9
OpenSSL/0.9.8g mod_python/3.3.1 Python/2.5.2 Server at xyzzy Port 443
Here's my httpd.conf:
# This is here for backwards compatability reasons and to support
# installing 3rd party modules directly via apxs2, rather than
# through the /etc/apache2/mods-{available,enabled} mechanism.
#
#LoadModule mod_placeholder /usr/lib/apache2/modules/mod_placeholder.so
LoadModule python_module /usr/lib/apache2/modules/mod_python.so
# End of httpd.conf --
Here's the apache2.conf:
#
# Based upon the NCSA server configuration files originally by Rob
McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are
unsure
# consult the online docs. You have been warned.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process
as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default'
server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32),
the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so
"/var/log/apache2/foo.log"
# with ServerRoot set to "" will be interpreted by the
# server as "//var/log/apache2/foo.log".
#
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
(available
# at <
URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/etc/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#
#
LockFile /var/lock/apache2/accept.lock
#
#
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait for the next request from
the
# same client on the same connection.
#
KeepAliveTimeout 15
##
## Server-Pool Size Regulation (MPM specific)
##
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept
spare
# MaxSpareServers: maximum number of server processes which are kept
spare
# MaxClients: maxim
Re: installation issues with pylucene
On Thu, Feb 19, 2009 at 10:54 AM, Dan Morrow wrote: > > Hi there, > > I'm not a python expert. I've never used pylucene, or jcc. I'm just > trying to follow the instructions and have a good result. The problem > is, since I'm not an expert in python, I don't really know what the > error messages mean. > > (PS. You know what would've been cool about reviewboard? If the > install was as easy as "yum install reviewboard", gosh that would've > been nice. But I digress). How are you installing Review Board? Review Board itself is as easy as "easy_install ReviewBoard." The dependencies are another issue, but htat's completely beyond our control. You'd have to contact your distro and ask them to package Review Board and its dependencies. > > > I wanted to install pylucene, because it looks like it would be very > useful. I was able to build the jcc. However, when I try and make > pylucene, It gets partially through the make, but then it errors out > (after building many files) saying > > /usr/bin/python: module jcc has no associated file I don't know what would be causing this. Could you send a full log of the compile? Also, what version of PyLucene? Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
installation issues with pylucene
Hi there, I'm not a python expert. I've never used pylucene, or jcc. I'm just trying to follow the instructions and have a good result. The problem is, since I'm not an expert in python, I don't really know what the error messages mean. (PS. You know what would've been cool about reviewboard? If the install was as easy as "yum install reviewboard", gosh that would've been nice. But I digress). I wanted to install pylucene, because it looks like it would be very useful. I was able to build the jcc. However, when I try and make pylucene, It gets partially through the make, but then it errors out (after building many files) saying /usr/bin/python: module jcc has no associated file I did google around trying to figure out what this means, but have not had any luck. If anyone on this board knows what this means, and how to resolve it, I'd be really grateful. Thanks, -Dan. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: New user group
Hello Kunal, I encountered the same problem in my company and at the moment we didn't have a good solution. There is the possibility to pass all relevant files as an command line argument to the post_review script. But this is a manual process and could produce faulty reviews. The other problem is, that not every developer likes to work with an command line. ~ Bernd On Feb 19, 12:14 pm, KunalG wrote: > Ok, we will try to manage with that. Also let me know if it is > possible to handle a scenario where we have only 3 files from a folder > out of 5 related to a bug, because other 2 files may be from different > bug. And so we can upload only 3 files for this bug. When we call > post_review for Subversion from a folder, it uploads all the files > from that folder, whereas we wish to upload only few files. > > Thanks, > Kunal > > On Feb 19, 6:43 am, David Trowbridge wrote: > > > There's no automatic method right now. You might be able to write a > > script that uses the django shell capabilities to create the groups. > > > -David > > > 2009/2/17 KunalG : > > > > Hi, > > > > We are setting up review board in our company and found one feature > > > which we need. > > > We use LDAP authentication for login. So after a request is created by > > > user A and A wants to add a review group to the request. But this user > > > group needs to be created in Review Board. Is there any way we can add > > > directly our mailer group IDs directly under the groups just like > > > adding "reviewb...@googlegroups.com" in the request. If I try to enter > > > directly the group email ID it is not added. > > > Is there any way this could be achieved > > > > TIA, > > > Kunal --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: New user group
You should be able to specify the files to include on the command line. Similar to other svn operations, like when you only want to diff or commit certain files. It's a little bit of micromanagement, especially when you want to update a review later on, but it works. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.review-board.org VMware, Inc. - http://www.vmware.com On Thu, Feb 19, 2009 at 3:14 AM, KunalG wrote: > > Ok, we will try to manage with that. Also let me know if it is > possible to handle a scenario where we have only 3 files from a folder > out of 5 related to a bug, because other 2 files may be from different > bug. And so we can upload only 3 files for this bug. When we call > post_review for Subversion from a folder, it uploads all the files > from that folder, whereas we wish to upload only few files. > > Thanks, > Kunal > > > On Feb 19, 6:43 am, David Trowbridge wrote: > > There's no automatic method right now. You might be able to write a > > script that uses the django shell capabilities to create the groups. > > > > -David > > > > 2009/2/17 KunalG : > > > > > > > > > Hi, > > > > > We are setting up review board in our company and found one feature > > > which we need. > > > We use LDAP authentication for login. So after a request is created by > > > user A and A wants to add a review group to the request. But this user > > > group needs to be created in Review Board. Is there any way we can add > > > directly our mailer group IDs directly under the groups just like > > > adding "reviewb...@googlegroups.com" in the request. If I try to enter > > > directly the group email ID it is not added. > > > Is there any way this could be achieved > > > > > TIA, > > > Kunal > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: New user group
Ok, we will try to manage with that. Also let me know if it is possible to handle a scenario where we have only 3 files from a folder out of 5 related to a bug, because other 2 files may be from different bug. And so we can upload only 3 files for this bug. When we call post_review for Subversion from a folder, it uploads all the files from that folder, whereas we wish to upload only few files. Thanks, Kunal On Feb 19, 6:43 am, David Trowbridge wrote: > There's no automatic method right now. You might be able to write a > script that uses the django shell capabilities to create the groups. > > -David > > 2009/2/17 KunalG : > > > > > Hi, > > > We are setting up review board in our company and found one feature > > which we need. > > We use LDAP authentication for login. So after a request is created by > > user A and A wants to add a review group to the request. But this user > > group needs to be created in Review Board. Is there any way we can add > > directly our mailer group IDs directly under the groups just like > > adding "reviewb...@googlegroups.com" in the request. If I try to enter > > directly the group email ID it is not added. > > Is there any way this could be achieved > > > TIA, > > Kunal --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
