Re: Clean rb-site install of alpha1 fails on htdocs/media/.htaccess
The nightly egg worked as well. Thanks for the quick turn-around.
On Jan 27, 4:19 pm, Christian Hammond chip...@chipx86.com wrote:
The problem's a bit odd, but I think I have it fixed in SVN if you want to
grab that and do:
sudo python setup.py nightly install
(the nightly is important)
Christian
--
Christian Hammond - chip...@chipx86.com
VMware, Inc.
On Tue, Jan 27, 2009 at 12:46 PM, Jamie Whitehouse
basil.whiteho...@gmail.com wrote:
I'm following the Getting Started guide on a Ubuntu 8.10 server, and
when I run: sudo rb-site install /var/www/review I get the following
error. This is with the 1.0 alpha that easy_install retrieves.
I've read some success stories in this group, but nothing that hints
to what may fix this problem. Any ideas?
Thanks,
Jamie.
* Installing the site...
Building site directories ... Traceback (most recent call last):
File /usr/bin/rb-site, line 5, in module
pkg_resources.run_script('ReviewBoard==1.0alpha2.dev-20090127',
'rb-site')
File /usr/lib/python2.5/site-packages/pkg_resources.py, line 448,
in run_script
self.require(requires)[0].run_script(script_name, ns)
File /usr/lib/python2.5/site-packages/pkg_resources.py, line 1166,
in run_script
execfile(script_filename, namespace, namespace)
File /usr/lib/python2.5/site-packages/
ReviewBoard-1.0alpha2.dev_20090127-py2.5.egg/EGG-INFO/scripts/rb-
site, line 1258, in module
main(sys.argv[1:])
File /usr/lib/python2.5/site-packages/
ReviewBoard-1.0alpha2.dev_20090127-py2.5.egg/EGG-INFO/scripts/rb-
site, line 1253, in main
command.run()
File /usr/lib/python2.5/site-packages/
ReviewBoard-1.0alpha2.dev_20090127-py2.5.egg/EGG-INFO/scripts/rb-
site, line 890, in run
self.show_install_status()
File /usr/lib/python2.5/site-packages/
ReviewBoard-1.0alpha2.dev_20090127-py2.5.egg/EGG-INFO/scripts/rb-
site, line 1108, in show_install_status
site.rebuild_site_directory)
File /usr/lib/python2.5/site-packages/
ReviewBoard-1.0alpha2.dev_20090127-py2.5.egg/EGG-INFO/scripts/rb-
site, line 497, in step
func()
File /usr/lib/python2.5/site-packages/
ReviewBoard-1.0alpha2.dev_20090127-py2.5.egg/EGG-INFO/scripts/rb-
site, line 123, in rebuild_site_directory
fp = open(os.path.join(media_base, .htaccess), w)
IOError: [Errno 2] No such file or directory: 'htdocs/media/.htaccess'
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
reviewboard group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---
Upgrade Of SVN Checkout
Hi, I upgraded my revieboard svn version to 1715 today. Now many users are not able to make any comments or add reviewers . Even For me unless I use google chrome browser , i'm not able to make any comments or add reviewers. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
newbie installation issues
I am trying to install reviewboard on an Ubuntu 8.10 VMWare virtual machine to try it without much luck. The following is the sequence of steps that I've followed so far (after looking through various posts on this discussion board): 1. I used rb-site install /var/www/reviewboard with the following options: domain-name: localhostsite-root: /media-url: media/ db-type: sqlite3cache-type: fileweb-server-type: lighttpd 2. Then I copied over the /etc/lighttpd/lighttpd.conf with the file in /var/www/conf/lighttpd.conf. 3. Added FORCE_SCRIPT_NAME='/' to settings_local.py 4. Ran sudo /etc/init.d/lighttpd force-reload 5. Ran rb-site manage /var/www/reviewboard runfcgi method=threaded host=127.0.0.1 port=3033 protocol=fcgi Visiting http://localhost/reviews/; redirects me to http://localhost/ reviewboard.fcgi/reviews/ which produces a Page not found (404) with the following: Page not found (404) Request Method: GET Request URL:http://localhost/reviewboard.fcgi/reviews/ Using the URLconf defined in djblets.util.rooturl, Django tried these URL patterns, in this order: 1. ^reviews/ The current URL, reviewboard.fcgi/reviews/, didn't match any of these. You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. Any help in getting this up and going is appreciated. Thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Newbie question: setup problems
Nice! I've edited C:\Python25\Lib\site-packages\reviewboard-1.0alpha2.dev-py2.5.egg \reviewboard\contrib\tools\rb-site and in the line just before. self.run_manage_command(syncdb, [--noinput]) I've put import pdb;pdb.set_trace() run the instalation command and when the install process stopped, I've edited settings_local.py and put double slashs int the database_name parameter: DATABASE_NAME = 'd:\\codereview\\db\\reviewboard.db' pressed 'c' in the hanged install prompt and it finished with success. thanks! On Jan 27, 8:29 pm, Christian Hammond chip...@chipx86.com wrote: There's a bug right now with Windows that I'm going to fix tonight. Make sure that in your conf/settings_local.py your path to the database looks like: D:\\mypath\\db\\reviewboard.db. The \ needs to be escaped. Christian -- Christian Hammond - chip...@chipx86.com VMware, Inc. On Tue, Jan 27, 2009 at 2:25 PM, Paulo Eduardo Neves paulone...@gmail.comwrote: I had the same error trying to install reviewboard in windows as administrator. The dir D:\mypath\db\ is empty. I'm also using sqlite, file as cache, and apache. On Jan 8, 3:04 pm, Phil lod...@comcast.net wrote: * Installing the site... Building site directories ... OK Building site configuration files ... OK Creatingdatabase... Traceback (most recent call last): FileC:\Python25\Lib\site-packages\ReviewBoard-0.9.dev_20090108- py2.5.egg\EGG-INFO\scripts\rb-site, line 1186, in module main(sys.argv[1:]) FileC:\Python25\Lib\site-packages\ReviewBoard-0.9.dev_20090108- py2.5.egg\EGG-INFO\scripts\rb-site, line 1181, in main command.run() FileC:\Python25\Lib\site-packages\ReviewBoard-0.9.dev_20090108- py2.5.egg\EGG-INFO\scripts\rb-site, line 822, in run self.show_install_status() FileC:\Python25\Lib\site-packages\ReviewBoard-0.9.dev_20090108- py2.5.egg\EGG-INFO\scripts\rb-site, line 1043, in show_install_status site.sync_database) FileC:\Python25\Lib\site-packages\ReviewBoard-0.9.dev_20090108- py2.5.egg\EGG-INFO\scripts\rb-site, line 469, in step func() FileC:\Python25\Lib\site-packages\ReviewBoard-0.9.dev_20090108- py2.5.egg\EGG-INFO\scripts\rb-site, line 181, in sync_database self.run_manage_command(syncdb, [--noinput]) FileC:\Python25\Lib\site-packages\ReviewBoard-0.9.dev_20090108- py2.5.egg\EGG-INFO\scripts\rb-site, line 219, in run_manage_command execute_manager(reviewboard.settings, [__file__, cmd] + params) Filec:\python25\lib\site-packages\django-1.0.2_final-py2.5.egg \django\core\management\__init__.py, line 340, in execute_manager utility.execute() Filec:\python25\lib\site-packages\django-1.0.2_final-py2.5.egg \django\core\management\__init__.py, line 295, in execute self.fetch_command(subcommand).run_from_argv(self.argv) Filec:\python25\lib\site-packages\django-1.0.2_final-py2.5.egg \django\core\management\base.py, line 192, in run_from_argv self.execute(*args, **options.__dict__) Filec:\python25\lib\site-packages\django-1.0.2_final-py2.5.egg \django\core\management\base.py, line 219, in execute output = self.handle(*args, **options) Filec:\python25\lib\site-packages\django-1.0.2_final-py2.5.egg \django\core\management\base.py, line 348, in handle return self.handle_noargs(**options) Filec:\python25\lib\site-packages\django-1.0.2_final-py2.5.egg \django\core\management\commands\syncdb.py, line 51, in handle_noargs cursor = connection.cursor() Filec:\python25\lib\site-packages\django-1.0.2_final-py2.5.egg \django\db\backends\__init__.py, line 56, in cursor cursor = self._cursor(settings) Filec:\python25\lib\site-packages\django-1.0.2_final-py2.5.egg \django\db\backends\sqlite3\base.py, line 145, in _cursor self.connection =Database.connect(**kwargs)sqlite3.OperationalError:unabletoopendatabasefile 11:53:16 C:\Python25\Lib\site-packages\ReviewBoard-0.9.dev_20090108- py2.5.egg\EGG-INFO\scripts --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Upgrade Of SVN Checkout
Make sure they've cleared their browser cache and you've cleared the server cache. A lot has changed. I strongly recommend moving to rb-site if you're running literally out of SVN (in other words, if Apache is configured to point to the SVN dir), as we're going to have to break that with a directory cleanup pretty soon. Christian -- Christian Hammond - chip...@chipx86.com VMware, Inc. On Wed, Jan 28, 2009 at 6:23 AM, roshanpius roshanpiustho...@gmail.comwrote: Hi, I upgraded my revieboard svn version to 1715 today. Now many users are not able to make any comments or add reviewers . Even For me unless I use google chrome browser , i'm not able to make any comments or add reviewers. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
perforce and post-review
How do you use post-review with the new installation? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
LDAP authentication questions
Hello! The current LDAP authentication scheme used in Review Board (acconts/backends.py|LDAPBackend.authenticate()) assumes that a chosen LDAP server allows anonymous search. This is not always true (e.g. our internal corp. directory server :) ) , so perhaps prior binding is necessary. Of course this binding may be performed by a designated unprivileged user and existing LDAP_ANON_BIND_UID perfectly suits the task. Certainly the change is rather trivial but since I'm almost unfamiliar with LDAP-related things I'd like to hear first that there're no other considerations not to add the binding. Respectfully, Alexey Morozov --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
GIT support in ReviewBoard
Hello! I'd like to hear, understand and perhaps discuss how GIT support is implemented in ReviewBoard. Right now I'm looking at contrib/tools/post-review|GitClient and frankly speaking not completely understand the _goals_ of the code. Perhaps I'm wrong but it seems that most of the code is written with the idea of a single centralized repository and all methods more suitable for CVS or SVN. For example when one have a traditional centralized SCM the only way to implement a pre-commit review is to make a diff against a revision which is already checked in and then send this diff for a review. From other hand if you have a distributed SCM, it's much more convenient to make a local commit (or even a series of commits!) and then send this commit (or commits) for review (or multiple reviews). Thus we can support things like ``git add -i'', automatic review title/summary generation etc. On the server side it becomes possible to correctly handle renames or copyings, binary diffs, handle cherry-picks and merges etc. However I'm just started to work with ReviewBoard (although I have some experience with SmartBear's CodeCollaborator) and perhaps I didn't notice significant issues or maybe current code processing model simply doesn't allow easy incorporation of these changes. Best regards, Alexey Morozov --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: LDAP authentication questions
Hello again! On Thursday 29 January 2009 05:03:05 Alexey Morozov wrote: Certainly the change is rather trivial but since I'm almost unfamiliar with LDAP-related things I'd like to hear first that there're no other considerations not to add the binding. Also in http://www.mechanicalcat.net/tech/roundup/wiki/LDAPLogin I noticed that they use ldap.SCOPE_SUBTREE instead of ldap.SCOPE_ONELEVEL when performing search-before-bind. This [potentially] could allow a more flexible LDAP trees (and I've found already this is useful on some LDAP configurations) but since I don't completely understand all consequences, I'd like to ask if it's worth doing. Yours respectfully, Alexey Morozov --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
