Reset Ship It in Review
Hi all, right now we are altering our Reviewboard installation to meet our new development requirements. In this requirements it is specified that only reviewed code is committed into our release repository (in order to achieve a safety certificate). Currently we are having the problem that in case of a review update an old Ship It can not be removed. Is there a way to reset all Ship It's when updating a review request? Thanks in advance, Karl -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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: Ready VM or Recommended distribution for Review Board 1.7
On Mon, Jan 7, 2013 at 9:54 PM, Matthew Woehlke mwoehlke.fl...@gmail.com wrote: On 2013-01-07 12:20, Erik Putrycz wrote: Are there any downloadable appliances with Review Board 1.7? I found bitnami review board but they only have 1.6 In BitNami we are already working on the installers and virtual appliances for Review Board 1.7. I will let you know as soon as they are ready. Best regards, Victoria. Otherwise, which distribution would result in the easiest install? Would CentOS 6.3 work? If you're willing to run non-LTS Fedora, and the still-in-beta version 18 thereof, I'm happily doing likewise using Stephen's packages of RB 1.7.1. -- Matthew -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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 -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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
Post-review installation
Hi! We just managed to install Review Board on one of our organisation's web hotel (a server which we don't have direct access to), so we have a working installation and we can reach the web interface. We also learned from you that for ClearCase, post-review is not only recommended but required. My basic question would be: where should we install this tool? We are having access to some Linux machines where we can reach ClearCase from. Should we put it on one of these? Am I right that it won't be useful to install post-review on the same machine where Review Board is installed, as we cannot get command line access there? Thanks, Géza Kulcsár -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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: Testing 1.7.1 on Fedora 18
Hi Stephen,
Bug raised as requested. I didn't see a place to set the CC field on the
google/reviewboard bug tracker, so here's the URL so you can star it and get
yourself CCed.
http://code.google.com/p/reviewboard/issues/detail?id=2850
Thanks,
Paul
From: Stephen Gallagher step...@gallagherhome.com
To: p...@talk21.com
Cc: chip...@chipx86.com chip...@chipx86.com; Christian Hammond
chip...@gmail.com; reviewboard@googlegroups.com
reviewboard@googlegroups.com
Sent: Monday, 7 January 2013, 19:55
Subject: Re: Testing 1.7.1 on Fedora 18
On 01/04/2013 04:07 AM, p...@talk21.com wrote:
Hi Stephen,
The following AVC denied errors occur:
1) named_connect to port 11211 (memcached)
type=AVC msg=audit(1357289094.993:338): avc: denied { name_connect }
for pid=1668 comm=httpd dest=11211
scontext=system_u:system_r:httpd_t:s0
tcontext=system_u:object_r:memcache_port_t:s0 tclass=tcp_socket
Reviewboard 1.7.1 by default uses memcached, it seems like the SELinux
profile for httpd doesn't allow TCP connections to port 11211. This
failure does not prevent reviewboard from working, but is likely to
affect performance. Should the profile shipped with Fedora be extended
to allow these connections by default?
It's a boolean in the shipped configuration:
setsebool -P httpd_can_network_memcache 1
[Unix permissions]
Reviewboard initially detects that write permission is not available and
returns a web page instructing the user to grant write permission with
these commands:
$ sudo chown -R apache /var/www/reviewboard/data
$ sudo chown -R apache /var/www/reviewboard/htdocs/media/ext
Once the permissions are changed, SELinux still prevents write access.
The individual permissions have nothing to do with SELinux. As I said in
my other email, you need to make sure these files have the right context
set (or install the site into /var/www/html, but I don't recommend that).
2) write to ext directory
type=AVC msg=audit(1357289565.991:401): avc: denied { write } for
pid=1665 comm=httpd name=ext dev=dm-1 ino=1896
scontext=system_u:system_r:httpd_t:s0
tcontext=unconfined_u:object_r:httpd_sys_content_t:s0 tclass=dir
SELinux context is currently:
$ ls -ldZ /var/www/reviewboard/htdocs/media/ext/
drwxrwxr-x. apache pafee unconfined_u:object_r:httpd_sys_content_t:s0
/var/www/reviewboard/htdocs/media/ext/
Suggestion from SELinux Trouble shooter fixed this issue:
$ sudo restorecon -v /var/www/reviewboard/htdocs/media/ext
$ ls -ldZ /var/www/reviewboard/htdocs/media/ext/
drwxrwxr-x. apache pafee unconfined_u:object_r:httpd_sys_rw_content_t:s0
/var/www/reviewboard/htdocs/media/ext/
I agree it would be difficult for Fedora to predict where a reviewboard
site would be placed. Would it be possible for rb-site install to set
the SELinux security contexts of the files it creates?
I know this is possible from the libsemanage-python package. We could
probably rig something up, but it's not going to be a trivial patch.
Could you open a bug on the Review Board tracker about this and make
sure I'm CCed on it, please? Christian, I'll look into this one since I
have a (limited) SELinux background.
It would certainly be nice to have Review Board properly protected by
SELinux.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
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: LDAP configuration problem
Well, I guess I misunderstood the meaning of the configuration field
(somewhat), and found what could be a problem in the code. My LDAP server
does not allow anonymous binds, and so I've had to take caution in
configuring what just about every other tool calls the bind account and
bind password. When I saw the Anonymous User Mask and Anonymous User
Password I drew a near immediate correlation. After I reviewed the code, I
found that when a user sends an authentication request, ReviewBoard uses
the user's credentials to perform its initial bind, instead of either
binding anonymously or using a bind account. Removing the Anonymous User
Mask and password fixed the problem for me (my ReviewBoard site does not
allow anonymous access anyways). But in studying the code I found that the
User Mask field contents are used to build the bind distinguished name
when no Anonymous User Mask is provided. This is all well and good,
except I thought the User Mask field was meant to hold an LDAP filter
specification. A proper filter to match against a uid would be (uid=%s)
with %s being substituted by the input user ID. This string, however, is
not appropriate to use as the first element of the bind DN, as line 208 in
reviewboard/accounts/backends.py:
userbinding=','.join([uid,settings.LDAP_BASE_DN])
If I'm reading that code right, uid which when the User Mask field has
been set to (uid=%s) has expanded to (uid=localuser) (for example with
a localuser user), is prepended to the base DN then used as the bind DN.
(uid=localuser),ou=Users,dc=local is of course a badly formatted DN.
Entering uid=%s (without the parenthesis) fixes the problem for now.
I'm still at a loss as to why with the Anonymous User Mask and Password
LDAP returned a bad search filter, though.
On Monday, January 7, 2013 5:45:00 PM UTC-5, Rolando Nieves wrote:
Well, I'm having the same error and I know my way around LDAP:
LDAP Server: ldap://localhost:389
LDAP Base DN: ou=Users,dc=local
Given Name Attribute: givenName
Surname Attribute: sn
Full Name Attribute: cn
E-Mail LDAP Attribute: mail
User Mask: (uid=%s)
Anonymous User Mask: cn=proxyuser,dc=local
Anonymous User Password:
When presented with valid LDAP credentials, ReviewBoard rejects them and I
receive this error in my Apache log:
[error] WARNING:root:LDAP error: {'desc': 'Bad search filter'}
Running this on the command line life is good:
ldapsearch -x -H ldap://localhost:389 -D 'cn=proxyuser,dc=local' -w
-b 'ou=Users,dc=local' '(uid=localuser)'
I know the '(uid=%s)' filter specification is not the problem since when I
log in with the built-in 'admin' account I see the appropriate error
message in my Apache2 log:
[error] WARNING:root:LDAP error: The specified object does not exist in
the Directory: (uid=admin)
Hence the uid filter is expanding properly, and there are no mysterious
filters in the initial LDAP search dip. There's gotta be another LDAP
search that has a poorly-constructed filter.
On Monday, August 20, 2012 4:02:19 PM UTC-4, Tucker wrote:
* You LDAP server needs to start with ldap://;. Probably
ldap://10.10.192.42:389;
* Your LDAP base DN is most likely wrong. You'll either need to
familiarize yourself with your LDAP schema or find someone who knows
what that should be.
* Unless you actually own example.com, your E-mail domain is wrong.
* Leave the anonymous user mask blank, unless you know what you're doing.
On Mon, Aug 20, 2012 at 12:40 AM, Raymond Meng raymon...@gmail.com
wrote:
hi guys:
I'm quite a freshman of reviewboard. I met problems during my LDAP
configuration.
my settings:
LDAP server: 10.10.192.41:389
LDAP base DN: ou=example,dc=example,dc=
example
given name attribute: givenName
surname attribute: sn
full name attribute: cn
E-mail Domain: example.com
E-mail LDAP attribute: mail
unchecked Use TLS for authentication
user mask: (uid=%s)
anonymous user mask: (uid=%s)
anonymous user password: ***
and when I try to login reviewboard with my email account, error occur:
WARNING - LDAP error: {'info': '', 'desc': 'Bad search filter'}
can you help me to take a look on that?
thanks!
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
--
--tucker
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more
Re: Error happens SVN HTTPS certificate not verified when adding a new repo.
Unfortunately this is a known bug in 1.7.1. We'll be putting out a 1.7.2 soon with a fix. -David On Jan 7, 2013, at 11:36 PM, Bing kevin.zhub...@gmail.com wrote: Hi, all, When I create a new repo (SVN) with https:// link, the following error message shows after click Save button. A verified HTTPS certificate is required to connect to this repository. There were errors validating this certificate: The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually. Certificate information: Hostname: .xx.com Valid: from Thu, 03 Nov 2011 23:33:44 GMT until Sun, 02 Nov 2014 23:33:44 GMT Issuer: Fingerprint: xxx Do you trust this host, or do you want to go back and edit the repository information? then there are two buttons: I trust this host and Re-Edit repository however, the problem is that both buttons are gray. so I cannot click any one of them. My review board is 1.7.1. Anyone can get me help? Thanks BING -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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 -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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
Trouble getting custom auth backend to work
Hi All, I'm trying to setup Reviewboard(version 0.7) to authenticate with a htpasswd file. Followed the instructions here, http://www.reviewboard.org/docs/codebase/dev/extending/auth-backends/ and got to the point where my backend started appearing in the Authentication dropdown from Admin preferences. Choosing that also seems to work fine, with the choice retained on navigating back and with no errors in apache logs. However, when I logout as admin and try to login as one of the users in htpasswd file, it does not work. I tried adding some log statements in the authenticate method.. but don't see them in the apache logs either. What am I missing? Thanks, Santhosh -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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: Error happens SVN HTTPS certificate not verified when adding a new repo.
Hi all, I am also facing this issue on 1.7.1. Both buttons are disabled the error log says Server certificate verification failed: issuer is not trusted. The data directory is owned by apache2 user. I am using apache+ mod_wsgi. It will be a great help if somebody can suggest a solution. Thanks, Sojan On Tuesday, 8 January 2013 13:06:35 UTC+5:30, Bing wrote: Hi, all, When I create a new repo (SVN) with https:// link, the following error message shows after click Save button. A verified HTTPS certificate is required to connect to this repository. There were errors validating this certificate: The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually. Certificate information: Hostname: .xx.com Valid: from Thu, 03 Nov 2011 23:33:44 GMT until Sun, 02 Nov 2014 23:33:44 GMT Issuer: Fingerprint: xxx Do you trust this host, or do you want to go back and edit the repository information? then there are two buttons: I trust this host and Re-Edit repository however, the problem is that both buttons are gray. so I cannot click any one of them. My review board is 1.7.1. Anyone can get me help? Thanks BING -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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: Cannot add a remote SVN repo on 1.6.15 (Regression?)
I'd be happy to do some code-level digging. Any tips on where to start? Thanks Liam -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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
rb-site upgrade fails on database migration
We've been making regular backups of our RB 1.5.5 database, and I decided
it was time to verify that we can restore the DB to a new install in case
our server fails. The backups are made with mysqlhotcopy, so I understand
they can be restored by simply stopping the mysql service, copying the
backup files into the appropriate folder (/var/lib/mysql/reviewboard), and
starting mysql.
I installed RB 1.7 on an Ubuntu 12.04 LTS VM. I got the software all
installed and removed the fresh 1.7 database, replacing it with our
backed-up 1.5.5 DB, making sure to set proper privileges on the db files
and in mysql itself.
I ran:
rb-site upgrade -d /var/www/mysite
Which failed, giving this output:
-- begin log output --
Creating tables ...
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Traceback (most recent call last):
File /usr/local/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.7.1', 'console_scripts', 'rb-site')()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 1937, in main
command.run()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 1778, in run
site.sync_database()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 366, in sync_database
self.run_manage_command(syncdb, params)
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 556, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/__init__.py,
line 459, in execute_manager
utility.execute()
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/__init__.py,
line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py,
line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py,
line 232, in execute
output = self.handle(*args, **options)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py,
line 371, in handle
return self.handle_noargs(**options)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/commands/syncdb.py,
line 102, in handle_noargs
cursor.execute(statement)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/backends/mysql/base.py,
line 114, in execute
return self.cursor.execute(query, args)
File /usr/lib/python2.7/dist-packages/MySQLdb/cursors.py, line 174, in
execute
self.errorhandler(self, exc, value)
File /usr/lib/python2.7/dist-packages/MySQLdb/connections.py, line 36,
in defaulterrorhandler
raise errorclass, errorvalue
django.db.utils.DatabaseError: (1005, Can't create table
'reviewboard.#sql-5a2b_5b' (errno: 150))
Any ideas?
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
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
Recent upgrade to 1.7.1 broke my site.
Hi, Today, I upgraded my review board installation to 1.7.1. By doing this, My site is broken. I get internal server error. In the apache log file, I see the following lines. [Tue Jan 08 14:55:08 2013] [notice] Apache/2.2.14 (Ubuntu) Phusion_Passenger/2.2.7 PHP/5.3.2-1ubuntu4.17 with Suhosin-Patch mod_python/3.3.1 Python/2.6.5 mod_wsgi/2.8 configured -- resuming normal operations [Tue Jan 08 22:55:17 2013] [error] /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead [Tue Jan 08 22:55:17 2013] [error] import md5 [Tue Jan 08 22:55:19 2013] [error] /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead [Tue Jan 08 22:55:19 2013] [error] import md5 My apache config is VirtualHost *:80 ServerName review.board DocumentRoot /var/www/review.board/htdocs # Error handlers ErrorDocument 500 /errordocs/500.html WSGIPassAuthorization On WSGIScriptAlias / /var/www/review.board/htdocs/reviewboard.wsgi/ # Serve django pages Location / PythonPath ['/var/www/review.board/conf'] + sys.path SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings SetEnv PYTHON_EGG_CACHE /var/www/review.board/tmp/egg_cache SetEnv HOME /var/www/review.board/data SetHandler mod_python PythonHandler django.core.handlers.modpython PythonAutoReload Off #PythonDebug Off PythonDebug On # Used to run multiple mod_python sites in the same apache PythonInterpreter reviewboard_crs_aaryanapps_net /Location # Serve static media without running it through mod_python # (overrides the above) Location /media SetHandler None /Location Location /errordocs SetHandler None /Location Location /static SetHandler None /Location Directory /var/www/review.board/htdocs AllowOverride All /Directory # Alias static media requests to filesystem Alias /media /var/www/review.board/htdocs/media Alias /errordocs /var/www/review.board/htdocs/errordocs Alias /static /var/www/review.board/htdocs/static /VirtualHost Not sure what else to look for and where. Thanks, -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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: Recent upgrade to 1.7.1 broke my site.
DeprecationWarnings are harmless. There's probably something else (either in the apache log or the reviewboard log). -David On Tue, Jan 8, 2013 at 3:01 PM, Custom Apps sme...@customapps.in wrote: Hi, Today, I upgraded my review board installation to 1.7.1. By doing this, My site is broken. I get internal server error. In the apache log file, I see the following lines. [Tue Jan 08 14:55:08 2013] [notice] Apache/2.2.14 (Ubuntu) Phusion_Passenger/2.2.7 PHP/5.3.2-1ubuntu4.17 with Suhosin-Patch mod_python/3.3.1 Python/2.6.5 mod_wsgi/2.8 configured -- resuming normal operations [Tue Jan 08 22:55:17 2013] [error] /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead [Tue Jan 08 22:55:17 2013] [error] import md5 [Tue Jan 08 22:55:19 2013] [error] /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead [Tue Jan 08 22:55:19 2013] [error] import md5 My apache config is VirtualHost *:80 ServerName review.board DocumentRoot /var/www/review.board/htdocs # Error handlers ErrorDocument 500 /errordocs/500.html WSGIPassAuthorization On WSGIScriptAlias / /var/www/review.board/htdocs/reviewboard.wsgi/ # Serve django pages Location / PythonPath ['/var/www/review.board/conf'] + sys.path SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings SetEnv PYTHON_EGG_CACHE /var/www/review.board/tmp/egg_cache SetEnv HOME /var/www/review.board/data SetHandler mod_python PythonHandler django.core.handlers.modpython PythonAutoReload Off #PythonDebug Off PythonDebug On # Used to run multiple mod_python sites in the same apache PythonInterpreter reviewboard_crs_aaryanapps_net /Location # Serve static media without running it through mod_python # (overrides the above) Location /media SetHandler None /Location Location /errordocs SetHandler None /Location Location /static SetHandler None /Location Directory /var/www/review.board/htdocs AllowOverride All /Directory # Alias static media requests to filesystem Alias /media /var/www/review.board/htdocs/media Alias /errordocs /var/www/review.board/htdocs/errordocs Alias /static /var/www/review.board/htdocs/static /VirtualHost Not sure what else to look for and where. Thanks, -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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 -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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: Recent upgrade to 1.7.1 broke my site.
I am not an expert in this. So not sure what else to look for. Even though they are deprecationwarning, they seem to have error tag. Can this be an issue? The apache log also has these entries. [Tue Jan 08 23:04:46 2013] [error] import md5 /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/core/handlers/modpython.py:131: DeprecationWarning: The mod_python handler is deprecated; use a WSGI or FastCGI server instead. DeprecationWarning) /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. DeprecationWarning /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/core/handlers/modpython.py:131: DeprecationWarning: The mod_python handler is deprecated; use a WSGI or FastCGI server instead. DeprecationWarning) /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. DeprecationWarning /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/core/handlers/modpython.py:131: DeprecationWarning: The mod_python handler is deprecated; use a WSGI or FastCGI server instead. DeprecationWarning) /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. DeprecationWarning [Tue Jan 08 15:06:21 2013] [notice] caught SIGTERM, shutting down PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626/pdo_sqlite.so' - /usr/lib/php5/20090626/pdo_sqlite.so: undefined symbol: php_pdo_register_driver in Unknown on line 0 PHP Warning: Module 'mysql' already loaded in Unknown on line 0 PHP Warning: Module 'sqlite3' already loaded in Unknown on line 0 [Tue Jan 08 15:06:22 2013] [notice] mod_python: Creating 8 session mutexes based on 150 max processes and 0 max threads. [Tue Jan 08 15:06:22 2013] [notice] mod_python: using mutex_directory /tmp [Tue Jan 08 15:06:22 2013] [notice] Apache/2.2.14 (Ubuntu) Phusion_Passenger/2.2.7 PHP/5.3.2-1ubuntu4.17 with Suhosin-Patch mod_python/3.3.1 Python/2.6.5 mod_wsgi/2.8 configured -- resuming normal operations /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/core/handlers/modpython.py:131: DeprecationWarning: The mod_python handler is deprecated; use a WSGI or FastCGI server instead. DeprecationWarning) /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. DeprecationWarning ~ On Tuesday, January 8, 2013 3:03:47 PM UTC-8, David Trowbridge wrote: DeprecationWarnings are harmless. There's probably something else (either in the apache log or the reviewboard log). -David On Tue, Jan 8, 2013 at 3:01 PM, Custom Apps sme...@customapps.injavascript: wrote: Hi, Today, I upgraded my review board installation to 1.7.1. By doing this, My site is broken. I get internal server error. In the apache log file, I see the following lines. [Tue Jan 08 14:55:08 2013] [notice] Apache/2.2.14 (Ubuntu) Phusion_Passenger/2.2.7 PHP/5.3.2-1ubuntu4.17 with Suhosin-Patch mod_python/3.3.1 Python/2.6.5 mod_wsgi/2.8 configured -- resuming normal operations [Tue Jan 08 22:55:17 2013] [error] /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead [Tue Jan 08 22:55:17 2013] [error] import md5 [Tue Jan 08 22:55:19 2013] [error] /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead [Tue Jan 08 22:55:19 2013] [error] import md5 My apache config is VirtualHost *:80 ServerName review.board DocumentRoot /var/www/review.board/htdocs # Error handlers ErrorDocument 500 /errordocs/500.html WSGIPassAuthorization On WSGIScriptAlias / /var/www/review.board/htdocs/reviewboard.wsgi/ # Serve django pages Location / PythonPath ['/var/www/review.board/conf'] + sys.path SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings SetEnv PYTHON_EGG_CACHE /var/www/review.board/tmp/egg_cache SetEnv HOME /var/www/review.board/data
Re: Recent upgrade to 1.7.1 broke my site.
OK. My bad. Somehow I upgraded the wrong site. So the database was not upgraded and the error was coming of missing db tables. Doing rb-site upgrade for the correct host fixed this. Sorry for this. Thanks On Tuesday, January 8, 2013 3:03:47 PM UTC-8, David Trowbridge wrote: DeprecationWarnings are harmless. There's probably something else (either in the apache log or the reviewboard log). -David On Tue, Jan 8, 2013 at 3:01 PM, Custom Apps sme...@customapps.injavascript: wrote: Hi, Today, I upgraded my review board installation to 1.7.1. By doing this, My site is broken. I get internal server error. In the apache log file, I see the following lines. [Tue Jan 08 14:55:08 2013] [notice] Apache/2.2.14 (Ubuntu) Phusion_Passenger/2.2.7 PHP/5.3.2-1ubuntu4.17 with Suhosin-Patch mod_python/3.3.1 Python/2.6.5 mod_wsgi/2.8 configured -- resuming normal operations [Tue Jan 08 22:55:17 2013] [error] /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead [Tue Jan 08 22:55:17 2013] [error] import md5 [Tue Jan 08 22:55:19 2013] [error] /usr/lib/python2.6/dist-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead [Tue Jan 08 22:55:19 2013] [error] import md5 My apache config is VirtualHost *:80 ServerName review.board DocumentRoot /var/www/review.board/htdocs # Error handlers ErrorDocument 500 /errordocs/500.html WSGIPassAuthorization On WSGIScriptAlias / /var/www/review.board/htdocs/reviewboard.wsgi/ # Serve django pages Location / PythonPath ['/var/www/review.board/conf'] + sys.path SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings SetEnv PYTHON_EGG_CACHE /var/www/review.board/tmp/egg_cache SetEnv HOME /var/www/review.board/data SetHandler mod_python PythonHandler django.core.handlers.modpython PythonAutoReload Off #PythonDebug Off PythonDebug On # Used to run multiple mod_python sites in the same apache PythonInterpreter reviewboard_crs_aaryanapps_net /Location # Serve static media without running it through mod_python # (overrides the above) Location /media SetHandler None /Location Location /errordocs SetHandler None /Location Location /static SetHandler None /Location Directory /var/www/review.board/htdocs AllowOverride All /Directory # Alias static media requests to filesystem Alias /media /var/www/review.board/htdocs/media Alias /errordocs /var/www/review.board/htdocs/errordocs Alias /static /var/www/review.board/htdocs/static /VirtualHost Not sure what else to look for and where. Thanks, -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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: Error happens SVN HTTPS certificate not verified when adding a new repo.
I've worked around this issue: 1. login the server, run svn list https://. 2. accept the certificate permanently. 3. then copy files generated in ~/.subversion/auth/svn.simple(server) to /var/www/reviewboard(your site name)/data/.subversion/auth/svn.xxx 4. change the file/group ownership to www-data. 4. now you can add repo in the administration UI. 在 2013年1月8日星期二UTC+8下午10时02分38秒，sojan john写道： Hi all, I am also facing this issue on 1.7.1. Both buttons are disabled the error log says Server certificate verification failed: issuer is not trusted. The data directory is owned by apache2 user. I am using apache+ mod_wsgi. It will be a great help if somebody can suggest a solution. Thanks, Sojan On Tuesday, 8 January 2013 13:06:35 UTC+5:30, Bing wrote: Hi, all, When I create a new repo (SVN) with https:// link, the following error message shows after click Save button. A verified HTTPS certificate is required to connect to this repository. There were errors validating this certificate: The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually. Certificate information: Hostname: .xx.com Valid: from Thu, 03 Nov 2011 23:33:44 GMT until Sun, 02 Nov 2014 23:33:44 GMT Issuer: Fingerprint: xxx Do you trust this host, or do you want to go back and edit the repository information? then there are two buttons: I trust this host and Re-Edit repository however, the problem is that both buttons are gray. so I cannot click any one of them. My review board is 1.7.1. Anyone can get me help? Thanks BING -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- 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: Issue 2723 in reviewboard: Show issue status in dashboard
Comment #5 on issue 2723 by matthew@kitware.com: Show issue status in dashboard http://code.google.com/p/reviewboard/issues/detail?id=2723 Just showing unresolved issues would be a significant improvement. Three column choices for unresolved, resolved, and total (or five, adding also fixed and dropped?) are fine, but for me lower priority. Issue importance is a fine idea, but maybe best tracked as a separate report... -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2851 in reviewboard: Error: The patch to 'ProcessCVSFiles.java' didn't apply cleanly
Updates: Status: NeedInfo Comment #1 on issue 2851 by trowb...@gmail.com: Error: The patch to 'ProcessCVSFiles.java' didn't apply cleanly http://code.google.com/p/reviewboard/issues/detail?id=2851 How did you create your diff? What is in those .rej files? -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 658 in reviewboard: Error : The patch to 'filepath' didn't apply cleanly.
Comment #16 on issue 658 by trowb...@gmail.com: Error : The patch to 'filepath' didn't apply cleanly. http://code.google.com/p/reviewboard/issues/detail?id=658 Getting rejects usually indicates some problem with how the diff was generated. Check the .rej file to see what failed. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2833 in reviewboard: post-review needs to override git diff.renames option
Comment #2 on issue 2833 by matthew@kitware.com: post-review needs to override git diff.renames option http://code.google.com/p/reviewboard/issues/detail?id=2833 This is fixed as of bacdab01f33; can someone with adequate permissions please close? -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2833 in reviewboard: post-review needs to override git diff.renames option
Updates: Status: Fixed Comment #3 on issue 2833 by trowb...@gmail.com: post-review needs to override git diff.renames option http://code.google.com/p/reviewboard/issues/detail?id=2833 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2853 in reviewboard: Reviewer should be able to reopen issues
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2853 by brunon...@brunonery.com: Reviewer should be able to reopen issues http://code.google.com/p/reviewboard/issues/detail?id=2853 What version are you running? 1.7.1 What's the URL of the page this enhancement relates to, if any? https://reviewboard.thousandeyes.com/r/xxx/ Describe the enhancement and the motivation for it. The reviewer should be able to reopen an issue (specially a dropped one). Suppose, for instance, that the Submitter drops an issue (explaining why he won't fix it) but the Reviewer want to argue about it (e.g. because it violates coding standards). This would be a use case where the Reviewer should be able to reopen an issue. What operating system are you using? What browser? Mac OS X. Chrome. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2854 in reviewboard: Reviewer should be able to close issues
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2854 by brunon...@brunonery.com: Reviewer should be able to close issues http://code.google.com/p/reviewboard/issues/detail?id=2854 What version are you running? 1.7.1 What's the URL of the page this enhancement relates to, if any? https://reviewboard.thousandeyes.com/r/xxx/ Describe the enhancement and the motivation for it. The reviewer should be able to close an issue. Suppose, for instance, that the Submitter makes a change but is not sure if it fixes the issue. The Reviewer should be able to verify it and close it. Also, the Reviewer might change his mind about an issue being really an issue (and then s/he should be able to drop it). What operating system are you using? What browser? Mac OS X. Chrome. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2713 in reviewboard: Reviewer, not author, should mark issues as resolved/reopened
Updates: Summary: Reviewer, not author, should mark issues as resolved/reopened Comment #2 on issue 2713 by trowb...@gmail.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2713 in reviewboard: Reviewer, not author, should mark issues as resolved/reopened
Comment #3 on issue 2713 by trowb...@gmail.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 Issue 2853 has been merged into this issue. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2853 in reviewboard: Reviewer should be able to reopen issues
Updates: Status: Duplicate Mergedinto: 2713 Comment #1 on issue 2853 by trowb...@gmail.com: Reviewer should be able to reopen issues http://code.google.com/p/reviewboard/issues/detail?id=2853 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2713 in reviewboard: Reviewer, not author, should mark issues as resolved/reopened
Comment #4 on issue 2713 by trowb...@gmail.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 Issue 2854 has been merged into this issue. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2854 in reviewboard: Reviewer should be able to close issues
Updates: Status: Duplicate Mergedinto: 2713 Comment #1 on issue 2854 by trowb...@gmail.com: Reviewer should be able to close issues http://code.google.com/p/reviewboard/issues/detail?id=2854 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2238 in reviewboard: unicode error in postreview
Updates: Status: Fixed Comment #5 on issue 2238 by trowb...@gmail.com: unicode error in postreview http://code.google.com/p/reviewboard/issues/detail?id=2238 Pushed the fix to rbtools master (7b53c05). Thanks! -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2855 in reviewboard: Clicking into an issue on the summary doesn't focus on the issue
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2855 by brunon...@brunonery.com: Clicking into an issue on the summary doesn't focus on the issue http://code.google.com/p/reviewboard/issues/detail?id=2855 What version are you running? 1.7.1 What's the URL of the page containing the problem? http://reviewboard/r/xxx What steps will reproduce the problem? 1. Open a review 2. Click Collapse all to make sure comments/issues are collapsed 3. Click on an issue on the issue summary What is the expected output? What do you see instead? The clicked issue is focused. Instead, nothing happens. What operating system are you using? What browser? Mac OS X. Chrome. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2856 in reviewboard: Error in accessing the review link
Updates: Status: Invalid Comment #1 on issue 2856 by trowb...@gmail.com: Error in accessing the review link http://code.google.com/p/reviewboard/issues/detail?id=2856 You need to fill out the form. If you're able to provide the requested information, please add a comment and we'll reopen this. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
