Yes, this is for the 1.1 development series. It's the HEAD from
github.
I tried running "./reviewboard/manage.py registerscmtools", but was
met with this error:
Unable to load SCMTool svn = reviewboard.scmtools.svn:SVNTool:
(Djblets 0.5.6.dev (/home/rroblak/workspace/djblets), Requirement.parse
Hi,
This problem has been resolved; in the .reviewboardrc , I set the
REVIEWBOARD_URL as http://192.168.3.20:8080/reviewboard; after I
delete the "reviewboard" ,login is successful now. But I stil can not
use RB yet, Error info:
Error creating review request: The repository path specified is not
Hi,
The Path or Mirror Path for the Repository entry in the admin UI in Review
Board must be exactly what post-review is trying to report. So, in your
case, it should be "cvs_gz/export/home/cvsoot". I'm hoping to add fuzzy
matching in the future (so as to make it possible to use aliases for
domain
Hi, I now set it like that with admin UI, But things is also the same.
The Repository account given to me by CVS Administrator
is :pserver:myn...@192.168.3.151:/export/home/cvsroot ,But the actual
repository is a subdirectory of the cvsroot, named "test". Then how to
set my Repository please? And
Hi,all,
It seems that the ReviewBoard help Review code with a Human
positive process, But somtimes a programmer may lazy to make code
review process and commit his code directly. So is there any way to
force all RB users in a ReviewGroup to make pre-commit review? say, If
somebody write new cod
Hi,
The detailed error info is:
-
[jo...@dev2 test]$ post-review --debug --username=Johnl1 --
password=Johnl1 myTestCode.c
>>> svn info
>>> repository info: Path: cvs_gz:/export/home/cvsroot, Base path: None,
>>> Supports changesets: False
>>> cv
On Mon, Dec 14, 2009 at 6:49 AM, JohnHenry wrote:
> Hi,all,
> It seems that the ReviewBoard help Review code with a Human
> positive process, But somtimes a programmer may lazy to make code
> review process and commit his code directly. So is there any way to
> force all RB users in a ReviewGro
With CVS you can write pre-commit scripts. In our repository, we are
required to input a valid defect ID as the first item in the commit log. CVS
looks up that defect ID and checks for the results of a review request.
Alternatively, you could require the developers to include the review id in
the c
Hello everyone,
I am currently somewhat stuck figuring out the cause of an error that
some colleagues are getting in response to the
/api/json/reviewrequests//diff/new/ call when posting a new review
request:
{u'fields': {u'path': [u'This field is required.']}, u'stat': u'fail',
u'err': {u'msg':
Hi,
After following the installation guide, I got RB kind of working on
centos but when I go to default page I get the message: Manual server
updates required
The suggestion is to run manage.py. After some investigation I found
someone that recommended a rb-site upgrade instead and that command
r
Hi,
The manual updates page is old and generally isn't seen anymore. We'll need
to update the text to reference rb-site instead of manage.py.
The error definitely seems to be that PIL isn't installed correctly. Yes,
easy_install should get it, but perhaps something went wrong. What version
of Pyt
Which version of Review Board is this running right now? I've seen this
recently on the 1.1 alpha nightlies.
Also, what repository type is this? It could indicate a missing dependency.
The error checking/reporting for that on 1.0.x is pretty bad, but improved
in 1.1.
Is this only happening to som
You'll need cvs diff -uN. It's best just to use post-review though.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Sun, Dec 13, 2009 at 7:18 PM, JohnHenry wrote:
> Hi, all,
>I tried the use ReviewBoar
Hi,
You will need cvs on the server, definitely. The 1.1 alpha series won't let
you create a CVS repository without having it. You'll also need it on the
client running post-review.
The base path should be None in this case. It's really only needed for
Subversion.
Can you show me the Repository
On Monday 14 December 2009 22:28:35 Christian Hammond wrote:
> Which version of Review Board is this running right now? I've seen this
> recently on the 1.1 alpha nightlies.
It's a slightly patched 1.0.5.1.
> Also, what repository type is this? It could indicate a missing dependency.
> The error
It should just be the field constraints from those FileFields. We don't do
any custom validation checks in those forms that I can see.
It could potentially fail if the diff itself is empty, even though the name
is populated. Are they uploading using post-review? Might be worth seeing
what post-rev
I am getting the same issue:
r...@scubuntuvm1:~# python --version
Python 2.5.2
r...@scubuntuvm1:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 8.04.3 LTS
Release:8.04
Codename: hardy
r...@scubuntuvm1:~# uname -r
2.6.24-23-generic
On Dec
>From a python prompt, type:
import PIL
If that fails, then PIL is not installed on the system. If it does work,
then we need to investigate why your Python isn't seeing it. I assume you've
done a web server restart since installing Review Board?
Christian
--
Christian Hammond - chip...@ch
OK, I am using ReviewBoardV1.05 My Repository setting on Administrator
UI is as follows:
Name: NewProductCode
Path: :perver:jo...@192.168.3.151:/export/home/
cvsroot
Mirror Path: /cvs_gz/export/home/cvsroot
Repository Type: CVS
Username:
Thanks for reply, It works now.
Best Regards!
On Dec 15, 5:29 am, Christian Hammond wrote:
> You'll need cvs diff -uN. It's best just to use post-review though.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vm
With your help, I can use WebUI pre-commit review now. But why the
post-review can't find "Base
Path" of repository?
Regards!
On Dec 15, 5:35 am, Christian Hammond wrote:
> Hi,...
>
> read more >>
>
> You will need cvs on the server, definitely. The 1.1 alpha series won't let
> you create a CVS r
Another problem is When I am using CVS repository, the debug info
report is :
>>> svn info
On Dec 15, 5:35 am, Christian Hammond wrote:
> Hi,...
>
> read more >>
>
> You will need cvs on the server, definitely. The 1.1 alpha series won't let
> you create a CVS repository without having it. You'l
Hi, Christian,
I have changed the source of Postreview.py, and now the post-
review can work fine. I found that in class CVSClient, the function
get_repository_info, It use socket.getfqdn(host) to replace the host
of repository_path; So I managed to keep the repository_path
unchanged. Though I
The getfqdn call essentially gets the fully-qualified domain (so,
foo.example.com instead of just foo, for instance).
We recently added support for Perforce to check against all aliases,
including what's reported locally. We should add this for CVS as well.
I don't really know what you mean by re
Hi, Christian,
Thanks for replay. I said "rebuild" because I am using the directly
installed ReviewBoard, I don't know it's compiling form souce process.
If I want to change some python source code of ReviewBoard, Then how
to compile the ReviewBoard again, and do I need to reinstall the
compile
Review Board is in Python, and doesn't actually need to be compiled.
However, to do any real development (with the expectation of contributing
back to the project) you'll need to have a copy of the source tree and
develop from there. There's some instructions at:
http://www.reviewboard.org/docs/co
Oh, I see. Thank you very much！
Best Regards!
On 12月15日, 下午2时13分, Christian Hammond wrote:
> Review Board is in Python, and doesn't actually need to be compiled.
> However, to do any real development (with the expectation of contributing
> back to the project) you'll need to have a copy of the s
Oh, I see. Thank you very much！
Best Regards!
On 12月15日, 下午2时13分, Christian Hammond wrote:
> Review Board is in Python, and doesn't actually need to be compiled.
> However, to do any real development (with the expectation of contributing
> back to the project) you'll need to have a copy of the s
Hi,
I have tried to post a review request and publish it using one
User, But in the Reviewers' UI, when He cilck the "view diff" link on
the top-right, There will be some error infomation:
**
The patch to 'mySouceTest.c' didn't apply cleanly. The t
29 matches
Mail list logo
