Re: post-reivew WEB API?
Hi I'm facing a similar problem but I can not solve it with the fixes given above, is there something else I can try ? * Review Board: 1.5.4 * RBTools: 0.3.1 * SCM tool: Clearcase * I'm using mod_wsgi * I have the following setting on the conf/apache-wsgi.conf WSGIPassAuthorization On * Also tried adding this and restarting the httpd service Directory / Options FollowSymLinks AllowOverride None Order deny,allow /Directory but still getting Error creating review request: You are not logged in (HTTP 401, API Error 103) Notes : * As other people and I can log properly on the web ui using the same user/passw * using -n I can see that the diff are well formed Thanks in advance fede On Mar 9, 11:56 am, Chris Tandiono chris.tandi...@gmail.com wrote: Oh huh, that seems like that'd be it. I couldn't try it earlier (building flooded, power was out, then drive in the RAID started to flake) but that worked perfectly. Thanks. Chris On Tue, 08 Mar 2011 01:33:07 -0800, Christian Hammond chip...@chipx86.com wrote: Hi Chris, Assuming your install is from before RB 1.5.2, you need to make a small change to your Apache configuration. Try: http://www.reviewboard.org/docs/manual/dev/faq/#i-m-using-post-review... Christian -- 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: post-reivew WEB API?
Hi, Just to be sure, is your Apache configuration directly including our conf/apache-wsgi.conf? Or did you copy the contents of that file elsewhere when setting up the server? What authentication backend are you using? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Tue, Mar 29, 2011 at 11:08 PM, fede fede.n...@gmail.com wrote: Hi I'm facing a similar problem but I can not solve it with the fixes given above, is there something else I can try ? * Review Board: 1.5.4 * RBTools: 0.3.1 * SCM tool: Clearcase * I'm using mod_wsgi * I have the following setting on the conf/apache-wsgi.conf WSGIPassAuthorization On * Also tried adding this and restarting the httpd service Directory / Options FollowSymLinks AllowOverride None Order deny,allow /Directory but still getting Error creating review request: You are not logged in (HTTP 401, API Error 103) Notes : * As other people and I can log properly on the web ui using the same user/passw * using -n I can see that the diff are well formed Thanks in advance fede On Mar 9, 11:56 am, Chris Tandiono chris.tandi...@gmail.com wrote: Oh huh, that seems like that'd be it. I couldn't try it earlier (building flooded, power was out, then drive in the RAID started to flake) but that worked perfectly. Thanks. Chris On Tue, 08 Mar 2011 01:33:07 -0800, Christian Hammond chip...@chipx86.com wrote: Hi Chris, Assuming your install is from before RB 1.5.2, you need to make a small change to your Apache configuration. Try: http://www.reviewboard.org/docs/manual/dev/faq/#i-m-using-post-review. .. Christian -- 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: Review Board 1.5.5 released
On 03/28/2011 06:24 AM, Christian Hammond wrote: Hi everyone, Review Board 1.5.5 is out, and contains a variety of good bug fixes, plus a fix for a major installation problem caused by a new release to one of our dependencies, python-dateutil. Is the dependency on python-dateutil == 1.5 strict, or is is possible to use older versions with ReviewBoard 1.5.5? I've been using python-dateutil 1.2 with ReviewBoard 1.5.4 on Red Hat Enterprise Linux 5 for quite a while now. -- 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
The Python module mercurial is not installed.
So, I'm trying to add a locally hosted mercurial repository, and, when configuring the item, I get the error message 'The Python module mercurial is not installed' . (Windows Server 2003, python 2.6, reviewboard 1.5.5) I've got tortoiseHg 2.0.2 installed (with mercurial 1.8.1 installed with it). Not knowing what else to try, I did : easy_install mercurial Which output the following: Searching for mercurial Reading http://pypi.python.org/simple/mercurial/ Reading http://mercurial.selenic.com/ Reading http://www.selenic.com/mercurial Best match: mercurial 1.8.1 Downloading http://mercurial.selenic.com/release/mercurial-1.8.1.tar.gz Processing mercurial-1.8.1.tar.gz Running mercurial-1.8.1\setup.py -q bdist_egg --dist-dir c: \docume~1\brian\local s~1\temp\1\easy_install-xs_7vp\mercurial-1.8.1\egg-dist-tmp-cmstci error: Setup script exited with error: Unable to find vcvarsall.bat I did a search here, but didn't find any other posts related to this issue, so, I'm hoping someone here can make a suggestion to help get me back up and running. 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
new reviewboard user greetings
Hello... I just tried to drop a comment on an earlier thread, and couldn't, and then I found that the group has moderation turned on. So, I'm introducing myself,so that later, I can reply to the other topic. Anyhow, I've just completed an install of 1.5.5 on a windows 2003 server, and after a dozen or so false-starts, I've finally got a functional website.Still trying to figure out how to hook up my Mercurial repos to it though. 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: The Python module mercurial is not installed.
Brian, see the instructions at http://code.google.com/p/rdflib/issues/detail?id=104 . Regards, Alex K On Wed, Mar 30, 2011 at 11:45 AM, brian.ackermann brian.ackerm...@gmail.com wrote: So, I'm trying to add a locally hosted mercurial repository, and, when configuring the item, I get the error message 'The Python module mercurial is not installed' . (Windows Server 2003, python 2.6, reviewboard 1.5.5) I've got tortoiseHg 2.0.2 installed (with mercurial 1.8.1 installed with it). Not knowing what else to try, I did : easy_install mercurial Which output the following: Searching for mercurial Reading http://pypi.python.org/simple/mercurial/ Reading http://mercurial.selenic.com/ Reading http://www.selenic.com/mercurial Best match: mercurial 1.8.1 Downloading http://mercurial.selenic.com/release/mercurial-1.8.1.tar.gz Processing mercurial-1.8.1.tar.gz Running mercurial-1.8.1\setup.py -q bdist_egg --dist-dir c: \docume~1\brian\local s~1\temp\1\easy_install-xs_7vp\mercurial-1.8.1\egg-dist-tmp-cmstci error: Setup script exited with error: Unable to find vcvarsall.bat I did a search here, but didn't find any other posts related to this issue, so, I'm hoping someone here can make a suggestion to help get me back up and running. 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: The Python module mercurial is not installed.
Brian, also, it might be useful to see http://groups.google.com/group/reviewboard/browse_thread/thread/724d1a487d19363c/17cb0311d75a12be#17cb0311d75a12be Alex K On Wed, Mar 30, 2011 at 3:06 PM, Alex Kotchnev akoch...@gmail.com wrote: Brian, see the instructions at http://code.google.com/p/rdflib/issues/detail?id=104 . Regards, Alex K On Wed, Mar 30, 2011 at 11:45 AM, brian.ackermann brian.ackerm...@gmail.com wrote: So, I'm trying to add a locally hosted mercurial repository, and, when configuring the item, I get the error message 'The Python module mercurial is not installed' . (Windows Server 2003, python 2.6, reviewboard 1.5.5) I've got tortoiseHg 2.0.2 installed (with mercurial 1.8.1 installed with it). Not knowing what else to try, I did : easy_install mercurial Which output the following: Searching for mercurial Reading http://pypi.python.org/simple/mercurial/ Reading http://mercurial.selenic.com/ Reading http://www.selenic.com/mercurial Best match: mercurial 1.8.1 Downloading http://mercurial.selenic.com/release/mercurial-1.8.1.tar.gz Processing mercurial-1.8.1.tar.gz Running mercurial-1.8.1\setup.py -q bdist_egg --dist-dir c: \docume~1\brian\local s~1\temp\1\easy_install-xs_7vp\mercurial-1.8.1\egg-dist-tmp-cmstci error: Setup script exited with error: Unable to find vcvarsall.bat I did a search here, but didn't find any other posts related to this issue, so, I'm hoping someone here can make a suggestion to help get me back up and running. 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: ImproperlyConfigured: Error importing middleware reviewboard.admin.middleware: DLL load failed: The specified module could not be found.
I was able to get this working, just by un-installing the 2.3 pycrypto, and instead installing the 2.1 pycrypto in its place. On Jan 5, 3:18 am, mandrake mt02c...@gmail.com wrote: Ok, I got it working now, thanks for the hint! I had to install MinGW and build pycrypto with it. (for you other guys with the same problem: setup.py build -- compiler=mingw32) This is our project server and windows is the only option. In my own company I only use linux servers, and of course I've never encountered a DLL-hell there :) Thanks On 5 Jan, 00:19, D Krueger dekr...@gmail.com wrote: There is definitely a problem involving mod_wsgi, Python, and extensions built with MSVC. See the question Why do no Python DLLs built with MSVC load with mod_wsgi? that's on Stack Overflow:http://stackoverflow.com/questions/3706293/why-do-no-python-dlls-buil... The author there worked around by installing a pycrypto built with MinGW. On Jan 4, 10:38 am, mandrake mt02c...@gmail.com wrote: Ok, I reinstalled the cryptolibrary and ran the tests using setup.py test, ALL OK. I ran the tests with lowest trust level as well, no diff (runas /trustlevel:0x2 ...). So I figured it might be a user privilege thing, so I tried running the apache service as administrator, but there was no difference. This is seriously annoying. On 4 Jan, 16:10, mandrake mt02c...@gmail.com wrote: Ok, I've traced the problem to the Crypto library: [Tue Jan 04 16:00:22 2011] [error] File C:\\Python27\\lib\\site- packages\\reviewboard-1.5.1-py2.7.egg\\reviewboard\\diffviewer\ \forms.py, line 9, in module [Tue Jan 04 16:00:22 2011] [error] from reviewboard.diffviewer.diffutils import DEFAULT_DIFF_COMPAT_VERSION [Tue Jan 04 16:00:22 2011] [error] File C:\\Python27\\lib\\site- packages\\reviewboard-1.5.1-py2.7.egg\\reviewboard\\diffviewer\ \diffutils.py, line 30, in module [Tue Jan 04 16:00:22 2011] [error] from reviewboard.scmtools.core import PRE_CREATION, HEAD [Tue Jan 04 16:00:22 2011] [error] File C:\\Python27\\lib\\site- packages\\reviewboard-1.5.1-py2.7.egg\\reviewboard\\scmtools\ \core.py, line 5, in module [Tue Jan 04 16:00:22 2011] [error] from reviewboard.scmtools import sshutils [Tue Jan 04 16:00:22 2011] [error] File C:\\Python27\\lib\\site- packages\\reviewboard-1.5.1-py2.7.egg\\reviewboard\\scmtools\ \sshutils.py, line 5, in module [Tue Jan 04 16:00:22 2011] [error] import paramiko [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \paramiko\\__init__.py, line 69, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \paramiko\\transport.py, line 32, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \paramiko\\util.py, line 32, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \paramiko\\common.py, line 98, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \paramiko\\rng.py, line 23, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \Crypto\\Util\\randpool.py, line 30, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \Crypto\\Random\\__init__.py, line 28, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \Crypto\\Random\\OSRNG\\__init__.py, line 34, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \Crypto\\Random\\OSRNG\\nt.py, line 28, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \Crypto\\Random\\OSRNG\\winrandom.py, line 7, in module [Tue Jan 04 16:00:22 2011] [error] File build\\bdist.win32\\egg\ \Crypto\\Random\\OSRNG\\winrandom.py, line 6, in __bootstrap__ [Tue Jan 04 16:00:22 2011] [error] ImportError: DLL load failed: The specified module could not be found. I will try to find out more.. On 12 Dec 2010, 12:50, Dan birb...@gmail.com wrote: Have you found solution to this problem, I have the same problem now. Could anyone give some hints? Any help will be highly appreciated. On Dec 1, 3:59 am, Travis dahlke.tra...@gmail.com wrote: Trying to install Reviewboard 1.5.1 on Windows XP SP3 with Apache 2.2 and mod_wsgi. Below is my apache error log. In my browser I get stuck on Review Board is taking a nap. Any idea what's going on? How do I tell which DLL failed? [Tue Nov 30 13:40:12 2010] [error] [client 127.0.0.1] mod_wsgi (pid=14184): Exception occurred processing WSGI script 'C:/reviewboard/ htdocs/reviewboard.wsgi'. [Tue Nov 30 13:40:12 2010] [error] [client 127.0.0.1] Traceback (most recent call last): [Tue Nov 30 13:40:12 2010] [error] [client 127.0.0.1] File C:\
Re: The Python module mercurial is not installed.
I found an answer that worked very well for me... http://mercurial.selenic.com/downloads/ Mercurial 1.8.1 Python 2.6 package - x86 Windows I installed that, and then I was off and running! On Mar 30, 2:14 pm, Alex Kotchnev akoch...@gmail.com wrote: Brian, also, it might be useful to seehttp://groups.google.com/group/reviewboard/browse_thread/thread/724d1... Alex K On Wed, Mar 30, 2011 at 3:06 PM, Alex Kotchnev akoch...@gmail.com wrote: Brian, see the instructions at http://code.google.com/p/rdflib/issues/detail?id=104. Regards, Alex K On Wed, Mar 30, 2011 at 11:45 AM, brian.ackermann brian.ackerm...@gmail.com wrote: So, I'm trying to add a locally hosted mercurial repository, and, when configuring the item, I get the error message 'The Python module mercurial is not installed' . (Windows Server 2003, python 2.6, reviewboard 1.5.5) I've got tortoiseHg 2.0.2 installed (with mercurial 1.8.1 installed with it). Not knowing what else to try, I did : easy_install mercurial Which output the following: Searching for mercurial Readinghttp://pypi.python.org/simple/mercurial/ Readinghttp://mercurial.selenic.com/ Readinghttp://www.selenic.com/mercurial Best match: mercurial 1.8.1 Downloadinghttp://mercurial.selenic.com/release/mercurial-1.8.1.tar.gz Processing mercurial-1.8.1.tar.gz Running mercurial-1.8.1\setup.py -q bdist_egg --dist-dir c: \docume~1\brian\local s~1\temp\1\easy_install-xs_7vp\mercurial-1.8.1\egg-dist-tmp-cmstci error: Setup script exited with error: Unable to find vcvarsall.bat I did a search here, but didn't find any other posts related to this issue, so, I'm hoping someone here can make a suggestion to help get me back up and running. Thanks -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know athttp://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: Review Board 1.5.5 released
Hi Stephen, We can't really say some version 2.0 so I went with the latest stable. The setup script requires that version, but Review Board itself doesn't care (though I assume of course that there are bug fixes in 1.5, but I doubt we're really impacted by them). Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Mar 30, 2011 at 6:35 AM, Stephen Gallagher step...@gallagherhome.com wrote: On 03/28/2011 06:24 AM, Christian Hammond wrote: Hi everyone, Review Board 1.5.5 is out, and contains a variety of good bug fixes, plus a fix for a major installation problem caused by a new release to one of our dependencies, python-dateutil. Is the dependency on python-dateutil == 1.5 strict, or is is possible to use older versions with ReviewBoard 1.5.5? I've been using python-dateutil 1.2 with ReviewBoard 1.5.4 on Red Hat Enterprise Linux 5 for quite a while now. -- 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
error trying to create site
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated;
use settings.DATABASES instead.
DeprecationWarning
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:60: DeprecationWarning: Short names for ENGINE in database
configurations are deprecated. Prepend default.ENGINE with
'django.db.backends.'
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 'rb-
site')()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1177, in run
self.show_install_status()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1436, in show_install_status
site.sync_database)
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 703, in step
func()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 339, in sync_database
self.run_manage_command(syncdb, params)
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/__init__.py, line 438, in execute_manager
utility.execute()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/__init__.py, line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 191, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 219, in execute
self.validate()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 249, in validate
num_errors = get_validation_errors(s, app)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/validation.py, line 103, in get_validation_errors
connection.validation.validate_field(e, opts, f)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/mysql/validation.py, line 14, in validate_field
db_version = self.connection.get_server_version()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/mysql/base.py, line 338, in get_server_version
self.cursor()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/__init__.py, line 252, in cursor
cursor = util.CursorWrapper(self._cursor(), self)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/mysql/base.py, line 322, in _cursor
self.connection = Database.connect(**kwargs)
File /var/lib/python-support/python2.5/MySQLdb/__init__.py, line
74, in Connect
return Connection(*args, **kwargs)
File /var/lib/python-support/python2.5/MySQLdb/connections.py,
line 170, in __init__
super(Connection, self).__init__(*args, **kwargs2)
_mysql_exceptions.OperationalError: (1049, Unknown database
'reviewboard')
16:30(root) ~ $
--
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 trying to create site
Hi,
This is something we should mention during rb-site (guess we don't), but you
need to create the database first before running rb-site.
The reason is that creation of a database generally takes root/admin access,
but that a site is setup with a user that wouldn't (and shouldn't) have
rights to create databases. So, root needs to create the database and grant
rights to the user you intend to use (you never want to use root as your
user for the site for security reasons).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 1:41 PM, funeeldy funee...@yahoo.com wrote:
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated;
use settings.DATABASES instead.
DeprecationWarning
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:60: DeprecationWarning: Short names for ENGINE in database
configurations are deprecated. Prepend default.ENGINE with
'django.db.backends.'
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 'rb-
site')()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1177, in run
self.show_install_status()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1436, in show_install_status
site.sync_database)
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 703, in step
func()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 339, in sync_database
self.run_manage_command(syncdb, params)
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/__init__.py, line 438, in execute_manager
utility.execute()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/__init__.py, line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 191, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 219, in execute
self.validate()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 249, in validate
num_errors = get_validation_errors(s, app)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/validation.py, line 103, in get_validation_errors
connection.validation.validate_field(e, opts, f)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/mysql/validation.py, line 14, in validate_field
db_version = self.connection.get_server_version()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/mysql/base.py, line 338, in get_server_version
self.cursor()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/__init__.py, line 252, in cursor
cursor = util.CursorWrapper(self._cursor(), self)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/mysql/base.py, line 322, in _cursor
self.connection = Database.connect(**kwargs)
File /var/lib/python-support/python2.5/MySQLdb/__init__.py, line
74, in Connect
return Connection(*args, **kwargs)
File /var/lib/python-support/python2.5/MySQLdb/connections.py,
line 170, in __init__
super(Connection, self).__init__(*args, **kwargs2)
_mysql_exceptions.OperationalError: (1049, Unknown database
'reviewboard')
16:30(root) ~ $
--
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,
Re: error trying to create site
Thanks. That should definitely be in your instructions, since you appear to be
giving detailed steps. I was fooled into thinking you would guide me all the
way..
Now I get this error. I have moved to another server (centos). I have
installed all the packages you told me to install, and I have created a mysql
db
and a user with rites.
[root@buildtest01 etc]# rb-site install /var/www/reviews.example.com
Traceback (most recent call last):
File /usr/bin/rb-site, line 5, in ?
from pkg_resources import load_entry_point
File /usr/lib/python2.4/site-packages/pkg_resources.py, line 2479, in ?
working_set.require(__requires__)
File /usr/lib/python2.4/site-packages/pkg_resources.py, line 585, in require
needed = self.resolve(parse_requirements(requirements))
File /usr/lib/python2.4/site-packages/pkg_resources.py, line 483, in resolve
raise DistributionNotFound(req) # XXX put more info here
pkg_resources.DistributionNotFound: flup
[root@buildtest01 etc]# id
uid=0(root) gid=0(root)
groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)
[root@buildtest01 etc]# hostname
buildtest01
[root@buildtest01 etc]# ls /var/www
cgi-bin cobbler cobbler_webui_content error html icons manual
[root@buildtest01 etc]# yum install python
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* addons: mirror.metrocast.net
* base: mirrors.netdna.com
* epel: mirror.seas.harvard.edu
* extras: mirrors.netdna.com
* updates: mirrors.netdna.com
Setting up Install Process
Package python-2.4.3-27.el5_5.3.x86_64 already installed and latest version
Nothing to do
Regards and be well!
Marlene
From: Christian Hammond chip...@chipx86.com
To: reviewboard@googlegroups.com
Cc: funeeldy funee...@yahoo.com
Sent: Wed, March 30, 2011 4:55:29 PM
Subject: Re: error trying to create site
Hi,
This is something we should mention during rb-site (guess we don't), but you
need to create the database first before running rb-site.
The reason is that creation of a database generally takes root/admin access,
but
that a site is setup with a user that wouldn't (and shouldn't) have rights to
create databases. So, root needs to create the database and grant rights to the
user you intend to use (you never want to use root as your user for the site
for
security reasons).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 1:41 PM, funeeldy funee...@yahoo.com wrote:
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated;
use settings.DATABASES instead.
DeprecationWarning
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:60: DeprecationWarning: Short names for ENGINE in database
configurations are deprecated. Prepend default.ENGINE with
'django.db.backends.'
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 'rb-
site')()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1177, in run
self.show_install_status()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1436, in show_install_status
site.sync_database)
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 703, in step
func()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 339, in sync_database
self.run_manage_command(syncdb, params)
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/__init__.py, line 438, in execute_manager
utility.execute()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/__init__.py, line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 191, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 219, in execute
self.validate()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 249, in validate
num_errors = get_validation_errors(s, app)
File
Re: error trying to create site
Evidently, the install of reviewboard failed and I didn't notice.
[root@buildtest01 etc]# easy_install ReviewBoard
Searching for ReviewBoard
Best match: ReviewBoard 1.5.5
Processing ReviewBoard-1.5.5-py2.4.egg
ReviewBoard 1.5.5 is already the active version in easy-install.pth
Installing rb-site script to /usr/bin
Installing rbssh script to /usr/bin
Using /usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg
Processing dependencies for ReviewBoard
Searching for pycrypto=1.9
Reading http://downloads.reviewboard.org/mirror/
Reading http://downloads.reviewboard.org/releases/ReviewBoard/1.5/
Reading http://pypi.python.org/simple/pycrypto/
Reading http://pycrypto.sourceforge.net
Reading http://www.pycrypto.org/
Download error: (101, 'Network is unreachable') -- Some packages may not be
found!
Reading http://www.amk.ca/python/code/crypto
Best match: pycrypto 2.3
Downloading http://www.pycrypto.org/files/pycrypto-2.3.tar.gz
error: Download error for http://www.pycrypto.org/files/pycrypto-2.3.tar.gz:
(101, 'Network is unreachable')
[root@buildtest01 etc]#
Regards and be well!
Marlene
From: Christian Hammond chip...@chipx86.com
To: reviewboard@googlegroups.com
Cc: funeeldy funee...@yahoo.com
Sent: Wed, March 30, 2011 4:55:29 PM
Subject: Re: error trying to create site
Hi,
This is something we should mention during rb-site (guess we don't), but you
need to create the database first before running rb-site.
The reason is that creation of a database generally takes root/admin access,
but
that a site is setup with a user that wouldn't (and shouldn't) have rights to
create databases. So, root needs to create the database and grant rights to the
user you intend to use (you never want to use root as your user for the site
for
security reasons).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 1:41 PM, funeeldy funee...@yahoo.com wrote:
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated;
use settings.DATABASES instead.
DeprecationWarning
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:60: DeprecationWarning: Short names for ENGINE in database
configurations are deprecated. Prepend default.ENGINE with
'django.db.backends.'
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 'rb-
site')()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1177, in run
self.show_install_status()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1436, in show_install_status
site.sync_database)
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 703, in step
func()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 339, in sync_database
self.run_manage_command(syncdb, params)
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/__init__.py, line 438, in execute_manager
utility.execute()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/__init__.py, line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 191, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 219, in execute
self.validate()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/base.py, line 249, in validate
num_errors = get_validation_errors(s, app)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
core/management/validation.py, line 103, in get_validation_errors
connection.validation.validate_field(e, opts, f)
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/mysql/validation.py, line 14, in validate_field
db_version = self.connection.get_server_version()
File /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/
db/backends/mysql/base.py, line 338, in get_server_version
self.cursor()
File
Re: error trying to create site
Ok.. I got past the problems with pycrypto and installed reviewboard.. not the
rb-site is failing again.. I have created a database named reviewboard and a
user named admin which has all rights. Is the problem with my version of mysql?
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/__init__.py:19:
DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES
instead.
DeprecationWarning
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/__init__.py:60:
DeprecationWarning: Short names for ENGINE in database configurations are
deprecated. Prepend default.ENGINE with 'django.db.backends.'
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 7, in ?
sys.exit(
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 1611, in main
command.run()
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 1177, in run
self.show_install_status()
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 1436, in show_install_status
site.sync_database)
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 703, in step
func()
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 339, in sync_database
self.run_manage_command(syncdb, params)
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 377, in run_manage_command
fix_django_evolution_issues(reviewboard.settings)
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/admin/migration.py,
line 13, in fix_django_evolution_issues
import django.db.models.fields as model_fields
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/__init__.py,
line 78, in ?
connection = connections[DEFAULT_DB_ALIAS]
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/utils.py,
line
93, in __getitem__
backend = load_backend(db['ENGINE'])
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/utils.py,
line
33, in load_backend
return import_module('.base', backend_name)
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/utils/importlib.py,
line 35, in import_module
__import__(name)
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/backends/mysql/base.py,
line 23, in ?
raise ImproperlyConfigured(MySQLdb-1.2.1p2 or newer is required; you have
%s % Database.__version__)
django.core.exceptions.ImproperlyConfigured: MySQLdb-1.2.1p2 or newer is
required; you have 1.2.1
[root@buildtest01 ~]#
Regards and be well!
Marlene
From: Christian Hammond chip...@chipx86.com
To: reviewboard@googlegroups.com
Cc: funeeldy funee...@yahoo.com
Sent: Wed, March 30, 2011 4:55:29 PM
Subject: Re: error trying to create site
Hi,
This is something we should mention during rb-site (guess we don't), but you
need to create the database first before running rb-site.
The reason is that creation of a database generally takes root/admin access,
but
that a site is setup with a user that wouldn't (and shouldn't) have rights to
create databases. So, root needs to create the database and grant rights to the
user you intend to use (you never want to use root as your user for the site
for
security reasons).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 1:41 PM, funeeldy funee...@yahoo.com wrote:
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated;
use settings.DATABASES instead.
DeprecationWarning
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:60: DeprecationWarning: Short names for ENGINE in database
configurations are deprecated. Prepend default.ENGINE with
'django.db.backends.'
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 'rb-
site')()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1177, in run
self.show_install_status()
File /usr/lib/python2.5/site-packages/ReviewBoard-1.5.5-py2.5.egg/
reviewboard/cmdline/rbsite.py, line 1436, in
Re: error trying to create site
Yes, it seems you need to upgrade your MySQLdb Python module. This
requirement is imposed by Django, not us. Unfortunately, I don't think we
can programatically know what their requirement is.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 3:03 PM, Marlene funee...@yahoo.com wrote:
Ok.. I got past the problems with pycrypto and installed reviewboard.. not
the rb-site is failing again.. I have created a database named reviewboard
and a user named admin which has all rights. Is the problem with my version
of mysql?
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/__init__.py:19:
DeprecationWarning: settings.DATABASE_* is deprecated; use
settings.DATABASES instead.
DeprecationWarning
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/__init__.py:60:
DeprecationWarning: Short names for ENGINE in database configurations are
deprecated. Prepend default.ENGINE with 'django.db.backends.'
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 7, in ?
sys.exit(
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 1611, in main
command.run()
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 1177, in run
self.show_install_status()
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 1436, in show_install_status
site.sync_database)
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 703, in step
func()
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 339, in sync_database
self.run_manage_command(syncdb, params)
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/cmdline/rbsite.py,
line 377, in run_manage_command
fix_django_evolution_issues(reviewboard.settings)
File
/usr/lib/python2.4/site-packages/ReviewBoard-1.5.5-py2.4.egg/reviewboard/admin/migration.py,
line 13, in fix_django_evolution_issues
import django.db.models.fields as model_fields
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/__init__.py,
line 78, in ?
connection = connections[DEFAULT_DB_ALIAS]
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/utils.py,
line 93, in __getitem__
backend = load_backend(db['ENGINE'])
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/utils.py,
line 33, in load_backend
return import_module('.base', backend_name)
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/utils/importlib.py,
line 35, in import_module
__import__(name)
File
/usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/backends/mysql/base.py,
line 23, in ?
raise ImproperlyConfigured(MySQLdb-1.2.1p2 or newer is required; you
have %s % Database.__version__)
django.core.exceptions.ImproperlyConfigured: MySQLdb-1.2.1p2 or newer is
required; you have 1.2.1
[root@buildtest01 ~]#
Regards and be well!
Marlene
--
*From:* Christian Hammond chip...@chipx86.com
*To:* reviewboard@googlegroups.com
*Cc:* funeeldy funee...@yahoo.com
*Sent:* Wed, March 30, 2011 4:55:29 PM
*Subject:* Re: error trying to create site
Hi,
This is something we should mention during rb-site (guess we don't), but
you need to create the database first before running rb-site.
The reason is that creation of a database generally takes root/admin
access, but that a site is setup with a user that wouldn't (and shouldn't)
have rights to create databases. So, root needs to create the database and
grant rights to the user you intend to use (you never want to use root as
your user for the site for security reasons).
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 1:41 PM, funeeldy funee...@yahoo.com wrote:
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated;
use settings.DATABASES instead.
DeprecationWarning
/usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/
__init__.py:60: DeprecationWarning: Short names for ENGINE in database
configurations are deprecated. Prepend default.ENGINE with
'django.db.backends.'
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
trying to setup post-review with perforce got the following error.
I am able to ping and telnet to the perforce server from my
client my repository setting is:
Hosting service: Custom
Repository type: Perforce
Path: perforce.example.com
Username: useranme
Password: password
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None, Supports
changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to /tmp/tmpzT7Exi
p4 print -o /tmp/tmpzT7Exi -q //depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpzT7Exi
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated 1.0
API
== Review Board Login Required
Enter username and password for Review Board at
http://vmreviews.lab-example.com/reviews/
Looking for 'vmreviews.lab-example /reviews/' cookie in
/home/build/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request on perforce.example.com for None
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/new/:
{'repository_path': 'perforce.example.com'}
Review request created
Attempting to set field 'summary' to 'p4-testing-change' for review request
'12'
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/draft/set/:
{'summary': 'p4-testing-change'}
Uploading diff, size: 361
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/diff/new/:
{}
Got API Error 105 (HTTP code 200): One or more fields had errors
Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server
failed; check $P4PORT.\nTCP connect to perforce.example.com
failed.\nperforce.example.com: service unknown.\n']}, u'stat': u'fail',
u'err': {u'msg': u'One or more fields had errors', u'code': 105},
u'deprecated': {u'in_version': u'1.5'}}
Error uploading diff
The generated diff file was empty. This usually means no files were
modified in this change.
Try running with --output-diff and --debug for more information.
Your review request still exists, but the diff is not attached.
$ post-review --debug --summary=p4-testing-change --output-diff
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None, Supports
changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to /tmp/tmpDCtOBl
p4 print -o /tmp/tmpDCtOBl -q //depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpDCtOBl
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated 1.0
API
--- //depot/Iocaine/main/Product/build.xml //depot/Iocaine/main/
Product/build.xml#197
+++ //depot/Iocaine/main/Product/build.xml 2011-03-30 06:09:25
@@ -1,4 +1,5 @@
project name=Iocaine default=all-nodist basedir=.
+project name=Iocaine default=all-nodist basedir=.
property environment=env /
property name=src_dir value=src/ /
$
what does check $P4PORT.\nTCP connect to perforce.example.com
failed. mean?
--
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: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
Sounds like the Review Board server isn't able to contact your Perforce
server for some reason. Might want to try SSHing into that server,
temporarily setting P4PORT in your session, and accessing the server. Or try
pinging it for an initial test.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 3:36 PM, storms v...@sendmail.com wrote:
trying to setup post-review with perforce got the following error.
I am able to ping and telnet to the perforce server from my
client my repository setting is:
Hosting service: Custom
Repository type: Perforce
Path: perforce.example.com
Username: useranme
Password: password
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to
/tmp/tmpzT7Exi
p4 print -o /tmp/tmpzT7Exi -q
//depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpzT7Exi
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated
1.0 API
== Review Board Login Required
Enter username and password for Review Board at
http://vmreviews.lab-example.com/reviews/
Looking for 'vmreviews.lab-example /reviews/' cookie in
/home/build/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request on perforce.example.com for None
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/new/:
{'repository_path': 'perforce.example.com'}
Review request created
Attempting to set field 'summary' to 'p4-testing-change' for review
request '12'
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/draft/set/:
{'summary': 'p4-testing-change'}
Uploading diff, size: 361
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/diff/new/:
{}
Got API Error 105 (HTTP code 200): One or more fields had errors
Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server
failed; check $P4PORT.\nTCP connect to perforce.example.com failed.\
nperforce.example.com: service unknown.\n']}, u'stat': u'fail', u'err':
{u'msg': u'One or more fields had errors', u'code': 105}, u'deprecated':
{u'in_version': u'1.5'}}
Error uploading diff
The generated diff file was empty. This usually means no files were
modified in this change.
Try running with --output-diff and --debug for more information.
Your review request still exists, but the diff is not attached.
$ post-review --debug --summary=p4-testing-change --output-diff
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to
/tmp/tmpDCtOBl
p4 print -o /tmp/tmpDCtOBl -q
//depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpDCtOBl
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated
1.0 API
--- //depot/Iocaine/main/Product/build.xml //depot/Iocaine/main/
Product/build.xml#197
+++ //depot/Iocaine/main/Product/build.xml 2011-03-30 06:09:25
@@ -1,4 +1,5 @@
project name=Iocaine default=all-nodist basedir=.
+project name=Iocaine default=all-nodist basedir=.
property environment=env /
property name=src_dir value=src/ /
$
what does check $P4PORT.\nTCP connect to perforce.example.com
failed. mean?
--
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: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
On my client I have set
export P4PORT=perforce.example.com:1666
Ping perforce.example.com works
PING repoman.example.com (x.y.z.a) 56(84) bytes of data.
64 bytes from repoman.example.com (x.y.z.a): icmp_seq=1 ttl=63 time=0.504 ms
64 bytes from repoman.example.com (x.y.z.a): icmp_seq=2 ttl=63 time=0.335 ms
$ telnet perforce.example.com 1666
Trying x.y.z.a...
Connected to perforce.example.com (x.y.z.a).
Escape character is '^]'.
;;xfiles5server3server217funprotocol^]
telnet
From: chip...@gmail.com [mailto:chip...@gmail.com] On Behalf Of Christian
Hammond
Sent: Wednesday, March 30, 2011 3:41 PM
To: reviewboard@googlegroups.com
Cc: Vincent Yee
Subject: Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or
more fields had errors
Sounds like the Review Board server isn't able to contact your Perforce server
for some reason. Might want to try SSHing into that server, temporarily setting
P4PORT in your session, and accessing the server. Or try pinging it for an
initial test.
Christian
--
Christian Hammond - chip...@chipx86.commailto:chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 3:36 PM, storms
v...@sendmail.commailto:v...@sendmail.com wrote:
trying to setup post-review with perforce got the following error.
I am able to ping and telnet to the perforce server from my
client my repository setting is:
Hosting service: Custom
Repository type: Perforce
Path: perforce.example.comhttp://perforce.example.com
Username: useranme
Password: password
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path:
repoman.example.com:1666http://repoman.example.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to /tmp/tmpzT7Exi
p4 print -o /tmp/tmpzT7Exi -q //depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpzT7Exi
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated 1.0
API
== Review Board Login Required
Enter username and password for Review Board at
http://vmreviews.lab-example.com/reviews/
Looking for 'vmreviews.lab-example /reviews/' cookie in
/home/build/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request on
perforce.example.comhttp://perforce.example.com for None
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/new/:
{'repository_path': 'perforce.example.comhttp://perforce.example.com'}
Review request created
Attempting to set field 'summary' to 'p4-testing-change' for review request
'12'
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/draft/set/:
{'summary': 'p4-testing-change'}
Uploading diff, size: 361
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/diff/new/:
{}
Got API Error 105 (HTTP code 200): One or more fields had errors
Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server
failed; check $P4PORT.\nTCP connect to
perforce.example.comhttp://perforce.example.com
failed.\nperforce.example.comhttp://nperforce.example.com: service
unknown.\n']}, u'stat': u'fail', u'err': {u'msg': u'One or more fields had
errors', u'code': 105}, u'deprecated': {u'in_version': u'1.5'}}
Error uploading diff
The generated diff file was empty. This usually means no files were
modified in this change.
Try running with --output-diff and --debug for more information.
Your review request still exists, but the diff is not attached.
$ post-review --debug --summary=p4-testing-change --output-diff
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path:
repoman.example.com:1666http://repoman.example.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to /tmp/tmpDCtOBl
p4 print -o /tmp/tmpDCtOBl -q //depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpDCtOBl
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated 1.0
API
--- //depot/Iocaine/main/Product/build.xml //depot/Iocaine/main/
Product/build.xml#197
+++ //depot/Iocaine/main/Product/build.xml 2011-03-30 06:09:25
@@ -1,4 +1,5 @@
project name=Iocaine default=all-nodist basedir=.
+project name=Iocaine
Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
The repository entry you showed doesn't seem to have :1666? Try adding the
port.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:00 PM, Vincent Yee v...@sendmail.com wrote:
On my client I have set
export P4PORT=perforce.example.com:1666
Ping perforce.example.com works
PING repoman.example.com (x.y.z.a) 56(84) bytes of data.
64 bytes from repoman.example.com (x.y.z.a): icmp_seq=1 ttl=63 time=0.504
ms
64 bytes from repoman.example.com (x.y.z.a): icmp_seq=2 ttl=63 time=0.335
ms
$ telnet perforce.example.com 1666
Trying x.y.z.a...
Connected to perforce.example.com (x.y.z.a).
Escape character is '^]'.
;;xfiles5server3server217funprotocol^]
telnet
--
*From:* chip...@gmail.com [mailto:chip...@gmail.com] *On Behalf Of *Christian
Hammond
*Sent:* Wednesday, March 30, 2011 3:41 PM
*To:* reviewboard@googlegroups.com
*Cc:* Vincent Yee
*Subject:* Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200):
One or more fields had errors
Sounds like the Review Board server isn't able to contact your Perforce
server for some reason. Might want to try SSHing into that server,
temporarily setting P4PORT in your session, and accessing the server. Or try
pinging it for an initial test.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 3:36 PM, storms v...@sendmail.com wrote:
trying to setup post-review with perforce got the following error.
I am able to ping and telnet to the perforce server from my
client my repository setting is:
Hosting service: Custom
Repository type: Perforce
Path: perforce.example.com
Username: useranme
Password: password
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to
/tmp/tmpzT7Exi
p4 print -o /tmp/tmpzT7Exi -q
//depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpzT7Exi
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated
1.0 API
== Review Board Login Required
Enter username and password for Review Board at
http://vmreviews.lab-example.com/reviews/
Looking for 'vmreviews.lab-example /reviews/' cookie in
/home/build/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request on perforce.example.com for None
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/new/:
{'repository_path': 'perforce.example.com'}
Review request created
Attempting to set field 'summary' to 'p4-testing-change' for review
request '12'
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/draft/set/:
{'summary': 'p4-testing-change'}
Uploading diff, size: 361
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/diff/new/:
{}
Got API Error 105 (HTTP code 200): One or more fields had errors
Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server
failed; check $P4PORT.\nTCP connect to perforce.example.com failed.\
nperforce.example.com: service unknown.\n']}, u'stat': u'fail', u'err':
{u'msg': u'One or more fields had errors', u'code': 105}, u'deprecated':
{u'in_version': u'1.5'}}
Error uploading diff
The generated diff file was empty. This usually means no files were
modified in this change.
Try running with --output-diff and --debug for more information.
Your review request still exists, but the diff is not attached.
$ post-review --debug --summary=p4-testing-change --output-diff
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to
/tmp/tmpDCtOBl
p4 print -o /tmp/tmpDCtOBl -q
//depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpDCtOBl
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated
1.0 API
--- //depot/Iocaine/main/Product/build.xml //depot/Iocaine/main/
Product/build.xml#197
+++
Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
Try putting the :1666 one in Mirror Path.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:19 PM, Vincent Yee v...@sendmail.com wrote:
I get a different error message if I have :1666 on my repository entry
(Got API Error 206 (HTTP code 200)
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.smi.sendmail.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to
/tmp/tmpIdYR5a
p4 print -o /tmp/tmpIdYR5a -q
//depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpIdYR5a
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated
1.0 API
== Review Board Login Required
Enter username and password for Review Board at
http://vmreviews.lab-example.com/reviews/
Looking for 'vmreviews.qa-lab.sendmail.com /reviews/' cookie in
/home/build/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request on perforce.example.com for None
HTTP POSTing to
http://vmreviews.qa-lab.sendmail.com/reviews/api/json/reviewrequests/new/:
{'repository_path': 'perforce.smi.sendmail.com'}
Got API Error 206 (HTTP code 200): The repository path specified is not
in the list of known repositories
Error data: {u'repository_path': u'perforce.example.com', u'stat':
u'fail', u'err': {u'msg': u'The repository path specified is not in the list
of known repositories', u'code': 206}, u'deprecated': {u'in_version':
u'1.5'}}
There was an error creating this review request.
The repository path repoman.example.com:1666 is not in the
list of known repositories on the server.
Ask the administrator to add this repository to the Review Board server.
For information on adding repositories, please read
http://www.reviewboard.org/docs/manual/dev/admin/management/repositories/
--
*From:* chip...@gmail.com [mailto:chip...@gmail.com] *On Behalf Of *Christian
Hammond
*Sent:* Wednesday, March 30, 2011 4:08 PM
*To:* Vincent Yee
*Cc:* reviewboard@googlegroups.com
*Subject:* Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200):
One or more fields had errors
The repository entry you showed doesn't seem to have :1666? Try adding the
port.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:00 PM, Vincent Yee v...@sendmail.com wrote:
On my client I have set
export P4PORT=perforce.example.com:1666
Ping perforce.example.com works
PING repoman.example.com (x.y.z.a) 56(84) bytes of data.
64 bytes from repoman.example.com (x.y.z.a): icmp_seq=1 ttl=63 time=0.504
ms
64 bytes from repoman.example.com (x.y.z.a): icmp_seq=2 ttl=63 time=0.335
ms
$ telnet perforce.example.com 1666
Trying x.y.z.a...
Connected to perforce.example.com (x.y.z.a).
Escape character is '^]'.
;;xfiles5server3server217funprotocol^]
telnet
--
*From:* chip...@gmail.com [mailto:chip...@gmail.com] *On Behalf Of *Christian
Hammond
*Sent:* Wednesday, March 30, 2011 3:41 PM
*To:* reviewboard@googlegroups.com
*Cc:* Vincent Yee
*Subject:* Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200):
One or more fields had errors
Sounds like the Review Board server isn't able to contact your Perforce
server for some reason. Might want to try SSHing into that server,
temporarily setting P4PORT in your session, and accessing the server. Or try
pinging it for an initial test.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 3:36 PM, storms v...@sendmail.com wrote:
trying to setup post-review with perforce got the following error.
I am able to ping and telnet to the perforce server from my
client my repository setting is:
Hosting service: Custom
Repository type: Perforce
Path: perforce.example.com
Username: useranme
Password: password
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
RE: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
Ok now it's a different error with
Mirror path: perforce.example.com:1666
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/20/draft/set/:
{'summary': 'p4-testing-change'}
Uploading diff, size: 361
HTTP POSTing to
http://vmreviews.qa-lab.sendmail.com/reviews/api/json/reviewrequests/20/diff/new/:
{}
Got API Error 105 (HTTP code 200): One or more fields had errors
Error data: {u'fields': {u'path': [u'[Errno 2] No such file or
directory']}, u'stat': u'fail', u'err': {u'msg': u'One or more fields had
errors', u'code': 105}, u'deprecated': {u'in_version': u'1.5'}}
Error uploading diff
The generated diff file was empty. This usually means no files were
modified in this change.
Try running with --output-diff and --debug for more information.
Your review request still exists, but the diff is not attached.
[build@vmtemp01 Product]$
If putting jsut :1666 in Mirror path,
It returns the original error:
Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server
failed; check $P4PORT.\nTCP connect to :1666 failed.\nconnect: :1666:
Connection refused\n']}, u'stat': u'fail', u'err': {u'msg': u'One or more
fields had errors', u'code': 105}, u'deprecated': {u'in_version': u'1.5'}}
From: chip...@gmail.com [mailto:chip...@gmail.com] On Behalf Of Christian
Hammond
Sent: Wednesday, March 30, 2011 4:23 PM
To: Vincent Yee
Cc: reviewboard@googlegroups.com
Subject: Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or
more fields had errors
Try putting the :1666 one in Mirror Path.
Christian
--
Christian Hammond - chip...@chipx86.commailto:chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:19 PM, Vincent Yee
v...@sendmail.commailto:v...@sendmail.com wrote:
I get a different error message if I have :1666 on my repository entry (Got API
Error 206 (HTTP code 200)
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path:
repoman.smi.sendmail.com:1666http://repoman.smi.sendmail.com:1666, Base
path: None, Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to /tmp/tmpIdYR5a
p4 print -o /tmp/tmpIdYR5a -q //depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpIdYR5a
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated 1.0
API
== Review Board Login Required
Enter username and password for Review Board at
http://vmreviews.lab-example.com/reviews/
Looking for
'vmreviews.qa-lab.sendmail.comhttp://vmreviews.qa-lab.sendmail.com
/reviews/' cookie in /home/build/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request on
perforce.example.comhttp://perforce.example.com for None
HTTP POSTing to
http://vmreviews.qa-lab.sendmail.com/reviews/api/json/reviewrequests/new/:
{'repository_path':
'perforce.smi.sendmail.comhttp://perforce.smi.sendmail.com'}
Got API Error 206 (HTTP code 200): The repository path specified is not in
the list of known repositories
Error data: {u'repository_path':
u'perforce.example.comhttp://perforce.example.com', u'stat': u'fail',
u'err': {u'msg': u'The repository path specified is not in the list of
known repositories', u'code': 206}, u'deprecated': {u'in_version': u'1.5'}}
There was an error creating this review request.
The repository path repoman.example.com:1666http://repoman.example.com:1666
is not in the
list of known repositories on the server.
Ask the administrator to add this repository to the Review Board server.
For information on adding repositories, please read
http://www.reviewboard.org/docs/manual/dev/admin/management/repositories/
From: chip...@gmail.commailto:chip...@gmail.com
[mailto:chip...@gmail.commailto:chip...@gmail.com] On Behalf Of Christian
Hammond
Sent: Wednesday, March 30, 2011 4:08 PM
To: Vincent Yee
Cc: reviewboard@googlegroups.commailto:reviewboard@googlegroups.com
Subject: Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or
more fields had errors
The repository entry you showed doesn't seem to have :1666? Try adding the port.
Christian
--
Christian Hammond - chip...@chipx86.commailto:chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:00 PM, Vincent Yee
v...@sendmail.commailto:v...@sendmail.com wrote:
On my client I have set
export P4PORT=perforce.example.com:1666http://perforce.example.com:1666
Ping perforce.example.comhttp://perforce.example.com works
PING
Re: post-reivew WEB API?
Hi Christian, Thanks for your pormpt response, We are using LDAP, and it is working fine from the WEB UI (as before) Yes i'm including it directly, the apache-wsgi.conf, it looks like this 1 VirtualHost *:80 2 ServerName reviewboard.al.com.au 3 DocumentRoot /var/www/reviewboard/rnd/htdocs 4 5 # Error handlers 6 ErrorDocument 500 /errordocs/500.html 7 8 WSGIPassAuthorization On 9 WSGIScriptAlias / /var/www/reviewboard/rnd/htdocs/ reviewboard.wsgi 10 11 Directory /var/www/reviewboard/rnd/htdocs 12 AllowOverride All 13 /Directory 14 15 # Alias static media requests to filesystem 16 Alias /media /var/www/reviewboard/rnd/htdocs/media 17 Alias /errordocs /var/www/reviewboard/rnd/htdocs/ errordocs 18 /VirtualHost We had it working before with RB 1.0.8, so we have not changed the apache conf, we just upgrade to 1.5.4 and RBTools: 0.3.1 and the post- review stop working There is no message in the httpd.erro.log when I try to submit the post-review We upgrade RB and started with a clean DB, so we did the rb-site install. This is the only error on the http/error.log But I think it is not related [error] /var/virtualenv/REVIEWBOARD-1/lib/python2.5/site-packages/ Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This application uses RandomPool, which is BROKEN in older releases. See http://www.pycrypto.org/randpool-broken Fede On Mar 30, 5:46 pm, Christian Hammond chip...@chipx86.com wrote: Hi, Just to be sure, is your Apache configuration directly including our conf/apache-wsgi.conf? Or did you copy the contents of that file elsewhere when setting up the server? What authentication backend are you using? Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Tue, Mar 29, 2011 at 11:08 PM, fede fede.n...@gmail.com wrote: Hi I'm facing a similar problem but I can not solve it with the fixes given above, is there something else I can try ? * Review Board: 1.5.4 * RBTools: 0.3.1 * SCM tool: Clearcase * I'm using mod_wsgi * I have the following setting on the conf/apache-wsgi.conf WSGIPassAuthorization On * Also tried adding this and restarting the httpd service Directory / Options FollowSymLinks AllowOverride None Order deny,allow /Directory but still getting Error creating review request: You are not logged in (HTTP 401, API Error 103) Notes : * As other people and I can log properly on the web ui using the same user/passw * using -n I can see that the diff are well formed Thanks in advance fede On Mar 9, 11:56 am, Chris Tandiono chris.tandi...@gmail.com wrote: Oh huh, that seems like that'd be it. I couldn't try it earlier (building flooded, power was out, then drive in the RAID started to flake) but that worked perfectly. Thanks. Chris On Tue, 08 Mar 2011 01:33:07 -0800, Christian Hammond chip...@chipx86.com wrote: Hi Chris, Assuming your install is from before RB 1.5.2, you need to make a small change to your Apache configuration. Try: http://www.reviewboard.org/docs/manual/dev/faq/#i-m-using-post-review. .. Christian -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know athttp://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: post-reivew WEB API?
Hi Fede, The reason it's broken now is that we've moved to using Basic HTTP auth for the API. This is a standard protocol, and things have supported it forever, but wsgi (and fastcgi) by default actually specifically filter out any Authorization headers related to it. That's what that directive is meant to prevent. The web UI itself doesn't use Basic HTTP auth, which is why you're not seeing the problem there. I don't know why it's not working for you. If that's the Apache file that your main Apache config is directly including, or those contents are in the main Apache config directly, then it should be solving the problem. The only other thing at this point that I can think of is if the web server actually wasn't restarted. Can you provide the full debug log (pass --debug) on post-review, with a login attempt? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Mar 30, 2011 at 5:08 PM, fede fede.n...@gmail.com wrote: Hi Christian, Thanks for your pormpt response, We are using LDAP, and it is working fine from the WEB UI (as before) Yes i'm including it directly, the apache-wsgi.conf, it looks like this 1 VirtualHost *:80 2 ServerName reviewboard.al.com.au 3 DocumentRoot /var/www/reviewboard/rnd/htdocs 4 5 # Error handlers 6 ErrorDocument 500 /errordocs/500.html 7 8 WSGIPassAuthorization On 9 WSGIScriptAlias / /var/www/reviewboard/rnd/htdocs/ reviewboard.wsgi 10 11 Directory /var/www/reviewboard/rnd/htdocs 12 AllowOverride All 13 /Directory 14 15 # Alias static media requests to filesystem 16 Alias /media /var/www/reviewboard/rnd/htdocs/media 17 Alias /errordocs /var/www/reviewboard/rnd/htdocs/ errordocs 18 /VirtualHost We had it working before with RB 1.0.8, so we have not changed the apache conf, we just upgrade to 1.5.4 and RBTools: 0.3.1 and the post- review stop working There is no message in the httpd.erro.log when I try to submit the post-review We upgrade RB and started with a clean DB, so we did the rb-site install. This is the only error on the http/error.log But I think it is not related [error] /var/virtualenv/REVIEWBOARD-1/lib/python2.5/site-packages/ Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This application uses RandomPool, which is BROKEN in older releases. See http://www.pycrypto.org/randpool-broken Fede On Mar 30, 5:46 pm, Christian Hammond chip...@chipx86.com wrote: Hi, Just to be sure, is your Apache configuration directly including our conf/apache-wsgi.conf? Or did you copy the contents of that file elsewhere when setting up the server? What authentication backend are you using? Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Tue, Mar 29, 2011 at 11:08 PM, fede fede.n...@gmail.com wrote: Hi I'm facing a similar problem but I can not solve it with the fixes given above, is there something else I can try ? * Review Board: 1.5.4 * RBTools: 0.3.1 * SCM tool: Clearcase * I'm using mod_wsgi * I have the following setting on the conf/apache-wsgi.conf WSGIPassAuthorization On * Also tried adding this and restarting the httpd service Directory / Options FollowSymLinks AllowOverride None Order deny,allow /Directory but still getting Error creating review request: You are not logged in (HTTP 401, API Error 103) Notes : * As other people and I can log properly on the web ui using the same user/passw * using -n I can see that the diff are well formed Thanks in advance fede On Mar 9, 11:56 am, Chris Tandiono chris.tandi...@gmail.com wrote: Oh huh, that seems like that'd be it. I couldn't try it earlier (building flooded, power was out, then drive in the RAID started to flake) but that worked perfectly. Thanks. Chris On Tue, 08 Mar 2011 01:33:07 -0800, Christian Hammond chip...@chipx86.com wrote: Hi Chris, Assuming your install is from before RB 1.5.2, you need to make a small change to your Apache configuration. Try: http://www.reviewboard.org/docs/manual/dev/faq/#i-m-using-post-review. .. Christian -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know athttp://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
Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
Okay, the No such file or directory indicates a configuration problem, but
is a step in the right direction. Some program you need is missing, and
Review Board's initial checks didn't catch it. Can you make sure that both
p4 and patch are both available on that system and accessible/executable?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:59 PM, Vincent Yee v...@sendmail.com wrote:
I tried with both in Mirror path:
perforce.example:1666 è Error data: {u'fields': {u'path': [u'[Errno
2] No such file or directory']}, u'stat': u'fail', u'err': {u'msg': u'One or
more fields had errors', u'code': 105}, u'deprecated': {u'in_version':
u'1.5'}}
:1666 è Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to
server failed; check $P4PORT.\nTCP connect to :1666 failed.\nconnect: :1666:
Connection refused\n']}, u'stat': u'fail', u'err': {u'msg': u'One or more
fields had errors', u'code': 105}, u'deprecated': {u'in_version': u'1.5'}}
--
*From:* chip...@gmail.com [mailto:chip...@gmail.com] *On Behalf Of *Christian
Hammond
*Sent:* Wednesday, March 30, 2011 4:42 PM
*To:* Vincent Yee
*Cc:* reviewboard@googlegroups.com
*Subject:* Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200):
One or more fields had errors
The error message says you're just using :1666.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:38 PM, Vincent Yee v...@sendmail.com wrote:
Ok now it’s a different error with
Mirror path: perforce.example.com:1666
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/20/draft/set/:
{'summary': 'p4-testing-change'}
Uploading diff, size: 361
HTTP POSTing to
http://vmreviews.qa-lab.sendmail.com/reviews/api/json/reviewrequests/20/diff/new/:
{}
Got API Error 105 (HTTP code 200): One or more fields had errors
Error data: {u'fields': {u'path': [u'[Errno 2] No such file or
directory']}, u'stat': u'fail', u'err': {u'msg': u'One or more fields had
errors', u'code': 105}, u'deprecated': {u'in_version': u'1.5'}}
Error uploading diff
The generated diff file was empty. This usually means no files were
modified in this change.
Try running with --output-diff and --debug for more information.
Your review request still exists, but the diff is not attached.
[build@vmtemp01 Product]$
If putting jsut :1666 in Mirror path,
It returns the original error:
Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server
failed; check $P4PORT.\nTCP connect to :1666 failed.\nconnect: :1666:
Connection refused\n']}, u'stat': u'fail', u'err': {u'msg': u'One or more
fields had errors', u'code': 105}, u'deprecated': {u'in_version': u'1.5'}}
--
*From:* chip...@gmail.com [mailto:chip...@gmail.com] *On Behalf Of *Christian
Hammond
*Sent:* Wednesday, March 30, 2011 4:23 PM
*To:* Vincent Yee
*Cc:* reviewboard@googlegroups.com
*Subject:* Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200):
One or more fields had errors
Try putting the :1666 one in Mirror Path.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:19 PM, Vincent Yee v...@sendmail.com wrote:
I get a different error message if I have :1666 on my repository entry (Got
API Error 206 (HTTP code 200)
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.smi.sendmail.com:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to
/tmp/tmpIdYR5a
p4 print -o /tmp/tmpIdYR5a -q
//depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpIdYR5a
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated
1.0 API
== Review Board Login Required
Enter username and password for Review Board at
http://vmreviews.lab-example.com/reviews/
Looking for 'vmreviews.qa-lab.sendmail.com /reviews/' cookie in
/home/build/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request on perforce.example.com for None
HTTP POSTing to
http://vmreviews.qa-lab.sendmail.com/reviews/api/json/reviewrequests/new/:
{'repository_path': 'perforce.smi.sendmail.com'}
Got API Error 206 (HTTP code 200): The repository path specified is
Successful upgrade from Reviewboard 1.0.5.1 to 1.5.5
We had a customized version of 1.0.5.1 and we now have a (less) customized version 1.5.5 (custom SCM back end and minor email/template tweaks). We're using Ubuntu 8.04.3 LTS (hardy) on x86 (same as the last time we upgraded, we've left the OS alone) . We had no problems at all with this upgrade! So unlike my previous upgrade reports this really is an uninteresting one :-) The only minor oddity was that setup tools needed to be upgraded. In our haste to upgrade we simply used easy_install for that (it may have been that apt-get would have found a new version). When the test upgrades had been done, a different OS version was used so this was our only surprise. We also went from Django-1.1.1 (we're behind a firewall so this old version has been fine for us) to Django-1.3 (other stuff was upgraded too, like Djblets-0.5.5 to Djblets-0.6.7, but this is one of the significant ones). The main reason for the upgrade was that we needed auth support for svn, we've wanted the other new features (drag-n-drop images, improved username lookup, ) for a while but we *needed* auth. Thanks again to everyone for making the upgrade path so easy, with great/clear documentation. We maybe brave soon and enable the Lucene support. Chris -- 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: post-reivew WEB API?
Hi Christian,
I'm restarting the web server every time I do any change, and checking
the httpd/error.logs to make sure it is restarted
We added ldap to the apache conf., we are close but not there yet
Here is the configuration, maybe you can spot something wrong
3 VirtualHost *:80
4 ServerName reviewboard.al.com.au
5 ServerAlias reviewboard
6
7 ServerAdmin @@
8 DocumentRoot /var/www/reviewboard
9
10 HostNameLookups Off
11 UseCanonicalName On
12 ServerSignature On
13
14 # Alias static media requests to filesystem
15 Alias /media /var/www/reviewboard/rnd/htdocs/media
16 Alias /errordocs /var/www/reviewboard/rnd/htdocs/
errordocs
17
18 WSGIScriptAlias / /var/www/reviewboard.wsgi
19
20 Location /api
21 AuthType Basic
22 AuthName AL ReviewBoard Repositories
23 AuthBasicProvider ldap
24 AuthzLDAPAuthoritative off
25 AuthLDAPBindDN **
26 AuthLDAPBindPassword *
27 AuthLDAPUrl ldap://ldap.al.com.au:389/ou=Active
Accounts,dc=al,dc=com,dc=au?sAMAccountName?sub?(objectClass=*)
28 Require valid-user
29 /Location
30
31 Directory /var/www/reviewboard/rnd/htdocs
32 AllowOverride All
33 /Directory
34
35 /VirtualHost
Here are the logs I'm getting (NOTE it is passing the GETting
http://reviewboard.al.com.au/api/info/)
HTTP GETting api/
== HTTP Authentication Required
Enter authorization information for AL ReviewBoard Repositories at
reviewboard.al.com.au
Username: federicon
Password:
HTTP GETting http://reviewboard.al.com.au/api/info/
Using the new web API
Attempting to create review request on None for None
HTTP POSTing to http://reviewboard.al.com.au/api/review-requests/:
{'repository': None}
Got API Error 103 (HTTP code 401): You are not logged in
Error data: {'stat': 'fail', 'err': {'msg': 'You are not logged in',
'code': 103}}
Attempting to create review request on None for None
HTTP POSTing to http://reviewboard.al.com.au/api/review-requests/:
{'repository': None}
Got HTTP error: 401: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title401 Authorization Required/title
/headbody
h1Authorization Required/h1
pThis server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required./p
hr
addressApache/2.2.3 (CentOS) Server at reviewboard.al.com.au Port
80/address
/body/html
Error creating review request: HTTP 401
Looks like Django/RB is not picking the user:passw ??
If I try a GET to this page, it is successful
curl -u federicon http://reviewboard.al.com.au/api/review-requests/
Enter host password for user 'federicon':
{total_results: 0, stat: ok, review_requests: [], links:
{self: {href: http://reviewboard.al.com.au/api/review-requests/;,
method: GET}, create: {href: http://reviewboard.al.com.au/api/
review-requests/, method: POST}}}
If I try a POST I get he Your are not Logged in error
curl --data sdf -u federicon http://reviewboard.al.com.au/api/review-requests/
Enter host password for user 'federicon':
{stat: fail, err: {msg: You are not logged in, code: 103}}
we run out of ideas in what to try
On Mar 31, 11:16 am, Christian Hammond chip...@chipx86.com wrote:
Hi Fede,
The reason it's broken now is that we've moved to using Basic HTTP auth for
the API. This is a standard protocol, and things have supported it forever,
but wsgi (and fastcgi) by default actually specifically filter out any
Authorization headers related to it. That's what that directive is meant to
prevent. The web UI itself doesn't use Basic HTTP auth, which is why you're
not seeing the problem there.
I don't know why it's not working for you. If that's the Apache file that
your main Apache config is directly including, or those contents are in the
main Apache config directly, then it should be solving the problem. The only
other thing at this point that I can think of is if the web server actually
wasn't restarted.
Can you provide the full debug log (pass --debug) on post-review, with a
login attempt?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Wed, Mar 30, 2011 at 5:08 PM, fede fede.n...@gmail.com wrote:
Hi Christian, Thanks for your pormpt response,
We are using LDAP, and it is working fine from the WEB UI (as before)
Yes i'm including it directly, the apache-wsgi.conf, it looks like
this
1 VirtualHost *:80
2 ServerName reviewboard.al.com.au
3 DocumentRoot /var/www/reviewboard/rnd/htdocs
4
5 # Error handlers
6
Re: post-reivew WEB API?
Hi,
You actually shouldn't have any ldap or auth configuration in your
Apache config. The wsgi directive you were using, though, is
absolutely required.
The reason is that we need Django and Review Board to handle all auth attempts.
Can you go back to the prior configuration and rerun post-review --debug?
Christian
On Wednesday, March 30, 2011, fede fede.n...@gmail.com wrote:
Hi Christian,
I'm restarting the web server every time I do any change, and checking
the httpd/error.logs to make sure it is restarted
We added ldap to the apache conf., we are close but not there yet
Here is the configuration, maybe you can spot something wrong
3 VirtualHost *:80
4 ServerName reviewboard.al.com.au
5 ServerAlias reviewboard
6
7 ServerAdmin @@
8 DocumentRoot /var/www/reviewboard
9
10 HostNameLookups Off
11 UseCanonicalName On
12 ServerSignature On
13
14 # Alias static media requests to filesystem
15 Alias /media /var/www/reviewboard/rnd/htdocs/media
16 Alias /errordocs /var/www/reviewboard/rnd/htdocs/
errordocs
17
18 WSGIScriptAlias / /var/www/reviewboard.wsgi
19
20 Location /api
21 AuthType Basic
22 AuthName AL ReviewBoard Repositories
23 AuthBasicProvider ldap
24 AuthzLDAPAuthoritative off
25 AuthLDAPBindDN **
26 AuthLDAPBindPassword *
27 AuthLDAPUrl ldap://ldap.al.com.au:389/ou=Active
Accounts,dc=al,dc=com,dc=au?sAMAccountName?sub?(objectClass=*)
28 Require valid-user
29 /Location
30
31 Directory /var/www/reviewboard/rnd/htdocs
32 AllowOverride All
33 /Directory
34
35 /VirtualHost
Here are the logs I'm getting (NOTE it is passing the GETting
http://reviewboard.al.com.au/api/info/)
HTTP GETting api/
== HTTP Authentication Required
Enter authorization information for AL ReviewBoard Repositories at
reviewboard.al.com.au
Username: federicon
Password:
HTTP GETting http://reviewboard.al.com.au/api/info/
Using the new web API
Attempting to create review request on None for None
HTTP POSTing to http://reviewboard.al.com.au/api/review-requests/:
{'repository': None}
Got API Error 103 (HTTP code 401): You are not logged in
Error data: {'stat': 'fail', 'err': {'msg': 'You are not logged in',
'code': 103}}
Attempting to create review request on None for None
HTTP POSTing to http://reviewboard.al.com.au/api/review-requests/:
{'repository': None}
Got HTTP error: 401: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title401 Authorization Required/title
/headbody
h1Authorization Required/h1
pThis server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required./p
hr
addressApache/2.2.3 (CentOS) Server at reviewboard.al.com.au Port
80/address
/body/html
Error creating review request: HTTP 401
Looks like Django/RB is not picking the user:passw ??
If I try a GET to this page, it is successful
curl -u federicon http://reviewboard.al.com.au/api/review-requests/
Enter host password for user 'federicon':
{total_results: 0, stat: ok, review_requests: [], links:
{self: {href: http://reviewboard.al.com.au/api/review-requests/;,
method: GET}, create: {href: http://reviewboard.al.com.au/api/
review-requests/, method: POST}}}
If I try a POST I get he Your are not Logged in error
curl --data sdf -u federicon http://reviewboard.al.com.au/api/review-requests/
Enter host password for user 'federicon':
{stat: fail, err: {msg: You are not logged in, code: 103}}
we run out of ideas in what to try
On Mar 31, 11:16 am, Christian Hammond chip...@chipx86.com wrote:
Hi Fede,
The reason it's broken now is that we've moved to using Basic HTTP auth for
the API. This is a standard protocol, and things have supported it forever,
but wsgi (and fastcgi) by default actually specifically filter out any
Authorization headers related to it. That's what that directive is meant to
prevent. The web UI itself doesn't use Basic HTTP auth, which is why you're
not seeing the problem there.
I don't know why it's not working for you. If that's the Apache file that
your main Apache config is directly including, or those contents are in the
main Apache config directly, then it should be solving the problem. The only
other thing at this point that I can think of is if the web server actually
wasn't restarted.
Can you provide the full debug log (pass --debug) on post-review, with a
login attempt?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc.
Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
Hi,
They're both in /usr/local/bin, which is certainly in your user's
path, but is it in Apache's?
You may want to see what happens if you move those to /usr/bin.
Alternatively, you can SetEnv PATH in your web server's config.
Christian
On Wednesday, March 30, 2011, Vincent Yee v...@sendmail.com wrote:
We do have p4 and patch on the client system:
$ which p4
/usr/local/bin/p4
$ /usr/local/bin/p4 -V
Perforce - The Fast Software Configuration Management System.
Copyright 1995-2011 Perforce Software. All rights reserved.
Rev. P4/LINUX26X86/2010.2/279478 (2011/01/03).
[build@vmtemp01 ~]$ ls -al /usr/local/bin/p4
-rwxr-xr-x 1 root root 777172 Mar 22 14:02 /usr/local/bin/p4
$ which patch
/usr/bin/patch
$ /usr/bin/patch -v
patch 2.5.4
Copyright 1984-1988 Larry Wall
Copyright 1989-1999 Free Software Foundation, Inc.
$ ls -al /usr/bin/patch
-rwxr-xr-x 1 root wheel 91476 Aug 11 2008 /usr/bin/patch
From: chip...@gmail.com
[mailto:chip...@gmail.com] On Behalf Of Christian Hammond
Sent: Wednesday, March 30, 2011 5:19 PM
To: Vincent Yee
Cc: reviewboard@googlegroups.com
Subject: Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200):
One or more fields had errors
Okay, the No such file or
directory indicates a configuration problem, but is a step in the right
direction. Some program you need is missing, and Review Board's initial checks
didn't catch it. Can you make sure that both p4 and patch are both available
on
that system and accessible/executable?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 4:59 PM, Vincent Yee v...@sendmail.com wrote:
I tried
with both in Mirror path:
perforce.example:1666
è
Error data: {u'fields': {u'path': [u'[Errno 2] No such file or
directory']}, u'stat': u'fail', u'err': {u'msg': u'One or more fields had
errors', u'code': 105}, u'deprecated': {u'in_version': u'1.5'}}
:1666 è
Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to
server failed; check $P4PORT.\nTCP connect to :1666 failed.\nconnect: :1666:
Connection refused\n']}, u'stat': u'fail', u'err': {u'msg': u'One or more
fields had errors', u'code': 105}, u'deprecated': {u'in_version': u'1.5'}}
From: chip...@gmail.com [mailto:chip...@gmail.com] On
Behalf Of Christian Hammond
Sent: Wednesday, March 30, 2011 4:42 PM
To: Vincent Yee
Cc: reviewboard@googlegroups.com
Subject: Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200):
One or more fields had errors
The
error message says you're just using :1666.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On
Wed, Mar 30, 2011 at 4:38 PM, Vincent Yee v...@sendmail.com wrote:
Ok now
it’s a different error with
Mirror
path: perforce.example.com:1666
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/20/draft/set/:
{'summary': 'p4-testing-change'}
Uploading diff, size: 361
--
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
--
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: post-reivew WEB API?
Hi Christian,
You were right all along .
I deleted the ldap bit and make sure that we have
WSGIPassAuthorization On on the apache conf file we are using and
now everything is working
Previously I got confused because we had 2 apache conf
files , and I thought we were using the one from the RB installation,
but l was wrong. just with your first answer I should have had this
working
Thanks millions for you help. I really appreciate it
Fede
On Mar 31, 3:48 pm, Christian Hammond chip...@chipx86.com wrote:
Hi,
You actually shouldn't have any ldap or auth configuration in your
Apache config. The wsgi directive you were using, though, is
absolutely required.
The reason is that we need Django and Review Board to handle all auth
attempts.
Can you go back to the prior configuration and rerun post-review --debug?
Christian
On Wednesday, March 30, 2011, fede fede.n...@gmail.com wrote:
Hi Christian,
I'm restarting thewebserver every time I do any change, and checking
the httpd/error.logs to make sure it is restarted
We added ldap to the apache conf., we are close but not there yet
Here is the configuration, maybe you can spot something wrong
3 VirtualHost *:80
4 ServerName reviewboard.al.com.au
5 ServerAlias reviewboard
6
7 ServerAdmin @@
8 DocumentRoot /var/www/reviewboard
9
10 HostNameLookups Off
11 UseCanonicalName On
12 ServerSignature On
13
14 # Alias static media requests to filesystem
15 Alias /media /var/www/reviewboard/rnd/htdocs/media
16 Alias /errordocs /var/www/reviewboard/rnd/htdocs/
errordocs
17
18 WSGIScriptAlias / /var/www/reviewboard.wsgi
19
20 Location /api
21 AuthType Basic
22 AuthName AL ReviewBoard Repositories
23 AuthBasicProvider ldap
24 AuthzLDAPAuthoritative off
25 AuthLDAPBindDN **
26 AuthLDAPBindPassword *
27 AuthLDAPUrl ldap://ldap.al.com.au:389/ou=Active
Accounts,dc=al,dc=com,dc=au?sAMAccountName?sub?(objectClass=*)
28 Require valid-user
29 /Location
30
31 Directory /var/www/reviewboard/rnd/htdocs
32 AllowOverride All
33 /Directory
34
35 /VirtualHost
Here are the logs I'm getting (NOTE it is passing the GETting
http://reviewboard.al.com.au/api/info/)
HTTP GETtingapi/
== HTTP Authentication Required
Enter authorization information for AL ReviewBoard Repositories at
reviewboard.al.com.au
Username: federicon
Password:
HTTP GETtinghttp://reviewboard.al.com.au/api/info/
Using the newwebAPI
Attempting to create review request on None for None
HTTP POSTing
tohttp://reviewboard.al.com.au/api/review-requests/:{'repository': None}
GotAPIError 103 (HTTP code 401): You are not logged in
Error data: {'stat': 'fail', 'err': {'msg': 'You are not logged in',
'code': 103}}
Attempting to create review request on None for None
HTTP POSTing
tohttp://reviewboard.al.com.au/api/review-requests/:{'repository': None}
Got HTTP error: 401: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title401 Authorization Required/title
/headbody
h1Authorization Required/h1
pThis server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required./p
hr
addressApache/2.2.3 (CentOS) Server at reviewboard.al.com.au Port
80/address
/body/html
Error creating review request: HTTP 401
Looks like Django/RB is not picking the user:passw ??
If I try a GET to this page, it is successful
curl -u federiconhttp://reviewboard.al.com.au/api/review-requests/
Enter host password for user 'federicon':
{total_results: 0, stat: ok, review_requests: [], links:
{self: {href: http://reviewboard.al.com.au/api/review-requests/;,
method: GET}, create: {href: http://reviewboard.al.com.au/api/
review-requests/, method: POST}}}
If I try a POST I get he Your are not Logged in error
curl --data sdf -u
federiconhttp://reviewboard.al.com.au/api/review-requests/
Enter host password for user 'federicon':
{stat: fail, err: {msg: You are not logged in, code: 103}}
we run out of ideas in what to try
On Mar 31, 11:16 am, Christian Hammond chip...@chipx86.com wrote:
Hi Fede,
The reason it's broken now is that we've moved to using Basic HTTP auth for
theAPI. This is a standard protocol, and things have supported it forever,
but wsgi (and fastcgi) by default actually specifically filter out any
Authorization headers related to it. That's what that directive is meant to
prevent. ThewebUI
Re: post-reivew WEB API?
Not a problem. Glad it works :)
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Mar 30, 2011 at 10:42 PM, fede fede.n...@gmail.com wrote:
Hi Christian,
You were right all along .
I deleted the ldap bit and make sure that we have
WSGIPassAuthorization On on the apache conf file we are using and
now everything is working
Previously I got confused because we had 2 apache conf
files , and I thought we were using the one from the RB installation,
but l was wrong. just with your first answer I should have had this
working
Thanks millions for you help. I really appreciate it
Fede
On Mar 31, 3:48 pm, Christian Hammond chip...@chipx86.com wrote:
Hi,
You actually shouldn't have any ldap or auth configuration in your
Apache config. The wsgi directive you were using, though, is
absolutely required.
The reason is that we need Django and Review Board to handle all auth
attempts.
Can you go back to the prior configuration and rerun post-review --debug?
Christian
On Wednesday, March 30, 2011, fede fede.n...@gmail.com wrote:
Hi Christian,
I'm restarting thewebserver every time I do any change, and checking
the httpd/error.logs to make sure it is restarted
We added ldap to the apache conf., we are close but not there yet
Here is the configuration, maybe you can spot something wrong
3 VirtualHost *:80
4 ServerName reviewboard.al.com.au
5 ServerAlias reviewboard
6
7 ServerAdmin @@
8 DocumentRoot /var/www/reviewboard
9
10 HostNameLookups Off
11 UseCanonicalName On
12 ServerSignature On
13
14 # Alias static media requests to filesystem
15 Alias /media /var/www/reviewboard/rnd/htdocs/media
16 Alias /errordocs /var/www/reviewboard/rnd/htdocs/
errordocs
17
18 WSGIScriptAlias / /var/www/reviewboard.wsgi
19
20 Location /api
21 AuthType Basic
22 AuthName AL ReviewBoard Repositories
23 AuthBasicProvider ldap
24 AuthzLDAPAuthoritative off
25 AuthLDAPBindDN **
26 AuthLDAPBindPassword *
27 AuthLDAPUrl ldap://ldap.al.com.au:389/ou=Active
Accounts,dc=al,dc=com,dc=au?sAMAccountName?sub?(objectClass=*)
28 Require valid-user
29 /Location
30
31 Directory /var/www/reviewboard/rnd/htdocs
32 AllowOverride All
33 /Directory
34
35 /VirtualHost
Here are the logs I'm getting (NOTE it is passing the GETting
http://reviewboard.al.com.au/api/info/)
HTTP GETtingapi/
== HTTP Authentication Required
Enter authorization information for AL ReviewBoard Repositories at
reviewboard.al.com.au
Username: federicon
Password:
HTTP GETtinghttp://reviewboard.al.com.au/api/info/
Using the newwebAPI
Attempting to create review request on None for None
HTTP POSTing tohttp://
reviewboard.al.com.au/api/review-requests/:{'repositoryhttp://reviewboard.al.com.au/api/review-requests/:%7B%27repository':
None}
GotAPIError 103 (HTTP code 401): You are not logged in
Error data: {'stat': 'fail', 'err': {'msg': 'You are not logged in',
'code': 103}}
Attempting to create review request on None for None
HTTP POSTing tohttp://
reviewboard.al.com.au/api/review-requests/:{'repositoryhttp://reviewboard.al.com.au/api/review-requests/:%7B%27repository':
None}
Got HTTP error: 401: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML
2.0//EN
htmlhead
title401 Authorization Required/title
/headbody
h1Authorization Required/h1
pThis server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required./p
hr
addressApache/2.2.3 (CentOS) Server at reviewboard.al.com.au Port
80/address
/body/html
Error creating review request: HTTP 401
Looks like Django/RB is not picking the user:passw ??
If I try a GET to this page, it is successful
curl -u federiconhttp://reviewboard.al.com.au/api/review-requests/
Enter host password for user 'federicon':
{total_results: 0, stat: ok, review_requests: [], links:
{self: {href: http://reviewboard.al.com.au/api/review-requests/;,
method: GET}, create: {href:
http://reviewboard.al.com.au/api/
review-requests/, method: POST}}}
If I try a POST I get he Your are not Logged in error
curl --data sdf -u federiconhttp://
reviewboard.al.com.au/api/review-requests/
Enter host password for user 'federicon':
{stat: fail, err: {msg: You are not logged
Issue 2054 in reviewboard: RBTools-0.3.2 + Perforce - failed to upload diff when source file is a new file
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2054 by fogyw...@gmail.com: RBTools-0.3.2 + Perforce - failed to
upload diff when source file is a new file
http://code.google.com/p/reviewboard/issues/detail?id=2054
Version: RevewBoard 1.5.2 + RBTools-0.3.2-py2.6
Client OS: Windows XP SP3
p4v-version: Perforce Visual Client/NTX86/2009.1/205670
Review-Type: Pre-submit review
Procedure:
1. add a new file to p4 workspace
2. create a new changelist
3. post-review change-num
4. error as below:
---
RBTools 0.3.2
Home = C:\Documents and Settings\fogy_wang\Application Data
svn info
git rev-parse --git-dir
p4 info
repository info: Path: perforce.my-rb-host.org:1666, Base path: None,
Supports changesets: True
HTTP GETting api/
HTTP GETting http://review.my-rb-host.org/api/info/
Using the new web API
Generating diff for changenum 748607
p4 describe -s 748607
Processing add of //Core/TRS/DEV/ID_Reputation/src/ARQ/common/test.cxx
diff -urNp c:\docume~1\fogy_w~1\locals~1\temp\tmp_l6zi6
C:\p4\default.fogy_wang.ID_Reputation-Lead\Core\TRS\DEV\ID_Reputation\src\ARQ\common\test.cxx
Using changenums on Review Board 1.5.2. Falling back to the deprecated
1.0 API
== Review Board Login Required
Enter username and password for Review Board at
http://review.my-rb-host.org/
Logging in with username fogy_wang
HTTP POSTing to http://review.my-rb-host.org/api/json/accounts/login/:
{'username': 'fogy_wang', 'password': '**'}
Logged in.
Attempting to create review request on perforce.my-rb-host.org:1666 for
748607
HTTP POSTing to
http://review.my-rb-host.org/api/json/reviewrequests/new/:
{'changenum': '748607', 'repository_path': 'perforce.my-rb-host.org:1666'}
Review request created
Uploading diff, size: 313
HTTP POSTing to
http://review.my-rb-host.org/api/json/reviewrequests/449/diff/new/: {}
Got API Error 105 (HTTP code 200): One or more fields had errors
Error data: {u'fields': {u'path': [u'[P4#run] Warnings during command
execution( p4 files
//Core/TRS/DEV/ID_Reputation/src/ARQ/common/test.cxx#1
)\n\n\t[Warning]:
//Core/TRS/DEV/ID_Reputation/src/ARQ/common/test.cxx#1 - no such
file(s).\n\n']}, u'stat': u'fail', u'err': {u'msg': u'One or more
fields had errors', u'code': 105}, u'deprecated': {u'in_version':
u'1.5'}}
Your review request still exists, but the diff is not attached.
Error uploading diff
The generated diff file was empty. This usually means no files were
modified in this change.
Try running with --output-diff and --debug for more information.
---
Additional Description:
This error ONLY appears when the uploaded file is a NEW file (i.e. p4
server has no previous revisions); if the uploaded file already exists on
perforce server (i.e. at least one previous revision exists), the review
could be successfully posted.
I can understand the warning by 'p4 file [file-repository-path]' because
there isn't a file on p4 server but shouldn't RB uses the uploaded diff
(i.e. size 313) instead when the file is 'new'?
I used to use 'RBTools-0.2rc2.dev_20100308-py2.6.bak' with 'Review Board
1.0.5.1' the issue didn't exist.
--
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 1917 in reviewboard: post-review doesn't play nice with msysgit on Windows
Comment #1 on issue 1917 by joshua.m...@gmail.com: post-review doesn't play nice with msysgit on Windows http://code.google.com/p/reviewboard/issues/detail?id=1917 Ping, any progress on 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.
Re: Issue 1917 in reviewboard: post-review doesn't play nice with msysgit on Windows
Updates: Status: PendingReview Comment #2 on issue 1917 by trowb...@gmail.com: post-review doesn't play nice with msysgit on Windows http://code.google.com/p/reviewboard/issues/detail?id=1917 Please put this on http://reviews.reviewboard.org/ -- 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 1917 in reviewboard: post-review doesn't play nice with msysgit on Windows
Comment #3 on issue 1917 by joshua.m...@gmail.com: post-review doesn't play nice with msysgit on Windows http://code.google.com/p/reviewboard/issues/detail?id=1917 OK, http://reviews.reviewboard.org/r/2226/ -- 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 1917 in reviewboard: post-review doesn't play nice with msysgit on Windows
Updates: Status: Fixed Comment #4 on issue 1917 by trowb...@gmail.com: post-review doesn't play nice with msysgit on Windows http://code.google.com/p/reviewboard/issues/detail?id=1917 Fixed in master as d0138a7. -- 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.
