Re: New installation/upgrade procedures

Yes, it can be used (we used it with SVN as well). Basically it depends if you want to use pre-commit reviews (code is reviewed and has to be approved before you commit it in SVN - that's how we use it). In this case you just make some changes to your working copy of repository, make diff using SV

Re: New installation/upgrade procedures

Hi lindal, I suppose it depends on your configuration (if you use apache (or similar) or built in webserver). Check the documentation (http://code.google.com/p/reviewboard/wiki/Documentation) for configuring ReviewBoard. Tom On 28 Lis, 19:57, lindal <[EMAIL PROTECTED]> wrote: > $ sudo rb-site in

Re: New installation/upgrade procedures

Hi Russell, this bug was present since the migration to easy_install. Removing the settings_local from site-packeges helped but not with upgrade from 27/11. Because if I removed from that one rb-site complained that the file is missing (even if there still was my settings_local in {site}/conf dir,

Re: New installation/upgrade procedures

We use SVN to store our code repositories. Can review-board be used by us and if yes, what are the steps involved when somebody changes a file. I could not find anything, pointer to such thing will also help but it should have the answer to above question. Thanks, Kunal On Nov 28, 11:57 am, lin

Re: New installation/upgrade procedures

$ sudo rb-site install /path/to/sitedir $ sudo rb-site install /var/www/reviews.example.com after above step, I don't konw how start the appliction and how to access ReviewBoard web site. please help me, thanks! --~--~-~--~~~---~--~~ You received this message becau

Re: New installation/upgrade procedures

On Thu, Nov 27, 2008 at 2:21 PM, Tomas Friml <[EMAIL PROTECTED]>wrote: > > Hi Chris, > > after last update (0.9.dev_20081127) there seems to be another > (packaging?) bug. If delete setting_local.py* ReviewBoard stops > working. I can see in logs that it's actually requiring the file I > deleted :

Re: New installation/upgrade procedures

Hi Chris, after last update (0.9.dev_20081127) there seems to be another (packaging?) bug. If delete setting_local.py* ReviewBoard stops working. I can see in logs that it's actually requiring the file I deleted :) Logs: [Fri Nov 28 09:11:50 2008] [error] [client 10.64.1.113] PythonHandler djang

Re: New installation/upgrade procedures

First, there's a bug in packaging so you'll need to delete the settings_local.* files in your installed ReviewBoard directory. I'll fix this when I get back from vacation. Second, on Windows you'll have to pass --copy-media to rb-site for now until we add Windows detection (also when I get back).

Re: New installation/upgrade procedures

I had problems using sudo, so I used some other tool to get the admin rights. After that I performed "easy_install ReviewBoard". It worked fine and rb-site is generated in Python25\Scripts directory Next step I do is "rb-site install /siteDir" which gives some error, so I had to explicitly call it

Re: New installation/upgrade procedures

Okay, but I'm still not sure when you say it's for testing whether you mean with fastcgi or something different. Review Board is not a server, so it does require an existing web server. We can't really provide anything custom there, nor would we want to maintain a web server for this project. Chri

Re: New installation/upgrade procedures

On Mon, Nov 24, 2008 at 22:58, Christian Hammond <[EMAIL PROTECTED]> wrote: > Yeah, it looks like easy_install leaves the old directory behind. I don't > know why. I think it's an issue on their end. Normal way, setuptools doesn't remove anything. -- Sebastien Douche <[EMAIL PROTECTED]> --~--

Re: New installation/upgrade procedures

On Mon, Nov 24, 2008 at 02:03, Christian Hammond <[EMAIL PROTECTED]> wrote: >> - where is start/stop script? > > There is none. It's assumed your web server will have its own start/stop > script. > > If you're using fastcgi, we probably should provide one, though I want to > point out that we've h

Re: New installation/upgrade procedures

Strange.. I'll look into this and should have a fix by tonight, hopefully. I'm leaving town for the holidays tonight so I won't be as active on here but will be checking on e-mail and fixing critical issues like this. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Tue, Nov

Re: New installation/upgrade procedures

Hi Chris, Today I updated again and guess what - the setting_local files are there again :) On 25 Lis, 12:57, Tomas Friml <[EMAIL PROTECTED]> wrote: > Ok, reinstalling still doesn't help (files are still created, but I > suppose that's because your nightly build hasn't been propagated yet > to e

Re: New installation/upgrade procedures

Ok, reinstalling still doesn't help (files are still created, but I suppose that's because your nightly build hasn't been propagated yet to easy_install or something like that), but if I remove the settings_local files rb-site upgrade works :). Thanks a lot, Tom On 25 Lis, 12:24, "Christian Hamm

Re: New installation/upgrade procedures

The settings_local.py in the ReviewBoard egg directory was a packaging error that has been fixed in the latest nightly. Go ahead and delete settings_local.py and .pyc from that directory and try the install again. You shouldn't hit this with future packages. What should be happening is that rb-sit

Re: New installation/upgrade procedures

Hi Chris, I would think that it works like that. But it doesn't not in my case :). The problem obviously is in settings_local.py in the ReviewBoard directory. If I set the correct db settings there everything works. But the default settings_local don't work for me. Settings_local.py in site direc

Re: New installation/upgrade procedures

One option would be a local PyPi mirror produced on a machine with internet access, there are a few of those around. I've not used any of them though, http://pypi.python.org/pypi/collective.eggproxy/ may be worth checking out. This way the dependencies can be dealt with. Chris Christian Ham

Re: New installation/upgrade procedures

Hi Chris. You sure can. Just check out the SVN tree, modify what you need, and, when you're ready to install, run: python setup.py install There's also a "python setup.py develop" command that sets up the installed tree to point to your source directory. This is fine for devel purposes, but if y

Re: New installation/upgrade procedures

Hi Tomas. Yeah, it looks like easy_install leaves the old directory behind. I don't know why. I think it's an issue on their end. You shouldn't ever deal with the settings file in that directory, though. The settings.py in there is meant to be untouched. You should only ever modify conf/settings_

Re: New installation/upgrade procedures

The best I can offer you is http://www.review-board.org/downloads/nightly/and http://www.review-board.org/downloads/mirror/. You can download the eggs from there and run easy_install on the file direcly. You may also want to pass the -N flag to have it skip dependencies, but make sure you have the

Re: New installation/upgrade procedures

One question that might be similar to what Chris Clark was asking about: what is the best way to install rb on a box that has no direct access to the Internet? The app has been in such flux that I finally stopped trying to install it after Django released 1.0, anticipating your own 1.0 release.

Re: New installation/upgrade procedures

Christian Hammond wrote: > .To sum up the new changes, basic installation has mostly become: > >$ sudo easy_install ReviewBoard >$ sudo rb-site install /var/www/reviews.example.com > > > For the most part, nothing too fundamental has changed. It's just

Re: New installation/upgrade procedures

Hi Christian, Yesterday I've migrated to "new way of..." ReviewBoard (after putting some effort :)). Today I wanted to upgrade it and all went smoothly till I wanted to upgrade site. I got same error as yesterday (missing python sqlite module which was caused by default settings of ReviewBoard).

Re: New installation/upgrade procedures

The egg cache error was as follows: > [Sun Nov 23 22:44:38 2008] [error] [client 137.65.232.150] PythonHandler > django.core.handlers.modpython: ExtractionError: Can't extract file(s) to > egg cache > > The following error occurred while trying to extract file(s) to the Python > egg > cache: > [

Re: New installation/upgrade procedures

Glad to hear it works. Interesting about the egg cache. I know that's something we'll have to deal with later, but I'm surprised it's a factor right now. What exactly was it complaining about? Also, curious about the entry. Perhaps that's due to some global config in your apache. Is that directo

Re: New installation/upgrade procedures

Thanks very much Christian. This solved my issue. I was able to get the rb-site install to recognize the existing mysql data. I did have to modify the apache conf file slightly, due to errors trying to extract files to an egg cache, when they did not have permissions to the default egg cache fol

Re: New installation/upgrade procedures

There seems to be a problem in the packaging of the ReviewBoard where settings_local.py and settings_local.pyc gets included. Try to remove /usr/lib/python2.5/site-packages/ReviewBoard*.egg/reviewboard/settings_local.py*. Then try "rb-site install" again. I'll have this fixed in tonight's nightl

Re: New installation/upgrade procedures

The only time I used new mysql settings, was the first time I tried the install. Since then, and just now, I have been using the old mysql connection instructions. Unfortunately, when I run the server using the '*rb-site manage...*' command-line, it does not use the mysql database. It appears to

Re: New installation/upgrade procedures

You can with the rb-site manage command, like so: rb-site manage /path/to/site runserver -- 0.0.0.0:8080 The manual updates appears to be due to your install having your media directory pointing to your Python site-packages directory. This would most likely be due to you having not specified your

Re: New installation/upgrade procedures

It appears that it does not recognize that an htdocs/media/uploaded folder exists. I have attached the html file for the manual server updates message. On my server I did find that there were some files installed in /usr/*local*/lib64/python2.4/site-packages/ as opposed to the normal location of

Re: New installation/upgrade procedures

If you went through rb-site install and select MySQL, you should never have had to modify settings_local.py. You could just specify the existing database information. Did you set the directory permissions correctly? Which manual server updates is it listing? manage.py is no more, though you can d

Re: New installation/upgrade procedures

I went through and ran the initial install, then changed the db settings and ran the rb-site upgrade. It reported the following: > Rebuilding directory structure > Updating database > Installing json fixture 'initial_data' from > '/usr/local/lib64/python2.4/site-packages/ReviewBoard-0.9.dev_20081

Re: New installation/upgrade procedures

Cool! adding the tcl-devel and tk-devel allowed the build to occur. Now I am trying to use the old mysql db, rather than the new one that was created. It looks as if I just need to modify the settings_local.py in the 'reviewboard/conf' folder. Maybe run 'rb-site upgrade' ??? Thanks for the prom

Re: New installation/upgrade procedures

You could try installing the tcl8.4-dev and tk8.4-dev packages (or equivalent names on your system). This will hopefully allow it to compile. As far as PIL 1.1.5, you could definitely try installing the RPM. The issue is that PIL is marked as a dependency and easy_install may attempt to upgrade it

Re: New installation/upgrade procedures

Forgot to ask . . . is there a way to bring the dependency for PIL 1.1.6 down to 1.1.5, which I can get an rpm for? Cheers, -Lyndon- On Sun, Nov 23, 2008 at 9:22 PM, Lyndon Washington < [EMAIL PROTECTED]> wrote: > Mmmm! On my system there is a dependency between python-tk and > python-devel. p

Re: New installation/upgrade procedures

Mmmm! On my system there is a dependency between python-tk and python-devel. python-devel is needed by python-setuptools. Removing python-tk will request that I remove the other two. Any other ideas? Cheers, -Lyndon- On Sun, Nov 23, 2008 at 8:01 PM, Christian Hammond <[EMAIL PROTECTED]>wrote:

Re: New installation/upgrade procedures

On Sun, Nov 23, 2008 at 4:04 AM, Sebastien Douche <[EMAIL PROTECTED]> wrote: > > On Sun, Nov 23, 2008 at 12:12, Christian Hammond <[EMAIL PROTECTED]> > wrote: > > We've just finished moving over to a new way of installing and upgrading > > Review Board. > > Yeah \o/ > > > For the most part, nothin

Re: New installation/upgrade procedures

I've noticed this as well. Best solution is to remove the python-tk package from your system. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Sun, Nov 23, 2008 at 5:00 PM, Lyndon Washington < [EMAIL PROTECTED]> wrote: > Hi, > > I tried to move from a svn based install to th

Re: New installation/upgrade procedures

Hi, I tried to move from a svn based install to the latest install and unfortunately failed when easy_install tried to install the dependency of PIL. I have [EMAIL PROTECTED] also an rpm for [EMAIL PROTECTED] The error is below. Anything obvious to any python people (of which I am not)? Cheers,

Re: New installation/upgrade procedures

On Sun, Nov 23, 2008 at 12:12, Christian Hammond <[EMAIL PROTECTED]> wrote: > We've just finished moving over to a new way of installing and upgrading > Review Board. Yeah \o/ > For the most part, nothing too fundamental has changed. It's just easier to > get going now. We are, however, consider

New installation/upgrade procedures

Hi everyone. We've just finished moving over to a new way of installing and upgrading Review Board. Review Board, Djblets, Django-Evolution, PIL and Django are now packaged up in such a way where you can install or upgrade them all with one command. Site installation and upgrading is also handle