Re: Failed to upgrade from 1.0.9 to 1.5
Hi Christian,
Thanks for the reply.
rb-site manage /var/reviewboard evolve -- --hint gives option error,
however, I tried something else.
The instance has been running for over 2 years, I don't know the exact
version I install at first but I believe it's 0.9.x. It has been
upgraded all the way to 1.0.9, nice and smooth. No in-development
release has been used ever since 1.0.
I even tried to edit diffviewer/models.py to add a default value 'M'
to FileDiff.status, so that evolve --hint --execute was a success,
but syncdb still reports errors:
Upgrading Review Board from 1.0.9 to 1.5.2
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
No fixtures found.
# pwd
/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-py2.6.egg/
reviewboard
# rb-site manager /var/reviewboard evolve -- --hint
Usage: rb-site command [options] path
Options:
--version show program's version number and exit
-h, --helpshow this help message and exit
(and more)
# rb-site manage /var/reviewboard evolve --hint
Usage: rb-site command [options] path
rb-site: error: no such option: --hint
# PYTHONPATH=/var/reviewboard/conf ./manage.py evolve --hint
#- Evolution for diffviewer
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('DiffSet', 'basedir', models.CharField, initial=u'',
max_length=256),
AddField('FileDiff', 'status', models.CharField, initial=USER
VALUE REQUIRED, max_length=1)
]
#--
#- Evolution for reviews
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('DefaultReviewer', 'repository', models.ManyToManyField,
related_model='scmtools.Repository'),
ChangeField('ReviewRequest', 'repository', initial=None,
null=True)
]
#--
#- Evolution for scmtools
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('Repository', 'visible', models.BooleanField,
initial=True),
AddField('Repository', 'raw_file_url', models.CharField,
initial='', max_length=255),
ChangeField('Repository', 'path', initial=None, max_length=255),
ChangeField('Repository', 'mirror_path', initial=None,
max_length=255)
]
#--
Trial evolution successful.
Run './manage.py evolve --hint --execute' to apply evolution.
On Jan 11, 4:59 am, Christian Hammond chip...@chipx86.com wrote:
Hi Terry,
That's strange... Can you run a test for me:
do:
rb-site manage /var/reviewboard evolve -- --hint
(Note that those are double hyphens, not single hyphens)
Show me the results. May hopefully shed some light on it.
At any point, did you try to upgrade to an in-development release
(either nightly or straight from Git)?
Also, do you remember what version of Review Board you started with?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Mon, Jan 10, 2011 at 12:29 PM, Terry Zhong think...@gmail.com wrote:
Hi all,
We have a Review Board 1.0.9 server running smoothly, but the
upgrading to 1.5 fails, with tracebacks below. We've tried 1.5, 1.5.1
and 1.5.2 with easy_install, same tracebacks. Would you please help us
out, thanks a lot.
Debian Squeeze
Python 2.6.6
MySQL 5.1.49
# rb-site upgrade /var/reviewboard/
Rebuilding directory structure
Updating database. This may take a while.
Upgrading Review Board from 1.0.9 to 1.5.2
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
Project signature has changed - an evolution is required
No fixtures found.
/usr/lib/python2.6/dist-packages/Crypto/Util/randpool.py:40:
RandomPool_DeprecationWarning: This application uses RandomPool, which
is BROKEN in older releases. Seehttp://www.pycrypto.org/randpool-broken
RandomPool_DeprecationWarning)
Traceback (most recent call last):
File /usr/local/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.5.2', 'console_scripts', 'rb-
site')()
File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1512, in run
site.migrate_database()
File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 346, in
migrate_database
self.run_manage_command(evolve, [--noinput, --execute])
File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 397, in
run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File /usr/lib/pymodules/python2.6/django/core/management/
Re: Failed to upgrade from 1.0.9 to 1.5
Hi Terry,
Just for future reference, you specifically need the -- before the
--hint. This tells rb-site to ignore the --hint and to instead pass it
on to the evolve management command.
What version of Django do you have running on there?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Jan 11, 2011 at 3:26 AM, Terry Zhong think...@gmail.com wrote:
Hi Christian,
Thanks for the reply.
rb-site manage /var/reviewboard evolve -- --hint gives option error,
however, I tried something else.
The instance has been running for over 2 years, I don't know the exact
version I install at first but I believe it's 0.9.x. It has been
upgraded all the way to 1.0.9, nice and smooth. No in-development
release has been used ever since 1.0.
I even tried to edit diffviewer/models.py to add a default value 'M'
to FileDiff.status, so that evolve --hint --execute was a success,
but syncdb still reports errors:
Upgrading Review Board from 1.0.9 to 1.5.2
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
No fixtures found.
# pwd
/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-py2.6.egg/
reviewboard
# rb-site manager /var/reviewboard evolve -- --hint
Usage: rb-site command [options] path
Options:
--version show program's version number and exit
-h, --help show this help message and exit
(and more)
# rb-site manage /var/reviewboard evolve --hint
Usage: rb-site command [options] path
rb-site: error: no such option: --hint
# PYTHONPATH=/var/reviewboard/conf ./manage.py evolve --hint
#- Evolution for diffviewer
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('DiffSet', 'basedir', models.CharField, initial=u'',
max_length=256),
AddField('FileDiff', 'status', models.CharField, initial=USER
VALUE REQUIRED, max_length=1)
]
#--
#- Evolution for reviews
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('DefaultReviewer', 'repository', models.ManyToManyField,
related_model='scmtools.Repository'),
ChangeField('ReviewRequest', 'repository', initial=None,
null=True)
]
#--
#- Evolution for scmtools
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('Repository', 'visible', models.BooleanField,
initial=True),
AddField('Repository', 'raw_file_url', models.CharField,
initial='', max_length=255),
ChangeField('Repository', 'path', initial=None, max_length=255),
ChangeField('Repository', 'mirror_path', initial=None,
max_length=255)
]
#--
Trial evolution successful.
Run './manage.py evolve --hint --execute' to apply evolution.
On Jan 11, 4:59 am, Christian Hammond chip...@chipx86.com wrote:
Hi Terry,
That's strange... Can you run a test for me:
do:
rb-site manage /var/reviewboard evolve -- --hint
(Note that those are double hyphens, not single hyphens)
Show me the results. May hopefully shed some light on it.
At any point, did you try to upgrade to an in-development release
(either nightly or straight from Git)?
Also, do you remember what version of Review Board you started with?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Mon, Jan 10, 2011 at 12:29 PM, Terry Zhong think...@gmail.com wrote:
Hi all,
We have a Review Board 1.0.9 server running smoothly, but the
upgrading to 1.5 fails, with tracebacks below. We've tried 1.5, 1.5.1
and 1.5.2 with easy_install, same tracebacks. Would you please help us
out, thanks a lot.
Debian Squeeze
Python 2.6.6
MySQL 5.1.49
# rb-site upgrade /var/reviewboard/
Rebuilding directory structure
Updating database. This may take a while.
Upgrading Review Board from 1.0.9 to 1.5.2
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
Project signature has changed - an evolution is required
No fixtures found.
/usr/lib/python2.6/dist-packages/Crypto/Util/randpool.py:40:
RandomPool_DeprecationWarning: This application uses RandomPool, which
is BROKEN in older releases. Seehttp://www.pycrypto.org/randpool-broken
RandomPool_DeprecationWarning)
Traceback (most recent call last):
File /usr/local/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.5.2', 'console_scripts', 'rb-
site')()
File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1512, in run
Re: Failed to upgrade from 1.0.9 to 1.5
What I think is happening is that it's attempting to apply the
database migration for lengthening the raw URL field's maximum size
without having applied the addition of that field first. It's possible
that this is due to some confusion in your database's migration
history.
Can you go to: http://yoursite/admin/db/django_evolution/evolution/
and screenshot what you see? You can send it to me privately. It'll
help figure out what's been applied and what hasn't. We may be able to
fix this manually.
Before we do anything further, though, please make sure you have a
full backup of your database.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Jan 11, 2011 at 3:39 AM, Christian Hammond chip...@chipx86.com wrote:
Hi Terry,
Just for future reference, you specifically need the -- before the
--hint. This tells rb-site to ignore the --hint and to instead pass it
on to the evolve management command.
What version of Django do you have running on there?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Jan 11, 2011 at 3:26 AM, Terry Zhong think...@gmail.com wrote:
Hi Christian,
Thanks for the reply.
rb-site manage /var/reviewboard evolve -- --hint gives option error,
however, I tried something else.
The instance has been running for over 2 years, I don't know the exact
version I install at first but I believe it's 0.9.x. It has been
upgraded all the way to 1.0.9, nice and smooth. No in-development
release has been used ever since 1.0.
I even tried to edit diffviewer/models.py to add a default value 'M'
to FileDiff.status, so that evolve --hint --execute was a success,
but syncdb still reports errors:
Upgrading Review Board from 1.0.9 to 1.5.2
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
No fixtures found.
# pwd
/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-py2.6.egg/
reviewboard
# rb-site manager /var/reviewboard evolve -- --hint
Usage: rb-site command [options] path
Options:
--version show program's version number and exit
-h, --help show this help message and exit
(and more)
# rb-site manage /var/reviewboard evolve --hint
Usage: rb-site command [options] path
rb-site: error: no such option: --hint
# PYTHONPATH=/var/reviewboard/conf ./manage.py evolve --hint
#- Evolution for diffviewer
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('DiffSet', 'basedir', models.CharField, initial=u'',
max_length=256),
AddField('FileDiff', 'status', models.CharField, initial=USER
VALUE REQUIRED, max_length=1)
]
#--
#- Evolution for reviews
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('DefaultReviewer', 'repository', models.ManyToManyField,
related_model='scmtools.Repository'),
ChangeField('ReviewRequest', 'repository', initial=None,
null=True)
]
#--
#- Evolution for scmtools
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('Repository', 'visible', models.BooleanField,
initial=True),
AddField('Repository', 'raw_file_url', models.CharField,
initial='', max_length=255),
ChangeField('Repository', 'path', initial=None, max_length=255),
ChangeField('Repository', 'mirror_path', initial=None,
max_length=255)
]
#--
Trial evolution successful.
Run './manage.py evolve --hint --execute' to apply evolution.
On Jan 11, 4:59 am, Christian Hammond chip...@chipx86.com wrote:
Hi Terry,
That's strange... Can you run a test for me:
do:
rb-site manage /var/reviewboard evolve -- --hint
(Note that those are double hyphens, not single hyphens)
Show me the results. May hopefully shed some light on it.
At any point, did you try to upgrade to an in-development release
(either nightly or straight from Git)?
Also, do you remember what version of Review Board you started with?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Mon, Jan 10, 2011 at 12:29 PM, Terry Zhong think...@gmail.com wrote:
Hi all,
We have a Review Board 1.0.9 server running smoothly, but the
upgrading to 1.5 fails, with tracebacks below. We've tried 1.5, 1.5.1
and 1.5.2 with easy_install, same tracebacks. Would you please help us
out, thanks a lot.
Debian Squeeze
Python 2.6.6
MySQL 5.1.49
# rb-site upgrade /var/reviewboard/
Rebuilding directory structure
Updating database. This may take a while.
Upgrading Review Board from 1.0.9 to 1.5.2
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for
Re: Failed to upgrade from 1.0.9 to 1.5
Hi Christian,
Your instinct is correct. I printed out the mutations in the evolve
process, and find the faulting field 'raw_file_url' is 'AddField' in
hinted version and 'ChangeField' in stored version. I don't know why
this is happening but it seems that the evolve history contained an
entry of 'raw_file_url' but in fact not applied. After a manual remove
of the history, rb-site successfully upgraded the instance.
Thanks for your help and I'd like to know the reason of this
confusion.
Terry
On Jan 11, 7:46 pm, Christian Hammond chip...@chipx86.com wrote:
What I think is happening is that it's attempting to apply the
database migration for lengthening the raw URL field's maximum size
without having applied the addition of that field first. It's possible
that this is due to some confusion in your database's migration
history.
Can you go to:http://yoursite/admin/db/django_evolution/evolution/
and screenshot what you see? You can send it to me privately. It'll
help figure out what's been applied and what hasn't. We may be able to
fix this manually.
Before we do anything further, though, please make sure you have a
full backup of your database.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Tue, Jan 11, 2011 at 3:39 AM, Christian Hammond chip...@chipx86.com
wrote:
Hi Terry,
Just for future reference, you specifically need the -- before the
--hint. This tells rb-site to ignore the --hint and to instead pass it
on to the evolve management command.
What version of Django do you have running on there?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Tue, Jan 11, 2011 at 3:26 AM, Terry Zhong think...@gmail.com wrote:
Hi Christian,
Thanks for the reply.
rb-site manage /var/reviewboard evolve -- --hint gives option error,
however, I tried something else.
The instance has been running for over 2 years, I don't know the exact
version I install at first but I believe it's 0.9.x. It has been
upgraded all the way to 1.0.9, nice and smooth. No in-development
release has been used ever since 1.0.
I even tried to edit diffviewer/models.py to add a default value 'M'
to FileDiff.status, so that evolve --hint --execute was a success,
but syncdb still reports errors:
Upgrading Review Board from 1.0.9 to 1.5.2
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
No fixtures found.
# pwd
/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.2-py2.6.egg/
reviewboard
# rb-site manager /var/reviewboard evolve -- --hint
Usage: rb-site command [options] path
Options:
--version show program's version number and exit
-h, --help show this help message and exit
(and more)
# rb-site manage /var/reviewboard evolve --hint
Usage: rb-site command [options] path
rb-site: error: no such option: --hint
# PYTHONPATH=/var/reviewboard/conf ./manage.py evolve --hint
#- Evolution for diffviewer
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('DiffSet', 'basedir', models.CharField, initial=u'',
max_length=256),
AddField('FileDiff', 'status', models.CharField, initial=USER
VALUE REQUIRED, max_length=1)
]
#--
#- Evolution for reviews
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('DefaultReviewer', 'repository', models.ManyToManyField,
related_model='scmtools.Repository'),
ChangeField('ReviewRequest', 'repository', initial=None,
null=True)
]
#--
#- Evolution for scmtools
from django_evolution.mutations import *
from django.db import models
MUTATIONS = [
AddField('Repository', 'visible', models.BooleanField,
initial=True),
AddField('Repository', 'raw_file_url', models.CharField,
initial='', max_length=255),
ChangeField('Repository', 'path', initial=None, max_length=255),
ChangeField('Repository', 'mirror_path', initial=None,
max_length=255)
]
#--
Trial evolution successful.
Run './manage.py evolve --hint --execute' to apply evolution.
On Jan 11, 4:59 am, Christian Hammond chip...@chipx86.com wrote:
Hi Terry,
That's strange... Can you run a test for me:
do:
rb-site manage /var/reviewboard evolve -- --hint
(Note that those are double hyphens, not single hyphens)
Show me the results. May hopefully shed some light on it.
At any point, did you try to upgrade to an in-development release
(either nightly or straight from Git)?
Also, do you remember what version of Review Board you started with?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board
Question about postreview.py get_repository_info
Hi Here I have a problem with postreview.py when publish a review request, could anyone please have a look? My enviroment is Reviewboard 1.5.1 and SVN. I downloaded postreview.py from https://github.com/reviewboard/rbtools/blob/184334a7a5ddc24172ae2aa0364f13aabe037470/rbtools/postreview.py, and configed the constants necessary. When I run postreivew, it throws a array index exception at line 677: url = rsp['links']['info']['href'], The whole piece of code is def get_repository_info(self, rid): Returns detailed information about a specific repository. if self.deprecated_api: url = 'api/json/repositories/%s/info/' % rid else: rsp = self.api_get( '%s%s/' % (self.root_resource['links']['repositories'] ['href'], rid)) url = rsp['links']['info']['href'] rsp = self.api_get(url) return rsp['info'] I added debug info for rep, it did not contain the links index indeed, but it contained a repository index. Then I manually went to check the xml from reviewboard server, and found the structure of the xml is like this rsp repository links info href so I changed line 677 to url = rsp[repository]['links']['info'] ['href'], finally it worked. Though it worked, I still did not know the reason and whether my change is right or wrong. I think it is unlike to be a bug of reviewboard, but I am too lazy to read all the code :-) so, could anyone kindly tell me that what the real problem is and what should I do? Any help will be highly appreciated! -- 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: GIT Repository - Local vs Remote Setup
thanks for the reply but something still isn't jiving with our setup. Installation information: ReviewBoard - version 1.5.1 GIT and GITWeb - version 1.7.0.4 We're using gitosis to control access to the repositories. Your example shows an http address for the path - does that mean that ReviewBoard expects the GIT repositories to be available via http? We don't have http access to the repos so I tried setting the path to: http://path/to/gitweb?p=repo.git (the base gitweb address) That results in: A repository was not found at the specified path. Our origin URL, as shown by 'git remote show origin', is: gito...@gitserver:repo.git Putting that in the Path results in the same not found at specified path error. Maybe I should start by asking what requirements ReviewBoard has in regards to GIT installations. Does it need http access to the repositories? Does it need non-authenticated file access? Will it work when repositories are available only via SSH key authentication and GITWeb? Thanks. On Jan 10, 11:00 pm, Christian Hammond chip...@chipx86.com wrote: Hi, First off, can you tell me which version of Review Board you're using? Perhaps the documentation is misleading, but what you should be doing is setting Path to be the origin URL. Review Board will use Path to attempt to match the repository provided by post-review (which it gets from doing 'git remote show origin'). If you point it to a local URL, it will try to access it, but if you otherwise use a remote URL, it won't try and instead will use the raw URL that was set. So you'd want: Path:http://git.example.com/blah/blah/blah.git Raw URL:http://path/to/gitweb/withfileandrevision Does that help? Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Mon, Jan 10, 2011 at 6:04 PM, NicBinkley nbink...@vmem.com wrote: I am attempting to setup ReviewBoard to use our GIT repositories on another server via GitWeb. The issue I'm running into is that I cannot complete the ReviewBoard repository setup UNLESS there is a valid local copy of the GIT repo on the same server. It will error out when clicking save if the Path is either not set or set to a dummy .git directory. All the instructions I've found say that the Path is not needed/used if the RAW file url mask is set. What did work is cloning the repo to the ReviewBoard server and then complete the setup using that path as the Path variable but that seems counter-intuitive to what I want (which is for ReviewBoard to use the GitWeb URL). Is this expected behavior? i.e. is an initial valid repository required only for setup purposes but after that it's never used? Here's a breakdown of what was tried: Attempt one: Failed. It also triggered django failure email to root @ localhost Hosting Service: Custom Repository Type: git Path: blank Mirror Path: blank RAW File Url mask:http://path/to/gitweb/withfileandrevision Attempt two: Failed with: django.utils.functional.__proxy__ object at 0x2ad39488e510 Hosting Service: Custom Repository Type: git Path: /path/to/dummy_repository Mirror Path: blank RAW File Url mask:http://path/to/gitweb/withfileandrevision Attempt Three: worked Hosting Service: Custom Repository Type: git Path: /path/to/valid/repository/.git Mirror Path: blank RAW File Url mask:http://path/to/gitweb/withfileandrevision -- Want to help the Review Board project? Donate today athttp://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 athttp://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: GIT Repository - Local vs Remote Setup
Hi, The http one is just an example. I'll give you a real-world example. http://reviews.reviewboard.org uses the following for our Review Board Git repo: Path: git://github.com/reviewboard/reviewboard.git Mirror Path: g...@github.com:reviewboard/reviewboard.git Raw file URL mask: http://github.com/api/v2/yaml/blob/show/reviewboard/reviewboard/revision The problem in your case is that it's backed by SSH, and you likely don't have a proper key setup that Review Board can access. We just put out the 1.5.2 release, which does a lot to make this clearer. It provides a more meaningful error when it's hitting key issues with SSH, and it fixes authentication issues (sometimes leading to repository not found errors) due to some parsing problems. It also provides SSH key management (admin UI - Settings - SSH), allowing you to create a brand new SSH key for your RB setup (you can then use the public key provided after creation) to allow access on the server end. Or you can upload an existing private key for RB to use. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Tue, Jan 11, 2011 at 10:47 AM, NicBinkley nbink...@vmem.com wrote: thanks for the reply but something still isn't jiving with our setup. Installation information: ReviewBoard - version 1.5.1 GIT and GITWeb - version 1.7.0.4 We're using gitosis to control access to the repositories. Your example shows an http address for the path - does that mean that ReviewBoard expects the GIT repositories to be available via http? We don't have http access to the repos so I tried setting the path to: http://path/to/gitweb?p=repo.git (the base gitweb address) That results in: A repository was not found at the specified path. Our origin URL, as shown by 'git remote show origin', is: gito...@gitserver:repo.git Putting that in the Path results in the same not found at specified path error. Maybe I should start by asking what requirements ReviewBoard has in regards to GIT installations. Does it need http access to the repositories? Does it need non-authenticated file access? Will it work when repositories are available only via SSH key authentication and GITWeb? Thanks. On Jan 10, 11:00 pm, Christian Hammond chip...@chipx86.com wrote: Hi, First off, can you tell me which version of Review Board you're using? Perhaps the documentation is misleading, but what you should be doing is setting Path to be the origin URL. Review Board will use Path to attempt to match the repository provided by post-review (which it gets from doing 'git remote show origin'). If you point it to a local URL, it will try to access it, but if you otherwise use a remote URL, it won't try and instead will use the raw URL that was set. So you'd want: Path:http://git.example.com/blah/blah/blah.git Raw URL:http://path/to/gitweb/withfileandrevision Does that help? Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Mon, Jan 10, 2011 at 6:04 PM, NicBinkley nbink...@vmem.com wrote: I am attempting to setup ReviewBoard to use our GIT repositories on another server via GitWeb. The issue I'm running into is that I cannot complete the ReviewBoard repository setup UNLESS there is a valid local copy of the GIT repo on the same server. It will error out when clicking save if the Path is either not set or set to a dummy .git directory. All the instructions I've found say that the Path is not needed/used if the RAW file url mask is set. What did work is cloning the repo to the ReviewBoard server and then complete the setup using that path as the Path variable but that seems counter-intuitive to what I want (which is for ReviewBoard to use the GitWeb URL). Is this expected behavior? i.e. is an initial valid repository required only for setup purposes but after that it's never used? Here's a breakdown of what was tried: Attempt one: Failed. It also triggered django failure email to root @ localhost Hosting Service: Custom Repository Type: git Path: blank Mirror Path: blank RAW File Url mask:http://path/to/gitweb/withfileandrevision Attempt two: Failed with: django.utils.functional.__proxy__ object at 0x2ad39488e510 Hosting Service: Custom Repository Type: git Path: /path/to/dummy_repository Mirror Path: blank RAW File Url mask:http://path/to/gitweb/withfileandrevision Attempt Three: worked Hosting Service: Custom Repository Type: git Path: /path/to/valid/repository/.git Mirror Path: blank RAW File Url mask:http://path/to/gitweb/withfileandrevision -- Want to help the Review Board project? Donate today athttp://www.reviewboard.org/donate/ Happy user? Let us know athttp://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group,
