Uploading attachments by reviewers

[Joe]

Hello,

In reviewboard the submitter can upload a file for review. Is it also 
possible to allow the reviewers (by some configuration) to upload a file 
into the reviewboard?

Thanks,
Joe

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: No diffs to review when creating review request from commit (commit has plenty of diffs)

[Joe Cooper]

I'm not sure how soon I'll be able to do that, but this problem is 
reproducible with other commits.

To Reproduce:
1. Commit a change to git where the following is true: a) a file is renamed 
& b) the same file is modified. Any file will do.
2. Create a review request for that commit

Environment Info:
- Repository is hosted in Git Hub
- Code is C# (although I really don't think this is relevant)
- We are using version 2.5.3

On Tuesday, June 21, 2016 at 12:08:42 PM UTC-4, David Trowbridge wrote:
>
> Well, we should figure out what part of the diff file isn't being parsed 
> correctly. If you're willing to jump into the code to make it save the diff 
> so we can have a sample, we can get the bug fixed.
>
> -David
>
> On Tue, Jun 21, 2016 at 9:04 AM Joe Cooper  > wrote:
>
>> I've narrowed this problem down to if the same file is modified and 
>> renamed in the same commit, no diffs are generated for any file when 
>> creating a review request and the 'could not be found in the repository' 
>> error is logged. Is there a work-around for this besides not committing a 
>> modification and rename at the same time?
>>
>> On Monday, June 20, 2016 at 2:48:08 PM UTC-4, Joe Cooper wrote:
>>>
>>> David,
>>>
>>> Thank you for your prompt feedback.
>>>
>>> I've added the error details from the log below. I the commit I had a 
>>> problem with a file was renamed to: ''/some/path/SomeFile.cs'. I'm not sure 
>>> why there would be a problem because the file is indeed in the repository 
>>> at that time. Unless the python code is looking for that file in the parent 
>>> commit? 
>>>
>>> What would be the best way to resolve this? Is there an configuration 
>>> option to ignore these types of errors so we can at least get diffs for the 
>>> remaining files? Is there a way to avoid this type of problem?
>>>
>>>
>>>
>>>
>>>  2016-06-20 18:15:34,668 - ERROR - - Unable to update new review request 
>>> from commit ID fa4e9537b44661f3d815d7b9bdbc413344f879bc: The file 
>>> '/some/path/SomeFile.cs' (r) could not be found in the repository
>>> Traceback (most recent call last):
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/managers.py", 
>>> line 150, in create
>>> review_request.update_from_commit_id(commit_id)
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
>>>  
>>> line 220, in update_from_commit_id
>>> self.update_from_committed_change(commit_id)
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
>>>  
>>> line 283, in update_from_committed_change
>>> base_commit_id=commit.base_commit_id)
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
>>> line 441, in create_from_data
>>> check_existence=(not parent_diff_file_contents)))
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
>>> line 586, in _process_files
>>> base_commit_id)
>>> FileNotFoundError: The file '/some/path/SomeFile.cs' (r) could not be 
>>> found in the repository
>>>
>>> 2016-06-20 18:15:34,668 - ERROR - - Unable to update new review request 
>>> from commit ID fa4e9537b44661f3d815d7b9bdbc413344f879bc: The file 
>>> '/some/path/SomeFile.cs' (r) could not be found in the repository
>>> Traceback (most recent call last):
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/managers.py", 
>>> line 150, in create
>>> review_request.update_from_commit_id(commit_id)
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
>>>  
>>> line 220, in update_from_commit_id
>>> self.update_from_committed_change(commit_id)
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
>>>  
>>> line 283, in update_from_committed_change
>>> base_commit_id=commit.base_commit_id)
>>> File 
>>> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
>>> line 441, in create_from_data
>>> check_existence=(not parent_diff_file_contents)))
>>

Re: No diffs to review when creating review request from commit (commit has plenty of diffs)

[Joe Cooper]

I've narrowed this problem down to if the same file is modified and renamed 
in the same commit, no diffs are generated for any file when creating a 
review request and the 'could not be found in the repository' error is 
logged. Is there a work-around for this besides not committing a 
modification and rename at the same time?

On Monday, June 20, 2016 at 2:48:08 PM UTC-4, Joe Cooper wrote:
>
> David,
>
> Thank you for your prompt feedback.
>
> I've added the error details from the log below. I the commit I had a 
> problem with a file was renamed to: ''/some/path/SomeFile.cs'. I'm not sure 
> why there would be a problem because the file is indeed in the repository 
> at that time. Unless the python code is looking for that file in the parent 
> commit? 
>
> What would be the best way to resolve this? Is there an configuration 
> option to ignore these types of errors so we can at least get diffs for the 
> remaining files? Is there a way to avoid this type of problem?
>
>
>
>
>  2016-06-20 18:15:34,668 - ERROR - - Unable to update new review request 
> from commit ID fa4e9537b44661f3d815d7b9bdbc413344f879bc: The file 
> '/some/path/SomeFile.cs' (r) could not be found in the repository
> Traceback (most recent call last):
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/managers.py", 
> line 150, in create
> review_request.update_from_commit_id(commit_id)
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
>  
> line 220, in update_from_commit_id
> self.update_from_committed_change(commit_id)
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
>  
> line 283, in update_from_committed_change
> base_commit_id=commit.base_commit_id)
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
> line 441, in create_from_data
> check_existence=(not parent_diff_file_contents)))
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
> line 586, in _process_files
> base_commit_id)
> FileNotFoundError: The file '/some/path/SomeFile.cs' (r) could not be 
> found in the repository
>
> 2016-06-20 18:15:34,668 - ERROR - - Unable to update new review request 
> from commit ID fa4e9537b44661f3d815d7b9bdbc413344f879bc: The file 
> '/some/path/SomeFile.cs' (r) could not be found in the repository
> Traceback (most recent call last):
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/managers.py", 
> line 150, in create
> review_request.update_from_commit_id(commit_id)
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
>  
> line 220, in update_from_commit_id
> self.update_from_committed_change(commit_id)
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
>  
> line 283, in update_from_committed_change
> base_commit_id=commit.base_commit_id)
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
> line 441, in create_from_data
> check_existence=(not parent_diff_file_contents)))
> File 
> "/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
> line 586, in _process_files
> base_commit_id)
> FileNotFoundError: The file '/some/path/SomeFile.cs' (r) could not be 
> found in the repository
> Show less
>
>
>
>
> On Monday, June 20, 2016 at 12:10:56 PM UTC-4, David Trowbridge wrote:
>>
>> Are there any errors in the Review Board log file?
>>
>> -David
>> On Mon, Jun 20, 2016 at 9:09 AM Joe Cooper  
>> wrote:
>>
>>> Hi,
>>>
>>> My team is using Review Board version 2.5.3. 
>>>
>>> We are using a github hosted repo. We create review requests by 
>>> selecting a repo -> branch -> and then selecting the commit to review on 
>>> the web interface. 
>>>
>>> Sometimes, the diff is not generated for the review. That is, the Diffs 
>>> tab is not available and the Diff Size is blank even though the commit 
>>> includes a lot of diffs. The last time this happened, the commit in 
>>> question happened before a merge. The merge commit generates diffs just 
>>> fine.  
>>>
>>> So far we have tried:
>>> 1. Deleting reviews permanently and recreating
>>> 2. Recreating using different users
>>> 3. Rebooting the server hosting reviewboard web app
>>>

Re: No diffs to review when creating review request from commit (commit has plenty of diffs)

[Joe Cooper]

David,

Thank you for your prompt feedback.

I've added the error details from the log below. I the commit I had a 
problem with a file was renamed to: ''/some/path/SomeFile.cs'. I'm not sure 
why there would be a problem because the file is indeed in the repository 
at that time. Unless the python code is looking for that file in the parent 
commit? 

What would be the best way to resolve this? Is there an configuration 
option to ignore these types of errors so we can at least get diffs for the 
remaining files? Is there a way to avoid this type of problem?




 2016-06-20 18:15:34,668 - ERROR - - Unable to update new review request 
from commit ID fa4e9537b44661f3d815d7b9bdbc413344f879bc: The file 
'/some/path/SomeFile.cs' (r) could not be found in the repository
Traceback (most recent call last):
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/managers.py", 
line 150, in create
review_request.update_from_commit_id(commit_id)
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
 
line 220, in update_from_commit_id
self.update_from_committed_change(commit_id)
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
 
line 283, in update_from_committed_change
base_commit_id=commit.base_commit_id)
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
line 441, in create_from_data
check_existence=(not parent_diff_file_contents)))
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
line 586, in _process_files
base_commit_id)
FileNotFoundError: The file '/some/path/SomeFile.cs' (r) could not be found 
in the repository

2016-06-20 18:15:34,668 - ERROR - - Unable to update new review request 
from commit ID fa4e9537b44661f3d815d7b9bdbc413344f879bc: The file 
'/some/path/SomeFile.cs' (r) could not be found in the repository
Traceback (most recent call last):
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/managers.py", 
line 150, in create
review_request.update_from_commit_id(commit_id)
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
 
line 220, in update_from_commit_id
self.update_from_committed_change(commit_id)
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/reviews/models/base_review_request_details.py",
 
line 283, in update_from_committed_change
base_commit_id=commit.base_commit_id)
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
line 441, in create_from_data
check_existence=(not parent_diff_file_contents)))
File 
"/opt/bitnami/apps/reviewboard/htdocs/reviewboard/diffviewer/managers.py", 
line 586, in _process_files
base_commit_id)
FileNotFoundError: The file '/some/path/SomeFile.cs' (r) could not be found 
in the repository
Show less




On Monday, June 20, 2016 at 12:10:56 PM UTC-4, David Trowbridge wrote:
>
> Are there any errors in the Review Board log file?
>
> -David
> On Mon, Jun 20, 2016 at 9:09 AM Joe Cooper  > wrote:
>
>> Hi,
>>
>> My team is using Review Board version 2.5.3. 
>>
>> We are using a github hosted repo. We create review requests by selecting 
>> a repo -> branch -> and then selecting the commit to review on the web 
>> interface. 
>>
>> Sometimes, the diff is not generated for the review. That is, the Diffs 
>> tab is not available and the Diff Size is blank even though the commit 
>> includes a lot of diffs. The last time this happened, the commit in 
>> question happened before a merge. The merge commit generates diffs just 
>> fine.  
>>
>> So far we have tried:
>> 1. Deleting reviews permanently and recreating
>> 2. Recreating using different users
>> 3. Rebooting the server hosting reviewboard web app
>>
>> None of these have worked. Does anyone have a suggestion as this is a bit 
>> of a show-stopper in terms of us being able to use this tool for reviews.
>>
>> Thanks in advance,
>> Joe
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
Supercharge your Review Board wi

No diffs to review when creating review request from commit (commit has plenty of diffs)

[Joe Cooper]

Hi,

My team is using Review Board version 2.5.3. 

We are using a github hosted repo. We create review requests by selecting a 
repo -> branch -> and then selecting the commit to review on the web 
interface. 

Sometimes, the diff is not generated for the review. That is, the Diffs tab 
is not available and the Diff Size is blank even though the commit includes 
a lot of diffs. The last time this happened, the commit in question 
happened before a merge. The merge commit generates diffs just fine.  

So far we have tried:
1. Deleting reviews permanently and recreating
2. Recreating using different users
3. Rebooting the server hosting reviewboard web app

None of these have worked. Does anyone have a suggestion as this is a bit 
of a show-stopper in terms of us being able to use this tool for reviews.

Thanks in advance,
Joe

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Custom fields in review-board

[Joe]

Hello,

I see from the documentation that it is still only possible to add extended 
review request fields only as text-inputs. Does that still hold true?

Is there any long term plan to support checkboxes and pull down menus. 
Those would be very helpful.

Best Regards,
Joe.

On Thursday, August 28, 2014 at 10:48:28 PM UTC+2, David Trowbridge wrote:
>
> Hi,
>
> If you're running 2.0.x, it is possible to add fields using an extension. 
> Right now this is only really capable of dealing with text-inputs (either 
> short or long form). See 
> https://www.reviewboard.org/docs/manual/2.0/extending/extensions/hooks/review-request-fields-hook/
>  
> for more info.
>
> -David
>
>
> On Thu, Aug 28, 2014 at 10:16 AM, Venkataraman R  > wrote:
>
>> Hi,
>>
>> I would like to add some custom fields in the review board like Product 
>> version, Impact to the product: Y/N ..etc. Is there option to do this?
>>
>>
>> Thanks,
>> VR
>>
>> -- 
>> Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
>> ---
>> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
>> ---
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to avoid empty draft creation when upload diff fails

[Joe]

Hello,

In our company, we have a custom source code packaging format. So we have 
written a wrapper above rbtools, based on  this link

https://www.reviewboard.org/docs/rbtools/dev/api/tutorial/

In our python script, we use the following snippet to create and upload a 
review request:

f = open("path/to/diff.txt", mode="r")
> diff_contents = f.read()
> f.close()
>
> review_request.get_diffs().upload_diff(diff_contents)
>
>
>
>
 The problem here is, when we upload a diff for which the file path doesn’t 
exist, then it throws an error 

The file was not found in the repository (HTTP 400, API Error 207)


However, an empty draft with no diff is generated in the review board site. 
Is there a way to avoid this? Or permanently delete this draft (we don’t 
want to discard it, but permanently delete it)

Best Regards,  
Joe.
 

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Table 'reviewboard.auth_user' doesn't exist

[Joe]

Hi David,

That has been the issue. When I tried to print the django version with the 
python command, it said

(1,6,5)

Now I removed that and have again reinstalled 1.4.13 and Im able to 
successfully install the rb-site.

Thanks for your help!

Best Regards,  
Joe.


On Saturday, July 12, 2014 12:26:13 AM UTC+2, David Trowbridge wrote:
>
> Can you just quickly verify that it's actually using that version of 
> django?
>
> $ python
> >>> import django
> >>> print django.VERSION
>
> -David
>
>
> On Fri, Jul 11, 2014 at 3:52 AM, Joe > 
> wrote:
>
>> Hello David, Christian,
>>
>> Following are the version which have been installed:
>>
>> Django 1.4.13
>> Djblets 0.7.30
>>
>> Best regards,  
>> Joe.
>>
>>
>> On Thursday, July 10, 2014 8:58:55 PM UTC+2, Christian Hammond wrote:
>>
>>> Also, what version of Djblets?
>>>
>>> This smells like a dependency version issue.
>>>
>>> Christian
>>>
>>> -- 
>>> Christian Hammond - chri...@beanbaginc.com
>>>
>>> Review Board - http://www.reviewboard.org
>>> Beanbag, Inc. - http://www.beanbaginc.com
>>>
>>> On July 10, 2014 at 11:49:18 AM, David Trowbridge (trow...@gmail.com) 
>>> wrote:
>>>
>>> What version of django did you install? 
>>>
>>> -David
>>>  
>>>
>>> On Thu, Jul 10, 2014 at 8:38 AM, Joe  wrote:
>>>
>>>>  Hello,
>>>>
>>>> Im trying to install review board on a SuSE system, which is our 
>>>> official server in the company. Unfortunately all other ports other than 
>>>> SSH is blocked from communication. So Im not able to use easy_install or 
>>>> pip to install any resources. 
>>>>
>>>> I have manually installed all the necessary packages using the SuSE 
>>>> DVD. And now finally when I try to run 
>>>>
>>>> # rb-site install /var/www/reviewboard.example.com
>>>>
>>>> Note: I have setup mysql with username password and I have already 
>>>> created the database "reviewboard" in it.
>>>>
>>>> Im getting the below error.
>>>>
>>>>  * Installing the site...
>>>> Building site directories ... OK
>>>> Building site configuration files ... OK
>>>> Creating database ...
>>>> [!] Unable to execute the manager command syncdb: cannot import name
>>>> execute_manager
>>>>  
>>>> [!] Unable to execute the manager command registerscmtools: cannot
>>>> import name execute_manager
>>>> OK
>>>> Performing migrations ...
>>>> [!] Unable to execute the manager command evolve: cannot import name
>>>> execute_manager
>>>> OK
>>>> Creating administrator account ... Traceback (most recent call last):
>>>>   File "/usr/local/bin/rb-site", line 8, in 
>>>> load_entry_point('ReviewBoard==1.7.22', 'console_scripts', 
>>>> 'rb-site')()
>>>>   File "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.
>>>> 22-py2.6.egg/reviewboard/cmdline/rbsite.py", line 2055, in main
>>>> command.run()
>>>>   File "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.
>>>> 22-py2.6.egg/reviewboard/cmdline/rbsite.py", line 1496, in run
>>>> self.show_install_status()
>>>>   File "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.
>>>> 22-py2.6.egg/reviewboard/cmdline/rbsite.py", line 1779, in 
>>>> show_install_status
>>>> site.create_admin_user)
>>>>   File "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.
>>>> 22-py2.6.egg/reviewboard/cmdline/rbsite.py", line 967, in step
>>>> func()
>>>>   File "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.
>>>> 22-py2.6.egg/reviewboard/cmdline/rbsite.py", line 553, in 
>>>> create_admin_user
>>>> self.admin_password)
>>>>   File 
>>>> "/usr/local/lib64/python2.6/site-packages/django/contrib/auth/models.py", 
>>>> line 195, in create_superuser
>>>>**extra_fields)
>>>>   File 
>>>> "/usr/local/lib64/python2.6/site-packages/django/contrib/auth/models.py", 
>>>> line 186, in _create_user
>>>> user.save(using=self._db)
>>&

Re: Table 'reviewboard.auth_user' doesn't exist

[Joe]

Hello David, Christian,

Following are the version which have been installed:

Django 1.4.13
Djblets 0.7.30

Best regards,  
Joe.


On Thursday, July 10, 2014 8:58:55 PM UTC+2, Christian Hammond wrote:
>
> Also, what version of Djblets?
>
> This smells like a dependency version issue.
>
> Christian
>
> -- 
> Christian Hammond - chri...@beanbaginc.com 
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>
> On July 10, 2014 at 11:49:18 AM, David Trowbridge (trow...@gmail.com 
> ) wrote:
>
> What version of django did you install? 
>
> -David
>  
>
> On Thu, Jul 10, 2014 at 8:38 AM, Joe > 
> wrote:
>
>>  Hello,
>>
>> Im trying to install review board on a SuSE system, which is our official 
>> server in the company. Unfortunately all other ports other than SSH is 
>> blocked from communication. So Im not able to use easy_install or pip to 
>> install any resources. 
>>
>> I have manually installed all the necessary packages using the SuSE DVD. 
>> And now finally when I try to run 
>>
>> # rb-site install /var/www/reviewboard.example.com
>>
>> Note: I have setup mysql with username password and I have already 
>> created the database "reviewboard" in it.
>>
>> Im getting the below error.
>>
>>  * Installing the site...
>> Building site directories ... OK
>> Building site configuration files ... OK
>> Creating database ...
>> [!] Unable to execute the manager command syncdb: cannot import name
>> execute_manager
>>  
>> [!] Unable to execute the manager command registerscmtools: cannot
>> import name execute_manager
>> OK
>> Performing migrations ...
>> [!] Unable to execute the manager command evolve: cannot import name
>> execute_manager
>> OK
>> Creating administrator account ... Traceback (most recent call last):
>>   File "/usr/local/bin/rb-site", line 8, in 
>> load_entry_point('ReviewBoard==1.7.22', 'console_scripts', 
>> 'rb-site')()
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
>>  
>> line 2055, in main
>> command.run()
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
>>  
>> line 1496, in run
>> self.show_install_status()
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
>>  
>> line 1779, in show_install_status
>> site.create_admin_user)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
>>  
>> line 967, in step
>> func()
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
>>  
>> line 553, in create_admin_user
>> self.admin_password)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/django/contrib/auth/models.py", 
>> line 195, in create_superuser
>>**extra_fields)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/django/contrib/auth/models.py", 
>> line 186, in _create_user
>> user.save(using=self._db)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/django/db/models/base.py", line 
>> 545, in save
>> force_update=force_update, update_fields=update_fields)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/django/db/models/base.py", line 
>> 573, in save_base
>> updated = self._save_table(raw, cls, force_insert, force_update, 
>> using, update_fields)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/django/db/models/base.py", line 
>> 654, in _save_table
>> result = self._do_insert(cls._base_manager, using, fields, update_pk, 
>> raw)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/django/db/models/base.py", line 
>> 687, in _do_insert
>> using=using, raw=raw)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/django/db/models/manager.py", 
>> line 232, in _insert
>> return insert_query(self.model, objs, fields, **kwargs)
>>   File 
>> "/usr/local/lib64/python2.6/site-packages/django/db/models/query.py", line 
>> 1514, in insert_query
>> return query.get_compiler(using=using).execute_sql(return_id)
>>   Fil

Table 'reviewboard.auth_user' doesn't exist

[Joe]

Hello,

Im trying to install review board on a SuSE system, which is our official 
server in the company. Unfortunately all other ports other than SSH is 
blocked from communication. So Im not able to use easy_install or pip to 
install any resources. 

I have manually installed all the necessary packages using the SuSE DVD. 
And now finally when I try to run 

# rb-site install /var/www/reviewboard.example.com

Note: I have setup mysql with username password and I have already created 
the database "reviewboard" in it.

Im getting the below error.

* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
Creating database ...
[!] Unable to execute the manager command syncdb: cannot import name
execute_manager
 
[!] Unable to execute the manager command registerscmtools: cannot
import name execute_manager
OK
Performing migrations ...
[!] Unable to execute the manager command evolve: cannot import name
execute_manager
OK
Creating administrator account ... Traceback (most recent call last):
  File "/usr/local/bin/rb-site", line 8, in 
load_entry_point('ReviewBoard==1.7.22', 'console_scripts', 'rb-site')()
  File 
"/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
 
line 2055, in main
command.run()
  File 
"/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
 
line 1496, in run
self.show_install_status()
  File 
"/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
 
line 1779, in show_install_status
site.create_admin_user)
  File 
"/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
 
line 967, in step
func()
  File 
"/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.py",
 
line 553, in create_admin_user
self.admin_password)
  File 
"/usr/local/lib64/python2.6/site-packages/django/contrib/auth/models.py", 
line 195, in create_superuser
   **extra_fields)
  File 
"/usr/local/lib64/python2.6/site-packages/django/contrib/auth/models.py", 
line 186, in _create_user
user.save(using=self._db)
  File "/usr/local/lib64/python2.6/site-packages/django/db/models/base.py", 
line 545, in save
force_update=force_update, update_fields=update_fields)
  File "/usr/local/lib64/python2.6/site-packages/django/db/models/base.py", 
line 573, in save_base
updated = self._save_table(raw, cls, force_insert, force_update, using, 
update_fields)
  File "/usr/local/lib64/python2.6/site-packages/django/db/models/base.py", 
line 654, in _save_table
result = self._do_insert(cls._base_manager, using, fields, update_pk, 
raw)
  File "/usr/local/lib64/python2.6/site-packages/django/db/models/base.py", 
line 687, in _do_insert
using=using, raw=raw)
  File 
"/usr/local/lib64/python2.6/site-packages/django/db/models/manager.py", 
line 232, in _insert
return insert_query(self.model, objs, fields, **kwargs)
  File 
"/usr/local/lib64/python2.6/site-packages/django/db/models/query.py", line 
1514, in insert_query
return query.get_compiler(using=using).execute_sql(return_id)
  File 
"/usr/local/lib64/python2.6/site-packages/django/db/models/sql/compiler.py", 
line 903, in execute_sql
cursor.execute(sql, params)
  File 
"/usr/local/lib64/python2.6/site-packages/django/db/backends/util.py", line 
53, in execute
return self.cursor.execute(sql, params)
  File "/usr/local/lib64/python2.6/site-packages/django/db/utils.py", line 
99, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
  File 
"/usr/local/lib64/python2.6/site-packages/django/db/backends/util.py", line 
53, in execute
return self.cursor.execute(sql, params)
  File 
"/usr/local/lib64/python2.6/site-packages/django/db/backends/mysql/base.py", 
line 124, in execute
return self.cursor.execute(query, args)
  File "/usr/lib64/python2.6/site-packages/MySQLdb/cursors.py", line 166, 
in execute
self.errorhandler(self, exc, value)
  File "/usr/lib64/python2.6/site-packages/MySQLdb/connections.py", line 
35, in defaulterrorhandler
raise errorclass, errorvalue
django.db.utils.ProgrammingError: (1146, "Table 'reviewboard.auth_user' 
doesn't exist")

Any pointers on what Im missing..

Best regards,  
Joe.

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Email All Reviewboard Users

[Joe]

Hello,

In our review board we have 200+ users. As a admin, I want to send an email 
to all these users. Is there any way to do it from within reviewboard.

We use RB 1.7.22

Best regards,  
Joe.

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bulk Upload of Users

[Joe]

Hello,

I have around 30 users who want to have an account created. Currently I see 
that I can do that via UI.

Wanted to know if there is any bulk user creation option from CSV file or 
something on those lines.

Best regards,  
Joe.

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: reviewboard search index

[Joe]

Ah!

it works with

# rb-site manage /var/www/reviewboard index

This rebuilds index.

# rb-site manage help

Doesnt show anything. Where to get the supported list of commands and their 
behaviour details?

Best regards,  
Joe.


On Thursday, April 24, 2014 11:22:43 AM UTC+2, Joe wrote:
>
> Hello,
>
> Im running reviewboard 1.7.22
>
> I have now installed pylucene and have enabled search. However, the search 
> doesnt return anything. So I tried to update or rebuild index as specified 
> in
>
>
> http://www.reviewboard.org/docs/manual/dev/admin/sites/management-commands/#search-indexing
>
> $ rb-site manage /path/to/site update_index
> $ rb-site manage /path/to/site rebuild_index
>
> But both return 
>
> # rb-site manage /var/www/reviewboard update_index
> Unknown command: 'update_index'
> Type 'rbsite.pyc help' for usage.
>
> # rb-site manage /var/www/reviewboard rebuild_index
> Unknown command: 'rebuild_index'
> Type 'rbsite.pyc help' for usage.
>
>
>
> Any pointers on how to build the search index.
>
> Best regards,  
> Joe.
>

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

reviewboard search index

[Joe]

Hello,

Im running reviewboard 1.7.22

I have now installed pylucene and have enabled search. However, the search 
doesnt return anything. So I tried to update or rebuild index as specified 
in

http://www.reviewboard.org/docs/manual/dev/admin/sites/management-commands/#search-indexing

$ rb-site manage /path/to/site update_index
$ rb-site manage /path/to/site rebuild_index

But both return 

# rb-site manage /var/www/reviewboard update_index
Unknown command: 'update_index'
Type 'rbsite.pyc help' for usage.

# rb-site manage /var/www/reviewboard rebuild_index
Unknown command: 'rebuild_index'
Type 'rbsite.pyc help' for usage.



Any pointers on how to build the search index.

Best regards,  
Joe.

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrating from sqlite3 to MySQL or PostgreSQL

[Joe]

Hi Christian,

It worked when I gave without the "--no-initial-data".

So following are the steps I followed:

I have assumed the /path/to/reviewboard in my case as /var/www/reviewboard

1. Stop reviewboard
2. # rb-site manage /var/www/reviewboard dumpdb > database.json
3. In reviewboard folder go into /conf and change the settings_local.py to 
point from sqlite3 to mysql

In settings_local.py change

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': '/var/www/reviewboard/data/reviewboard.db',
},
}

to

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'reviewboard_mysql',
'USER': 'root',
'PASSWORD': '',
'HOST': 'localhost',
'PORT': ''
},
}

4. # rb-site manage /var/www/reviewboard syncdb --
5. # rb-site manage /var/www/reviewboard loaddb 
/path/to/dumpfile/database.json

Done.



Best regards,  
Joe.

On Thursday, April 24, 2014 10:20:25 AM UTC+2, Joe wrote:
>
> Hi Christian,
>
> Thanks for the details. 
>
> When I run the below command I get the error --no-initial-data is not an 
> avaialble option. Am I missing something here:
>
>
> # rb-site manage /var/www/reviewboard syncdb -- --no-initial-data
> Usage: 
> /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.pyc
>  
> syncdb [options]
>
> Create the database tables for all apps in INSTALLED_APPS whose tables 
> haven't already been created.
>
> /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.pyc:
>  
> error: no such option: --no-initial-data
>
> Best regards,  
> Joe.
>
>
> On Tuesday, April 15, 2014 9:34:26 PM UTC+2, Christian Hammond wrote:
>>
>> loaddb and loaddata both require that you have an existing database 
>> schema in place.
>>
>> You'll need to first use the version of Review Board you were using for 
>> the sqlite database. I'm assuming in this case that it's the same one and 
>> that you aren't also trying trying to upgrade the software. If you are, 
>> you'll first need to update the sqlite database.
>>
>> Then, once you've configured your site to use MySQL (by modifying the 
>> settings_local.py file), you can create the initial schema by doing:
>>
>> $ rb-site manage /path/to/site syncdb -- --no-initial-data
>>
>> (Note the extra "--" in there.)
>>
>> If you already had data in the database, you'll need to wipe it before 
>> doing that.
>>
>> You should then be able to do the import.
>>
>> Christian
>>
>> -- 
>> Christian Hammond - chi...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> Beanbag, Inc. - http://www.beanbaginc.com
>>
>>
>> On Tue, Apr 15, 2014 at 5:08 AM, Joe  wrote:
>>
>>> Hello,
>>>
>>> Anyone who can say what could be the issue that I have mentioned below.
>>>
>>> Best regards,  
>>> Joe.
>>>
>>> On Monday, April 14, 2014 3:45:48 PM UTC+2, Joe wrote:
>>>>
>>>> David:
>>>>
>>>> When I tried this, I get the following errors:
>>>>
>>>> 1. rb-site manage /path/to/site dumpdb > database.json
>>>>
>>>> Success. Database.json was created
>>>>
>>>> 2. rb-site manage /path/to/site loaddb database.json
>>>>
>>>> Interestingly it said that database.json doesn't exist, while it exists.
>>>>
>>>> It started running when I gave the full path
>>>>
>>>> rb-site manage /path/to/site loaddb /home/rbusr/backup/database.json
>>>>
>>>> 3. But this loaddb command did not complete. It got failed with the 
>>>> following error:
>>>>
>>>> ine 2019: '{"pk": "2cb7881974e3b16dc27d181a7afad869", "model": 
>>>> "sessions.session", "fields": {"expire_date": "2015-03-19T05:43:49.644Z", 
>>>> "session_data": "gAJ9cQFVCnRlc3Rjb29raWVxAlUGd2
>>>> 9ya2VkcQNzLjViMGE0ODQwNDRhMjdjY2UyNDhjODgxYWIx\nZjlkZDky\n"}}
>>>> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't 
>>>> exist")
>>>> Line 2020: '{"pk": "57e2c5013b1a55003e2df355c6

Re: Migrating from sqlite3 to MySQL or PostgreSQL

[Joe]

Hi Christian,

Thanks for the details. 

When I run the below command I get the error --no-initial-data is not an 
avaialble option. Am I missing something here:


# rb-site manage /var/www/reviewboard syncdb -- --no-initial-data
Usage: 
/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.pyc
 
syncdb [options]

Create the database tables for all apps in INSTALLED_APPS whose tables 
haven't already been created.

/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/cmdline/rbsite.pyc:
 
error: no such option: --no-initial-data

Best regards,  
Joe.


On Tuesday, April 15, 2014 9:34:26 PM UTC+2, Christian Hammond wrote:
>
> loaddb and loaddata both require that you have an existing database schema 
> in place.
>
> You'll need to first use the version of Review Board you were using for 
> the sqlite database. I'm assuming in this case that it's the same one and 
> that you aren't also trying trying to upgrade the software. If you are, 
> you'll first need to update the sqlite database.
>
> Then, once you've configured your site to use MySQL (by modifying the 
> settings_local.py file), you can create the initial schema by doing:
>
> $ rb-site manage /path/to/site syncdb -- --no-initial-data
>
> (Note the extra "--" in there.)
>
> If you already had data in the database, you'll need to wipe it before 
> doing that.
>
> You should then be able to do the import.
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>
>
> On Tue, Apr 15, 2014 at 5:08 AM, Joe >wrote:
>
>> Hello,
>>
>> Anyone who can say what could be the issue that I have mentioned below.
>>
>> Best regards,  
>> Joe.
>>
>> On Monday, April 14, 2014 3:45:48 PM UTC+2, Joe wrote:
>>>
>>> David:
>>>
>>> When I tried this, I get the following errors:
>>>
>>> 1. rb-site manage /path/to/site dumpdb > database.json
>>>
>>> Success. Database.json was created
>>>
>>> 2. rb-site manage /path/to/site loaddb database.json
>>>
>>> Interestingly it said that database.json doesn't exist, while it exists.
>>>
>>> It started running when I gave the full path
>>>
>>> rb-site manage /path/to/site loaddb /home/rbusr/backup/database.json
>>>
>>> 3. But this loaddb command did not complete. It got failed with the 
>>> following error:
>>>
>>> ine 2019: '{"pk": "2cb7881974e3b16dc27d181a7afad869", "model": 
>>> "sessions.session", "fields": {"expire_date": "2015-03-19T05:43:49.644Z", 
>>> "session_data": "gAJ9cQFVCnRlc3Rjb29raWVxAlUGd2
>>> 9ya2VkcQNzLjViMGE0ODQwNDRhMjdjY2UyNDhjODgxYWIx\nZjlkZDky\n"}}
>>> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't 
>>> exist")
>>> Line 2020: '{"pk": "57e2c5013b1a55003e2df355c69bc722", "model": 
>>> "sessions.session", "fields": {"expire_date": "2015-03-19T06:25:37.154Z", 
>>> "session_data": "gAJ9cQEoVRJfYXV0aF91c2VyX2JhY2
>>> tlbmRxAlUpZGphbmdvLmNvbnRyaWIuYXV0aC5iYWNrZW5k\
>>> ncy5Nb2RlbEJhY2tlbmRxA1UNX2F1dGhfdXNlcl9pZHEES4t1LmNhYTJlZmF
>>> mMzM0YWY5NDY1ZjAx\nNjM3ZjA3NTA1M2Rl\n"}}
>>> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't 
>>> exist")
>>> Line 2021: '{"pk": "f5039c679f6f5d0fcd4e1ce45375d2c9", "model": 
>>> "sessions.session", "fields": {"expire_date": "2015-04-01T05:35:47.003Z", 
>>> "session_data": "gAJ9cQEoVRJfYXV0aF91c2VyX2JhY2
>>> tlbmRxAlUpZGphbmdvLmNvbnRyaWIuYXV0aC5iYWNrZW5k\
>>> ncy5Nb2RlbEJhY2tlbmRxA1UNX2F1dGhfdXNlcl9pZHEES2R1LjA3ODVlNzk
>>> 1YzNkYmExMmJmY2Fm\nMTNmMmMzODI0MmFh\n"}}
>>> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't 
>>> exist")
>>> Line 2022: '{"pk": "b9da809d942c8ab930c14843aabd5d9b", "model": 
>>> "sessions.session", "fields": {"expire_date": "2015-03-20T22:06:59.624Z", 
>>> "session_data": "gAJ9cQEoVQ1fYXV0aF91c2VyX2lkcQ
>>> JLKFUSX2F1dGhfdXNlcl9iYWNrZW5kcQNVKWRqYW5nby5j\
>>> nb250cmliLmF1dGguYmFja2

Re: Migrating from sqlite3 to MySQL or PostgreSQL

[Joe]

Hello,

Anyone who can say what could be the issue that I have mentioned below.

Best regards,  
Joe.

On Monday, April 14, 2014 3:45:48 PM UTC+2, Joe wrote:
>
> David:
>
> When I tried this, I get the following errors:
>
> 1. rb-site manage /path/to/site dumpdb > database.json
>
> Success. Database.json was created
>
> 2. rb-site manage /path/to/site loaddb database.json
>
> Interestingly it said that database.json doesn't exist, while it exists.
>
> It started running when I gave the full path
>
> rb-site manage /path/to/site loaddb /home/rbusr/backup/database.json
>
> 3. But this loaddb command did not complete. It got failed with the 
> following error:
>
> ine 2019: '{"pk": "2cb7881974e3b16dc27d181a7afad869", "model": 
> "sessions.session", "fields": {"expire_date": "2015-03-19T05:43:49.644Z", 
> "session_data": 
> "gAJ9cQFVCnRlc3Rjb29raWVxAlUGd29ya2VkcQNzLjViMGE0ODQwNDRhMjdjY2UyNDhjODgxYWIx\nZjlkZDky\n"}}
> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
> Line 2020: '{"pk": "57e2c5013b1a55003e2df355c69bc722", "model": 
> "sessions.session", "fields": {"expire_date": "2015-03-19T06:25:37.154Z", 
> "session_data": 
> "gAJ9cQEoVRJfYXV0aF91c2VyX2JhY2tlbmRxAlUpZGphbmdvLmNvbnRyaWIuYXV0aC5iYWNrZW5k\ncy5Nb2RlbEJhY2tlbmRxA1UNX2F1dGhfdXNlcl9pZHEES4t1LmNhYTJlZmFmMzM0YWY5NDY1ZjAx\nNjM3ZjA3NTA1M2Rl\n"}}
> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
> Line 2021: '{"pk": "f5039c679f6f5d0fcd4e1ce45375d2c9", "model": 
> "sessions.session", "fields": {"expire_date": "2015-04-01T05:35:47.003Z", 
> "session_data": 
> "gAJ9cQEoVRJfYXV0aF91c2VyX2JhY2tlbmRxAlUpZGphbmdvLmNvbnRyaWIuYXV0aC5iYWNrZW5k\ncy5Nb2RlbEJhY2tlbmRxA1UNX2F1dGhfdXNlcl9pZHEES2R1LjA3ODVlNzk1YzNkYmExMmJmY2Fm\nMTNmMmMzODI0MmFh\n"}}
> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
> Line 2022: '{"pk": "b9da809d942c8ab930c14843aabd5d9b", "model": 
> "sessions.session", "fields": {"expire_date": "2015-03-20T22:06:59.624Z", 
> "session_data": 
> "gAJ9cQEoVQ1fYXV0aF91c2VyX2lkcQJLKFUSX2F1dGhfdXNlcl9iYWNrZW5kcQNVKWRqYW5nby5j\nb250cmliLmF1dGguYmFja2VuZHMuTW9kZWxCYWNrZW5kcQR1LjIzNzk5MzQwY2ZhODUwMWNmMzU5\nMWY4MWUyNmY5YjIx\n"}}
> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
> Line 2023: '{"pk": "ba719abc8094a9bc8cc3b677cbc3db1d", "model": 
> "sessions.session", "fields": {"expire_date": "2015-03-20T00:34:54.056Z", 
> "session_data": 
> "gAJ9cQEoVRJfYXV0aF91c2VyX2JhY2tlbmRxAlUpZGphbmdvLmNvbnRyaWIuYXV0aC5iYWNrZW5k\ncy5Nb2RlbEJhY2tlbmRxA1UNX2F1dGhfdXNlcl9pZHEES311LjZmZWI3MGM5NzUyNTIxOGM2OTk1\nNjg1NGQyOTE5NDc1\n"}}
> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
> Line 2024: '{"pk": "b7ef1ec805fba7b77c567fe403ffcc80", "model": 
> "sessions.session", "fields": {"expire_date": "2015-03-20T00:36:22.807Z", 
> "session_data": 
> "gAJ9cQFVCnRlc3Rjb29raWVxAlUGd29ya2VkcQNzLjViMGE0ODQwNDRhMjdjY2UyNDhjODgxYWIx\nZjlkZDky\n"}}
> 'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
> Line 2025: '{"pk": "4eefe47bedaa52c81faaf65f3fec65e7", "model": 
> "sessions.session", "fields": {"expire_date": "2015-03-20T00:37:22.556Z", 
> "session_data": 
> "gAJ9cQFVCnRlc3Rjb29raWVxAlUGd29ya2VkcQNzLjViMGE0ODQwNDRhMjdjY2UyNDhjODgxYWIx\nZjlkZDky\n"}}
> Line 2166: '{"pk": "0fb6592d2c2784aafd9fa256f522dd52", "model": 
> "sessions.session", "fields": {"expire_date": "2015-04-14T10:18:01.105Z", 
> "session_data": 
> "MTgzOTdhYTQzYzIzMWUyNTJhOTcwYzk3ODQwNTE0MDFjN2JhNzYxYjqAAn1xAShVEl9hdXRoX3Vz\nZXJfYmFja2VuZHECVTFyZXZpZXdib2FyZC5hY2NvdW50cy5iYWNrZW5kcy5TdGFuZGFyZEF1dGhC\nYWNrZW5kcQNVDV9hdXRoX3VzZXJfaWRxBEsQdS4=\n"}}
>
> 'Problem installing '/home/rbusr/reviewboard/database.json': (1146, "Table 
> 'reviewboard_mysqldb.django_site' doesn't exist")
>
>
>
>
>
> Any though

Re: Migrating from sqlite3 to MySQL or PostgreSQL

[Joe]

David:

When I tried this, I get the following errors:

1. rb-site manage /path/to/site dumpdb > database.json

Success. Database.json was created

2. rb-site manage /path/to/site loaddb database.json

Interestingly it said that database.json doesn't exist, while it exists.

It started running when I gave the full path

rb-site manage /path/to/site loaddb /home/rbusr/backup/database.json

3. But this loaddb command did not complete. It got failed with the 
following error:

ine 2019: '{"pk": "2cb7881974e3b16dc27d181a7afad869", "model": 
"sessions.session", "fields": {"expire_date": "2015-03-19T05:43:49.644Z", 
"session_data": 
"gAJ9cQFVCnRlc3Rjb29raWVxAlUGd29ya2VkcQNzLjViMGE0ODQwNDRhMjdjY2UyNDhjODgxYWIx\nZjlkZDky\n"}}
'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
Line 2020: '{"pk": "57e2c5013b1a55003e2df355c69bc722", "model": 
"sessions.session", "fields": {"expire_date": "2015-03-19T06:25:37.154Z", 
"session_data": 
"gAJ9cQEoVRJfYXV0aF91c2VyX2JhY2tlbmRxAlUpZGphbmdvLmNvbnRyaWIuYXV0aC5iYWNrZW5k\ncy5Nb2RlbEJhY2tlbmRxA1UNX2F1dGhfdXNlcl9pZHEES4t1LmNhYTJlZmFmMzM0YWY5NDY1ZjAx\nNjM3ZjA3NTA1M2Rl\n"}}
'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
Line 2021: '{"pk": "f5039c679f6f5d0fcd4e1ce45375d2c9", "model": 
"sessions.session", "fields": {"expire_date": "2015-04-01T05:35:47.003Z", 
"session_data": 
"gAJ9cQEoVRJfYXV0aF91c2VyX2JhY2tlbmRxAlUpZGphbmdvLmNvbnRyaWIuYXV0aC5iYWNrZW5k\ncy5Nb2RlbEJhY2tlbmRxA1UNX2F1dGhfdXNlcl9pZHEES2R1LjA3ODVlNzk1YzNkYmExMmJmY2Fm\nMTNmMmMzODI0MmFh\n"}}
'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
Line 2022: '{"pk": "b9da809d942c8ab930c14843aabd5d9b", "model": 
"sessions.session", "fields": {"expire_date": "2015-03-20T22:06:59.624Z", 
"session_data": 
"gAJ9cQEoVQ1fYXV0aF91c2VyX2lkcQJLKFUSX2F1dGhfdXNlcl9iYWNrZW5kcQNVKWRqYW5nby5j\nb250cmliLmF1dGguYmFja2VuZHMuTW9kZWxCYWNrZW5kcQR1LjIzNzk5MzQwY2ZhODUwMWNmMzU5\nMWY4MWUyNmY5YjIx\n"}}
'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
Line 2023: '{"pk": "ba719abc8094a9bc8cc3b677cbc3db1d", "model": 
"sessions.session", "fields": {"expire_date": "2015-03-20T00:34:54.056Z", 
"session_data": 
"gAJ9cQEoVRJfYXV0aF91c2VyX2JhY2tlbmRxAlUpZGphbmdvLmNvbnRyaWIuYXV0aC5iYWNrZW5k\ncy5Nb2RlbEJhY2tlbmRxA1UNX2F1dGhfdXNlcl9pZHEES311LjZmZWI3MGM5NzUyNTIxOGM2OTk1\nNjg1NGQyOTE5NDc1\n"}}
'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
Line 2024: '{"pk": "b7ef1ec805fba7b77c567fe403ffcc80", "model": 
"sessions.session", "fields": {"expire_date": "2015-03-20T00:36:22.807Z", 
"session_data": 
"gAJ9cQFVCnRlc3Rjb29raWVxAlUGd29ya2VkcQNzLjViMGE0ODQwNDRhMjdjY2UyNDhjODgxYWIx\nZjlkZDky\n"}}
'Error: (1146, "Table 'reviewboard_mysqldb.django_session' doesn't exist")
Line 2025: '{"pk": "4eefe47bedaa52c81faaf65f3fec65e7", "model": 
"sessions.session", "fields": {"expire_date": "2015-03-20T00:37:22.556Z", 
"session_data": 
"gAJ9cQFVCnRlc3Rjb29raWVxAlUGd29ya2VkcQNzLjViMGE0ODQwNDRhMjdjY2UyNDhjODgxYWIx\nZjlkZDky\n"}}
Line 2166: '{"pk": "0fb6592d2c2784aafd9fa256f522dd52", "model": 
"sessions.session", "fields": {"expire_date": "2015-04-14T10:18:01.105Z", 
"session_data": 
"MTgzOTdhYTQzYzIzMWUyNTJhOTcwYzk3ODQwNTE0MDFjN2JhNzYxYjqAAn1xAShVEl9hdXRoX3Vz\nZXJfYmFja2VuZHECVTFyZXZpZXdib2FyZC5hY2NvdW50cy5iYWNrZW5kcy5TdGFuZGFyZEF1dGhC\nYWNrZW5kcQNVDV9hdXRoX3VzZXJfaWRxBEsQdS4=\n"}}

'Problem installing '/home/rbusr/reviewboard/database.json': (1146, "Table 
'reviewboard_mysqldb.django_site' doesn't exist")





Any thoughts on how to fix this..

Best regards,  
Joe.



On Saturday, April 12, 2014 8:29:54 AM UTC+2, David Trowbridge wrote:
>
> Joe,
>
> There are two management commands you can use for this. They aren't 
> well-documented, but there's an example of how to use them at 
> http://www.reviewboard.org/docs/releasenotes/reviewboard/1.6.4/
>
> I don't think there's a strong reason to choose either over the other. It 
> usually comes down more

Migrating from sqlite3 to MySQL or PostgreSQL

[Joe]

Hello,

I believe I'm still running my review board in sqlite3 (how to confirm it)

Are there any scripts from review board to convert this database to MySQL 
or PostgreSQL.

Also which one (MySQL or PostgreSQL) is better option.

Best regards,  
Joe.

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Post just the diff

[Joe]

Hi Matthew,

Yes, it would be good if rbt has an option to specify the repository so 
that one can directly post. 

The reason here is, in our development tree we have a packaging 
architecture and the diff generated by another tool. So we don't have the 
repo details with us.

Best regards,  
Joe.

On Wednesday, April 9, 2014 9:57:41 PM UTC+2, Matthew Woehlke wrote:
>
> On 2014-04-09 11:39, Joe wrote: 
> > I would want to post a diff directly from the command line. When I use 
> the 
> > `rbt post --diff-filename` option, it still searches for the repository 
> in 
> > the current directory. 
> > 
> > I don't want that. I want to just post a diff from command line without 
> it 
> > checking for any repository in the current location. Is that possible? 
>
> ...no? RB needs to know what repo the diff is for. 
>
> Would you want to add an option to rbt post to specify a repository? 
>
> -- 
> Matthew 
>

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

OperationalError: database is locked

[Joe]

Hello,

We periodically get this lock error. Im running review board 1.7.22. 

Best regards,  
Joe.

--

Traceback (most recent call last):

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/core/handlers/base.py",
 
line 111, in get_response
response = callback(request, *callback_args, **callback_kwargs)

  File 
"/usr/local/lib/python2.6/dist-packages/Djblets-0.7.28-py2.6.egg/djblets/auth/util.py",
 
line 47, in _checklogin
return view_func(request, *args, **kwargs)

  File 
"/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/site/decorators.py",
 
line 35, in _check
return view_func(request, local_site=local_site, *args, **kwargs)

  File 
"/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/accounts/decorators.py",
 
line 53, in _check_valid_prefs
return view_func(request, *args, **kwargs)

  File 
"/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/reviews/views.py",
 
line 828, in dashboard
'sidebar_counts': get_sidebar_counts(request.user, local_site),

  File 
"/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/reviews/datagrids.py",
 
line 803, in get_sidebar_counts
profile=profile)

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/fields/related.py",
 
line 493, in get_or_create
return super(RelatedManager, 
self.db_manager(db)).get_or_create(**kwargs)

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/manager.py",
 
line 134, in get_or_create
return self.get_query_set().get_or_create(**kwargs)

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/query.py",
 
line 452, in get_or_create
obj.save(force_insert=True, using=self.db)

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/base.py",
 
line 463, in save
self.save_base(using=using, force_insert=force_insert, 
force_update=force_update)

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/base.py",
 
line 555, in save_base
transaction.commit_unless_managed(using=using)

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/transaction.py",
 
line 135, in commit_unless_managed
connection.commit_unless_managed()

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/backends/__init__.py",
 
line 214, in commit_unless_managed
self._commit()

  File 
"/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/backends/__init__.py",
 
line 50, in _commit
return self.connection.commit()

OperationalError: database is locked


,
POST:,
COOKIES:{'collapsediffs': 'True',
 'csrftoken': '5a764b26f0910188c3e86cf96567dea7',
 'rbsessionid': '6880c2e09e0002d305c304b9282eb587'},
META:{'AUTH_TYPE': None,
 'CONTENT_LENGTH': 0,
 'CONTENT_TYPE': None,
 'GATEWAY_INTERFACE': 'CGI/1.1',
 'HTTP_ACCEPT': 
'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
 'HTTP_ACCEPT_ENCODING': 'gzip, deflate',
 'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.5',
 'HTTP_CONNECTION': 'keep-alive',
 'HTTP_COOKIE': 'rbsessionid=6880c2e09e0002d305c304b9282eb587; 
csrftoken=5a764b26f0910188c3e86cf96567dea7; collapsediffs=True',
 'HTTP_HOST': 'daytona',
 'HTTP_REFERER': 
'http://daytona/reviews/account/preferences/<https://webmail.ami.com/owa/redir.aspx?C=8b9d44d8594b4f51aa1d9d122ac19ddc&URL=http%3a%2f%2fdaytona%2freviews%2faccount%2fpreferences%2f>
',
 'HTTP_USER_AGENT': 'Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) 
Gecko/20100101 Firefox/23.0',
 'PATH_INFO': u'/reviews/dashboard/',
 'PATH_TRANSLATED': None,
 'QUERY_STRING': None,
 'REMOTE_ADDR': '172.16.56.188',
 'REMOTE_HOST': None,
 'REMOTE_IDENT': None,
 'REMOTE_USER': None,
 'REQUEST_METHOD': 'GET',
 'SCRIPT_NAME': '',
 'SERVER_NAME': 'daytona.us.megatrends.com',
 'SERVER_PORT': 80,
 'SERVER_PROTOCOL': 'HTTP/1.1',
 'SERVER_SOFTWARE': 'mod_python'}>

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Post just the diff

[Joe]

Hello,

I see that post-review has been deprecated.

I would want to post a diff directly from the command line. When I use the 
`rbt post --diff-filename` option, it still searches for the repository in 
the current directory. 

I don't want that. I want to just post a diff from command line without it 
checking for any repository in the current location. Is that possible?

Best regards,  
Joe.

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Users are automatically created if authenticated through ldap

[Joe Reyna]

Hi Eric, can you post your modified custom authenticator?

On Wednesday, March 23, 2011 1:02:10 PM UTC-7, Eric Johnson wrote:
>
> I achieved your aim for our local copy of ReviewBoard by snagging the 
> existing LDAP code, and modifying it slightly. I then used the modified 
> code as a custom authenticator.
>
> That way, unauthorized people- not in the reviewboard DB - don't get 
> authenticated.
>
> Eric
>
> On Mar 23, 2011, at 8:29 AM, Pablo G > 
> wrote:
>
> Hi guys.
>
> I have a RB installation validating against an LDAP server. It looks like 
> RB creates users in the local database whenever a user is correctly 
> authenticated with LDAP. What I need is a way to disable this automatic 
> user creation, so the site admin can decide which users in the full LDAP 
> repository can access the RB. Is this possible? I am on RB 1.5.2.
>
> thanks a lot.
>
>  -- 
> 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...@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
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Static media still broken in 1.7 after updating Apache configuration

[Joe Attardi]

Adding a  section fixed the problem!
Thanks, Christian! 

On Tuesday, December 18, 2012 1:02:53 AM UTC-5, Christian Hammond wrote:
>
> Hi Joe,
>
> Sorry for the late response. Looks like gmail flagged this as spam. Odd.
>
> You may need to add a  that works just like the media 
> one. The static files are probably going through Review Board, which won't 
> know how to serve them.
>
> As for the "Couldn't find manual update check" error, we just have a bug 
> where a second resolve-check prints that. I assume it worked the first time.
>
> If the  doesn't fix things, we'll do some debugging with your 
> setup and see what we can find.
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
>
> On Mon, Dec 17, 2012 at 8:15 PM, Joe Attardi 
> > wrote:
>
>> I updated my site to 1.7.0.1-py2.7 and I'm still getting 404 errors for 
>> anything under /static
>>
>> I added the alias for /static and restarted Apache 2, but it seems to 
>> have no effect. Am I missing something obvious?
>>
>> My Apache 2 configuration:
>>
>> 
>> ServerName uxworks-reviewboard.mysite.com
>> DocumentRoot "/var/www/uxworks-reviewboard/htdocs"
>>
>> # Error handlers
>> ErrorDocument 500 /errordocs/500.html
>>
>> # Serve django pages
>> 
>> PythonPath "['/var/www/uxworks-reviewboard/conf'] + 
>> sys.path"
>> SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings
>> SetEnv PYTHON_EGG_CACHE 
>> "/var/www/uxworks-reviewboard/tmp/egg_cache"
>> SetEnv HOME "/var/www/uxworks-reviewboard/data"
>> SetHandler mod_python
>> PythonHandler django.core.handlers.modpython
>> PythonAutoReload Off
>> PythonDebug Off
>> # Used to run multiple mod_python sites in the same apache
>> PythonInterpreter reviewboard_uxworks-reviewboard
>> 
>>
>> # Serve static media without running it through mod_python
>> # (overrides the above)
>> 
>> SetHandler None
>> 
>> 
>> SetHandler None
>> 
>>
>> 
>> AllowOverride All
>> 
>>
>> # Alias static media requests to filesystem
>> Alias /media "/var/www/uxworks-reviewboard/htdocs/media"
>> Alias /errordocs "/var/www/uxworks-reviewboard/htdocs/erordocs"
>> Alias /static "/var/www/uxworks-reviewboard/htdocs/static"
>> 
>>
>> I tried running rb-site manage /var/www/uxworks-reviewboard 
>> resolve-check static-media but it gave me an error: Couldn't find manual 
>> update check 'static-media'
>>
>> Any help would be appreciated. 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...@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

Static media still broken in 1.7 after updating Apache configuration

[Joe Attardi]

I updated my site to 1.7.0.1-py2.7 and I'm still getting 404 errors for 
anything under /static

I added the alias for /static and restarted Apache 2, but it seems to have 
no effect. Am I missing something obvious?

My Apache 2 configuration:


ServerName uxworks-reviewboard.mysite.com
DocumentRoot "/var/www/uxworks-reviewboard/htdocs"

# Error handlers
ErrorDocument 500 /errordocs/500.html

# Serve django pages

PythonPath "['/var/www/uxworks-reviewboard/conf'] + 
sys.path"
SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings
SetEnv PYTHON_EGG_CACHE 
"/var/www/uxworks-reviewboard/tmp/egg_cache"
SetEnv HOME "/var/www/uxworks-reviewboard/data"
SetHandler mod_python
PythonHandler django.core.handlers.modpython
PythonAutoReload Off
PythonDebug Off
# Used to run multiple mod_python sites in the same apache
PythonInterpreter reviewboard_uxworks-reviewboard


# Serve static media without running it through mod_python
# (overrides the above)

SetHandler None


SetHandler None



AllowOverride All


# Alias static media requests to filesystem
Alias /media "/var/www/uxworks-reviewboard/htdocs/media"
Alias /errordocs "/var/www/uxworks-reviewboard/htdocs/erordocs"
Alias /static "/var/www/uxworks-reviewboard/htdocs/static"


I tried running rb-site manage /var/www/uxworks-reviewboard resolve-check 
static-media but it gave me an error: Couldn't find manual update check 
'static-media'

Any help would be appreciated. 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: Can't post reviews w/ git after upgrade 1.63 -> 1.6.12

[Joe]

Christian,

Thanks for clearing up the mystery. 

We went back to the v2 api whose raw URLs look like:
/api/v2/yaml/blob/show/cm/ultrasound/?login=...&token=...
As near as I can tell, the equivalent v3 url would be
/api/v3/repos/cm/ultrasound/git/blobs/?access_token=...
but the default content type returns a json wrapper around the file content 
base64-encoding. The only way I could see to change the content type was by 
setting the accepted content type header. Since you've done the real GitHub 
integration perhaps you know of another way?

In any event, we're good for the time being -- no need to get this working 
for us.

And thanks, for ReviewBoard -- it's great.

Joe

-- 
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: Can't post reviews w/ git after upgrade 1.63 -> 1.6.12

[Joe]

Christian,

Actually I'm sure going back to the old raw-file URL will work -- we did 
some tests -- but like the GitHub service, the latest version of the 
self-hosted GitHub also drops the v2 api and requires the username/password 
pair.

The part that confuses me, is that a simple diff works, but a more 
complicated diff doesn't. What's different?

The longer diff causes the post-review or the review board API to loose 
track of the git repository -- the debug output for the simple diff is 
quite happy and knows what the repository is, but the debug from the 
complex diff says ">>> Error data: {u'fields': {u'path': [u"fatal: Not a 
git repository: 'None'\n"]}, u'stat': u'fail', u'err': {u'msg': u'One or 
more fields had errors', u'code': 105}}" and this is confirmed in the 
review server logs:
2012-10-05 08:54:11,419 - ERROR - Error uploading new diff: fatal: Not a 
git repository: 'None'
Traceback (most recent call last):
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-1.6.12-py2.6.egg/reviewboard/webapi/resources.py",
 
line 1509, in create
request.FILES.get('parent_diff_path'))
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-1.6.12-py2.6.egg/reviewboard/reviews/forms.py",
 
line 296, in create
history)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-1.6.12-py2.6.egg/reviewboard/diffviewer/forms.py",
 
line 84, in create
diff_file, basedir, check_existance=(not parent_diff_file)))
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-1.6.12-py2.6.egg/reviewboard/diffviewer/forms.py",
 
line 170, in _process_files
not self.repository.get_file_exists(filename, revision))):
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-1.6.12-py2.6.egg/reviewboard/scmtools/models.py",
 
line 169, in get_file_exists
return self.get_scmtool().file_exists(path, revision)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-1.6.12-py2.6.egg/reviewboard/scmtools/git.py",
 
line 82, in file_exists
return self.client.get_file_exists(path, revision)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-1.6.12-py2.6.egg/reviewboard/scmtools/git.py",
 
line 398, in get_file_exists
contents = self._cat_file(path, revision, "-t")
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-1.6.12-py2.6.egg/reviewboard/scmtools/git.py",
 
line 440, in _cat_file
raise SCMError(errmsg)
SCMError: fatal: Not a git repository: 'None'




On Friday, October 5, 2012 1:15:14 PM UTC-7, Christian Hammond wrote:
>
> Hi Joe,
>
> GitHub itself moved to requiring the new API several months back, and for 
> that, we had to introduce deeper hosting service support. In order to talk 
> to github.com, Hosting Service must be set to GitHub.
>
> Now, for a self-hosted GitHub instance, I imagine the old API still 
> exists. In that case, you'll have to keep the raw file URL field, as that's 
> how Review Board fetched files and checked for file existence with the old 
> API. Bringing that back may solve your problem.
>
> We have a contribution we'll be incorporating (once it's ready) for 
> Hosting Service support for self-hosted GitHub instances. We'll release 
> that when it's ready. It should then be a bit easier to get going with the 
> new API.
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Fri, Oct 5, 2012 at 8:59 AM, Joe >wrote:
>
>> Hi,
>>
>> We upgraded to 1.6.12 from 1.6.3 yesterday. We're using an internal 
>> github as our master repository, and have about 20 repositories defined in 
>> reviewboard. The hosting service is set to None, the type to git, the paths 
>> look
>> like g...@github.corp.ad.local:cm/transform.git. For the upgrade we 
>> deleted the raw file URL mask and added a username & password (that is we 
>> wanted to move to the new git hub api). Everything seemed to work, we could 
>> add a small test file and post the review for the repositories, but then we 
>> discovered it wouldn't work for read diffs. We've fiddled with everything 
>> we could think of to no avail -- any help would be appreciated.  Here's an 
>> example of review that worked (with a failing post below):
>>
>> $ post-review --debug
>> >>> RBTools 0.4.2
>> >>> Python 2.6.6 (r266:84292, Dec  7 2011, 20:38:36) 
>> [GCC 4.4.6 20110731 (Red Hat 4.4.6-3)]
>> >>> Running on Linux-2.6.32-220.13.1.el6.i686-i686-with-centos-6.2-Final
>> >>> Home = /home/CORP/jf

Can't post reviews w/ git after upgrade 1.63 -> 1.6.12

[Joe]

Hi,

We upgraded to 1.6.12 from 1.6.3 yesterday. We're using an internal github 
as our master repository, and have about 20 repositories defined in 
reviewboard. The hosting service is set to None, the type to git, the paths 
look
like g...@github.corp.ad.local:cm/transform.git. For the upgrade we deleted 
the raw file URL mask and added a username & password (that is we wanted to 
move to the new git hub api). Everything seemed to work, we could add a 
small test file and post the review for the repositories, but then we 
discovered it wouldn't work for read diffs. We've fiddled with everything 
we could think of to no avail -- any help would be appreciated.  Here's an 
example of review that worked (with a failing post below):

$ post-review --debug
>>> RBTools 0.4.2
>>> Python 2.6.6 (r266:84292, Dec  7 2011, 20:38:36) 
[GCC 4.4.6 20110731 (Red Hat 4.4.6-3)]
>>> Running on Linux-2.6.32-220.13.1.el6.i686-i686-with-centos-6.2-Final
>>> Home = /home/CORP/jfrisbie
>>> Current Directory = /home/CORP/jfrisbie/projects/transform
>>> Checking the repository type. Errors shown below are mostly harmless.
DEBUG:root:Checking for a CVS repository...
DEBUG:root:Checking for a ClearCase repository...
DEBUG:root:Checking for a Git repository...
DEBUG:root:Running: git rev-parse --git-dir
DEBUG:root:Running: git config core.bare
DEBUG:root:Running: git rev-parse --show-toplevel
DEBUG:root:Running: git symbolic-ref -q HEAD
DEBUG:root:Running: git config --get branch.master.merge
DEBUG:root:Running: git config --get branch.master.remote
DEBUG:root:Running: git config --get remote.origin.url
DEBUG:root:repository info: Path: 
g...@github.corp.ad.local:cm/transform.git, Base path: , Supports 
changesets: False
>>> Finished checking the repository type.
DEBUG:root:Running: git config --get reviewboard.url
>>> HTTP GETting api/
>>> HTTP GETting https://reviewboard.corp.ad.local/api/info/
>>> Using the new web API
DEBUG:root:Running: git merge-base origin/master refs/heads/master
DEBUG:root:Running: git diff --no-color --full-index --no-ext-diff 
--ignore-submodules 
08d87f9f8aa11cf60d2f6419fb9fe43d4d336967..refs/heads/master
DEBUG:root:Running: git log --pretty=format:%s HEAD^..
DEBUG:root:Running: git log --pretty=format:%s%n%n%b 
08d87f9f8aa11cf60d2f6419fb9fe43d4d336967..
>>> Attempting to create review request on 
g...@github.corp.ad.local:cm/transform.git for None
>>> HTTP POSTing to https://reviewboard.corp.ad.local/api/review-requests/: 
{'repository': 'g...@github.corp.ad.local:cm/transform.git'}
>>> Review request created
>>> Attempting to set field 'target_groups' to 'PDDev' for review request 
'405'
>>> HTTP PUTting to 
https://reviewboard.corp.ad.local/api/review-requests/405/draft/: 
{'target_groups': 'PDDev'}
>>> Attempting to set field 'summary' to 'With Master' for review request 
'405'
>>> HTTP PUTting to 
https://reviewboard.corp.ad.local/api/review-requests/405/draft/: 
{'summary': 'With Master'}
>>> Attempting to set field 'description' to 'With Master' for review 
request '405'
>>> HTTP PUTting to 
https://reviewboard.corp.ad.local/api/review-requests/405/draft/: 
{'description': 'With Master'}
>>> Uploading diff, size: 205
>>> HTTP POSTing to 
https://reviewboard.corp.ad.local/api/review-requests/405/diffs/: {}
Review request #405 posted.

https://reviewboard.corp.ad.local/r/405/

$ post-review --output-diff
diff --git a/Master.txt b/Master.txt
new file mode 100644
index 
..1796c7667d90e91a02868ea565c3b6aedea5e335
--- /dev/null
+++ b/Master.txt
@@ -0,0 +1 @@
+Yes, Master


Here's an example of a review that fails -- same local git, different 
branch checked out with a real change (both branches have one diff on top 
of what's at the tip of the master repo:

$ post-review --debug
>>> RBTools 0.4.2
>>> Python 2.6.6 (r266:84292, Dec  7 2011, 20:38:36) 
[GCC 4.4.6 20110731 (Red Hat 4.4.6-3)]
>>> Running on Linux-2.6.32-220.13.1.el6.i686-i686-with-centos-6.2-Final
>>> Home = /home/CORP/jfrisbie
>>> Current Directory = /home/CORP/jfrisbie/projects/transform
>>> Checking the repository type. Errors shown below are mostly harmless.
DEBUG:root:Checking for a CVS repository...
DEBUG:root:Checking for a ClearCase repository...
DEBUG:root:Checking for a Git repository...
DEBUG:root:Running: git rev-parse --git-dir
DEBUG:root:Running: git config core.bare
DEBUG:root:Running: git rev-parse --show-toplevel
DEBUG:root:Running: git symbolic-ref -q HEAD
DEBUG:root:Running: git config --get branch.working.merge
DEBUG:root:Running: git config --get branch.working.remote
DEBUG:root:Running: git config --get remote.origin.url
DEBUG:root:repository info: Path: 
g...@github.corp.ad.local:cm/transform.git, Base path: , Supports 
changesets: False
>>> Finished checking the repository type.
DEBUG:root:Running: git config --get reviewboard.url
>>> HTTP GETting api/
>>> HTTP GETting https://reviewboard.corp.ad.local/api/info/
>>> Using the new web API
DEBUG:root:Running: git merge-base origin/

Re: Intermittent SCMError

[Joe Mou]

On Tue, Oct 18, 2011 at 11:55 AM, Christian Hammond wrote:

> Hi Joe,
>
> For the git configuration, are you using a clone that Review Board can
> access, or the raw URL configuration?
>
I'm not sure I understand entirely, but the git repository is on the local
filesystem of the ReviewBoard host. The path is set
to: /home/public/burnttoast.git


> I assume you weren't running Python 2.7 before?

I'm pretty sure that before the upgrade, the default interpreter was 2.7.1.
Python 2.6.6 was also installed, but I think it was not default. After the
upgrade, I am running 2.7.2.


> If that's new, and you're using the raw URL access, it may be possible
> you're hitting some regressions in their urllib2 support (we recently found
> other issues there). That's just an initial guess though. We'd need more
> information to figure it out.
>
> 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

Intermittent SCMError

[Joe Mou]

Hi, I have intermittent failures from ReviewBoard. These failures pop up in
various interactions (reading reviews, post-review, publishing comments),
but all seem to be related to accessing my git repository. From what I've
gathered while researching this, it's usually a fatal condition (e.g., the
repository has the wrong permissions). Not only have I double checked the
permissions, but the weird part is that retrying the action or refreshing
the web page usually works fine. Roughly 1 out of 10 actions result in an
error though.

Last week, everything was working fine. The onset of the errors coincides
with an update of the hosting machine from Ubuntu 10.04 to 10.10. So
obviously a lot has changed that could be contributing to the error, but I
can't narrow it down.

Does anyone have any ideas on what might be wrong, or how I might diagnose
this?

Below is an error e-mail that ReviewBoard sent.

Thanks,
Joe



[Review Board] ERROR (EXTERNAL IP): Internal Server Error: /r/52/

Traceback (most recent call last):

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/django/core/handlers/base.py",
line 111, in get_response
   response = callback(request, *callback_args, **callback_kwargs)

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/reviewboard/accounts/decorators.py",
line 21, in _check
   return view_func(*args, **kwargs)

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/reviewboard/reviews/views.py",
line 461, in review_detail
   'PRE_CREATION': PRE_CREATION,

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/reviewboard/reviews/views.py",
line 109, in _make_review_request_context
   upload_diff_form = UploadDiffForm(review_request)

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/reviewboard/reviews/forms.py",
line 266, in __init__
   data, *args, **kwargs)

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/reviewboard/diffviewer/forms.py",
line 44, in __init__
   if self.repository.get_scmtool().get_diffs_use_absolute_paths():

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/reviewboard/scmtools/models.py",
line 122, in get_scmtool
   return cls(self)

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/reviewboard/scmtools/git.py",
line 70, in __init__
   local_site_name)

 File
"/home/jmou/src/reviewboard/lib/python2.7/site-packages/reviewboard/scmtools/git.py",
line 316, in __init__
   raise SCMError(_('Unable to retrieve information from '

SCMError: 


,
POST:,
COOKIES:{'collapsediffs': 'True',
 'csrftoken': '580b2766fe12c70c23a58cca755a00f5',
 'rbsessionid': '940bf1a27bf8477126b7a90e7e0c4293'},
META:{'DOCUMENT_ROOT': '/var/www/reviews.burnttoast.local/htdocs',
 'GATEWAY_INTERFACE': 'CGI/1.1',
 'HTTP_ACCEPT':
'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
 'HTTP_ACCEPT_CHARSET': 'ISO-8859-1,utf-8;q=0.7,*;q=0.3',
 'HTTP_ACCEPT_ENCODING': 'gzip,deflate,sdch',
 'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.8',
 'HTTP_CONNECTION': 'keep-alive',
 'HTTP_COOKIE': 'csrftoken=580b2766fe12c70c23a58cca755a00f5;
rbsessionid=940bf1a27bf8477126b7a90e7e0c4293; collapsediffs=True',
 'HTTP_HOST': 'reviews.burnttoast.local',
 'HTTP_IF_NONE_MATCH': 'jmou:2011-10-18 04:06:15.963042::0:0:1317097313',
 'HTTP_REFERER': 'http://reviews.burnttoast.local/r/52/',
 'HTTP_USER_AGENT': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1
(KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1',
 'PATH_INFO': u'/r/52/',
 'PATH_TRANSLATED':
'/var/www/reviews.burnttoast.local/htdocs/reviewboard.wsgi/r/52/',
 'QUERY_STRING': '',
 'REMOTE_ADDR': '192.168.1.111',
 'REMOTE_PORT': '48526',
 'REQUEST_METHOD': 'GET',
 'REQUEST_URI': '/r/52/',
 'SCRIPT_FILENAME':
'/var/www/reviews.burnttoast.local/htdocs/reviewboard.wsgi',
 'SCRIPT_NAME': u'',
 'SERVER_ADDR': '192.168.1.108',
 'SERVER_ADMIN': '[no address given]',
 'SERVER_NAME': 'reviews.burnttoast.local',
 'SERVER_PORT': '80',
 'SERVER_PROTOCOL': 'HTTP/1.1',
 'SERVER_SIGNATURE': 'Apache/2.2.20 (Ubuntu) Server at
reviews.burnttoast.local Port 80\n',
 'SERVER_SOFTWARE': 'Apache/2.2.20 (Ubuntu)',
 'mod_wsgi.application_group': 'reviews.burnttoast.local|',
 'mod_wsgi.callable_object': 'application',
 'mod_

Re: Went to upgrade to 1.6 and got the following:

[Joe Campbell]

I did eventually make it past this issue by physically making the
modifications to the postgres database by hand.  The evolution then
completed and I was able to 'revert' any changes I had done and
everything worked.

After this was all said and done - upgrading from 1.6.0 to 1.6.1,
'Just worked' without needing any special intervention from me.

Joe

On Sep 11, 4:14 pm, Christian Hammond  wrote:
> Which 1.5?
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
> On Sun, Sep 11, 2011 at 1:02 PM, Joe Campbell
> wrote:
>
>
>
>
>
>
>
> > Was upgrading from base 1.5 release to 1.6 with a postgres DB.  I did
> > eventually get the evolutions to work by renaming existing columns and
> > dropping at least one empty table.  This allowed the evolutions to complete
> > and I was able to get the site back up and running.
>
> > Joe
>
> > On Sat, Sep 10, 2011 at 3:43 AM, Christian Hammond 
> > wrote:
>
> >> Hi Joe,
>
> >> Sorry, this got lost in a flood of e-mails.
>
> >> What version were you upgrading from?
>
> >> What type of database?
>
> >> Christian
>
> >> --
> >> Christian Hammond - chip...@chipx86.com
> >> Review Board -http://www.reviewboard.org
> >> VMware, Inc. -http://www.vmware.com
>
> >> On Thu, Sep 8, 2011 at 1:05 PM, Joe Campbell  >> > wrote:
>
> >>> Running rb-site upgrade /var/www/cim-review after an easy_install -U
> >>> ReviewBoard resulted in this:
>
> >>> Rebuilding directory structure
> >>> Updating database. This may take a while.
> >>> /usr/lib/python2.6/site-packages/Django-1.3-py2.6.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 tables ...
> >>> There are unapplied evolutions for sessions.
> >>> There are unapplied evolutions for accounts.
> >>> 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
> >>> Installing custom SQL ...
> >>> Installing indexes ...
> >>> No fixtures found.
> >>> /usr/lib/python2.6/site-packages/pycrypto-2.3-py2.6-linux-x86_64.egg/
> >>> Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This
> >>> application uses RandomPool, which is BROKEN in older releases.  See
> >>>http://www.pycrypto.org/randpool-broken
> >>>  RandomPool_DeprecationWarning)
> >>> Error: Error applying evolution: column "basedir" of relation
> >>> "diffviewer_diffset" already exists
>
> >>> And now my ReviewBoard Instance is complaining the DB is broken.
> >>> HELP?
>
> >>> --
> >>> 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 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 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: Missing an LDAP Bind DN?

[Joe Campbell]

Never mind - I found this after looking at how the code worked.  This
is currently listed as an Anonymous Bind Mask/Anonymous User Mask and
an Anonymous User Password.  These are actually the BIND DN and BIND
Password that I was looking for and are just very badly mislabeled on
the site.

Thanks,
 Joe


On Sep 8, 5:42 pm, Joe Campbell  wrote:
> There is currently no way to set a bind DN for a bind user to access
> the LDAP.  My ldap does not support anonymous binding.  Am I missing
> this config or is truly not there?

-- 
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: Went to upgrade to 1.6 and got the following:

[Joe Campbell]

1.5.0.

On Sun, Sep 11, 2011 at 4:14 PM, Christian Hammond wrote:

> Which 1.5?
>
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Sun, Sep 11, 2011 at 1:02 PM, Joe Campbell  > wrote:
>
>> Was upgrading from base 1.5 release to 1.6 with a postgres DB.  I did
>> eventually get the evolutions to work by renaming existing columns and
>> dropping at least one empty table.  This allowed the evolutions to complete
>> and I was able to get the site back up and running.
>>
>> Joe
>>
>> On Sat, Sep 10, 2011 at 3:43 AM, Christian Hammond 
>> wrote:
>>
>>> Hi Joe,
>>>
>>> Sorry, this got lost in a flood of e-mails.
>>>
>>> What version were you upgrading from?
>>>
>>> What type of database?
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - chip...@chipx86.com
>>> Review Board - http://www.reviewboard.org
>>> VMware, Inc. - http://www.vmware.com
>>>
>>>
>>> On Thu, Sep 8, 2011 at 1:05 PM, Joe Campbell <
>>> joseph.r.campb...@gmail.com> wrote:
>>>
>>>> Running rb-site upgrade /var/www/cim-review after an easy_install -U
>>>> ReviewBoard resulted in this:
>>>>
>>>> Rebuilding directory structure
>>>> Updating database. This may take a while.
>>>> /usr/lib/python2.6/site-packages/Django-1.3-py2.6.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 tables ...
>>>> There are unapplied evolutions for sessions.
>>>> There are unapplied evolutions for accounts.
>>>> 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
>>>> Installing custom SQL ...
>>>> Installing indexes ...
>>>> No fixtures found.
>>>> /usr/lib/python2.6/site-packages/pycrypto-2.3-py2.6-linux-x86_64.egg/
>>>> Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This
>>>> application uses RandomPool, which is BROKEN in older releases.  See
>>>> http://www.pycrypto.org/randpool-broken
>>>>  RandomPool_DeprecationWarning)
>>>> Error: Error applying evolution: column "basedir" of relation
>>>> "diffviewer_diffset" already exists
>>>>
>>>> And now my ReviewBoard Instance is complaining the DB is broken.
>>>> HELP?
>>>>
>>>> --
>>>> 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
>>>
>>
>>  --
>> 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
>

-- 
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: Went to upgrade to 1.6 and got the following:

[Joe Campbell]

Was upgrading from base 1.5 release to 1.6 with a postgres DB.  I did
eventually get the evolutions to work by renaming existing columns and
dropping at least one empty table.  This allowed the evolutions to complete
and I was able to get the site back up and running.

Joe

On Sat, Sep 10, 2011 at 3:43 AM, Christian Hammond wrote:

> Hi Joe,
>
> Sorry, this got lost in a flood of e-mails.
>
> What version were you upgrading from?
>
> What type of database?
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Thu, Sep 8, 2011 at 1:05 PM, Joe Campbell 
> wrote:
>
>> Running rb-site upgrade /var/www/cim-review after an easy_install -U
>> ReviewBoard resulted in this:
>>
>> Rebuilding directory structure
>> Updating database. This may take a while.
>> /usr/lib/python2.6/site-packages/Django-1.3-py2.6.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 tables ...
>> There are unapplied evolutions for sessions.
>> There are unapplied evolutions for accounts.
>> 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
>> Installing custom SQL ...
>> Installing indexes ...
>> No fixtures found.
>> /usr/lib/python2.6/site-packages/pycrypto-2.3-py2.6-linux-x86_64.egg/
>> Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This
>> application uses RandomPool, which is BROKEN in older releases.  See
>> http://www.pycrypto.org/randpool-broken
>>  RandomPool_DeprecationWarning)
>> Error: Error applying evolution: column "basedir" of relation
>> "diffviewer_diffset" already exists
>>
>> And now my ReviewBoard Instance is complaining the DB is broken.
>> HELP?
>>
>> --
>> 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

-- 
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

Missing an LDAP Bind DN?

[Joe Campbell]

There is currently no way to set a bind DN for a bind user to access
the LDAP.  My ldap does not support anonymous binding.  Am I missing
this config or is truly not there?

-- 
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

Went to upgrade to 1.6 and got the following:

[Joe Campbell]

Running rb-site upgrade /var/www/cim-review after an easy_install -U
ReviewBoard resulted in this:

Rebuilding directory structure
Updating database. This may take a while.
/usr/lib/python2.6/site-packages/Django-1.3-py2.6.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 tables ...
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
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
Installing custom SQL ...
Installing indexes ...
No fixtures found.
/usr/lib/python2.6/site-packages/pycrypto-2.3-py2.6-linux-x86_64.egg/
Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This
application uses RandomPool, which is BROKEN in older releases.  See
http://www.pycrypto.org/randpool-broken
  RandomPool_DeprecationWarning)
Error: Error applying evolution: column "basedir" of relation
"diffviewer_diffset" already exists

And now my ReviewBoard Instance is complaining the DB is broken.
HELP?

-- 
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: Upgrading from 1.6RC1 to 1.6RC2: There are unapplied evolutions for diffviewer.

[Joe Lencioni]

Specifically "There are unapplied evolutions for diffviewer." It
appeared in a red color which made me think it might be a problem.

On Fri, Jul 29, 2011 at 3:51 PM, Christian Hammond  wrote:
> Hi Joe,
>
> Nothing in there looks problematic to me. What concerned you? Just things
> like "No fixtures found" and "There are unapplied evolutions?"
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Fri, Jul 29, 2011 at 1:05 PM, Joe Lencioni 
> wrote:
>>
>> I just upgraded from 1.6RC1 to 1.6RC2 and when I ran rb-site upgrade, I
>> got the following output:
>> Rebuilding directory structure
>> Updating database. This may take a while.
>> Creating tables ...
>> Upgrading Review Board from 1.6 RC1 to 1.6 RC2
>> There are unapplied evolutions for diffviewer.
>> Installing custom SQL ...
>> Installing indexes ...
>> No fixtures found.
>> Evolution successful.
>> Resetting in-database caches.
>> Upgrade complete.
>>
>> After restarting my web server, everything seemed to work so I'm not too
>> worried about this, but thought I should pass it along in case this is a
>> problem that needs to be addressed.
>>
>> --
>> 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

-- 
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

Upgrading from 1.6RC1 to 1.6RC2: There are unapplied evolutions for diffviewer.

[Joe Lencioni]

I just upgraded from 1.6RC1 to 1.6RC2 and when I ran rb-site upgrade, I got 
the following output:

Rebuilding directory structure
Updating database. This may take a while.
Creating tables ...
Upgrading Review Board from 1.6 RC1 to 1.6 RC2
There are unapplied evolutions for diffviewer.
Installing custom SQL ...
Installing indexes ...
No fixtures found.
Evolution successful.
Resetting in-database caches.
Upgrade complete.


After restarting my web server, everything seemed to work so I'm not too 
worried about this, but thought I should pass it along in case this is a 
problem that needs to be addressed.

-- 
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

ValueError: No JSON object could be decoded

[Joe Lencioni]

I was running into a weird error with post-review.

Here's the post-review --debug

>>> RBTools 0.3.2
>>> Home = /path/to/home/dir
>>> svn info
>>> git rev-parse --git-dir
>>> git symbolic-ref -q HEAD
>>> git config --get branch.master.merge
>>> git config --get branch.master.remote
>>> git config remote.origin.url
>>> repository info: Path: /path/to/repo.git, Base path: , Supports 
changesets: False
>>> HTTP GETting api/
Traceback (most recent call last):
  File "/usr/bin/post-review", line 9, in 
load_entry_point('RBTools==0.3.2', 'console_scripts', 'post-review')()
  File "/usr/lib/python2.6/site-packages/rbtools/postreview.py", line 3741, 
in main
server.check_api_version()
  File "/usr/lib/python2.6/site-packages/rbtools/postreview.py", line 433, 
in check_api_version
root_resource = self.api_get('api/')
  File "/usr/lib/python2.6/site-packages/rbtools/postreview.py", line 876, 
in api_get
return self.process_json(self.http_get(path))
  File "/usr/lib/python2.6/site-packages/rbtools/postreview.py", line 812, 
in process_json
rsp = json_loads(data)
  File "/usr/lib64/python2.6/json/__init__.py", line 307, in loads
return _default_decoder.decode(s)
  File "/usr/lib64/python2.6/json/decoder.py", line 319, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python2.6/json/decoder.py", line 338, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded


I determined that the value of REVIEWBOARD_URL in my .reviewboardrc file was 
wrong. I corrected it and this fixed the error.

Would it be possible for post-review to generate a more helpful error 
message in this case?

-- 
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: Using post-review

[Joe Lencioni]

I think I figured this out.

Essentially, we were using git without a centralized repository. I believe 
that reviewboard doesn't like this.

So, I set up a directory on our server to act as a central repository and 
then cloned our repositories into there using the --bare option:

cd /path/to/new/
git clone --bare /path/to/old/git/repository

Then, I removed the old repositories:

rm -r /path/to/old/repository

And then cloned the git repository from the centralized repository back to 
where the old one was.

cd /path/to/old/
git clone /path/to/new/repository.git

Now I can run post-review and everything is happy.

post-review --guess-description --guess-summary

I even set up a post-commit hook for my git repository to automate this 
task:

echo "post-review --guess-summary --guess-description" >> 
/path/to/old/repository/.git/hooks/post-commit

So now when I do a git commit, the review automatically gets posted. Boom, 
roasted.

I think this is all working swimmingly now. Can you see any issues with this 
configuration?

-- 
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: Using post-review

[Joe Lencioni]

I am having the exact issue that Rajat was. I'm guessing that it is simply a 
matter of me not understanding exactly how reviewboard works.

Here's what post-review --debug gives me:

post-review --debug
>>> RBTools 0.3.2
>>> Home = /path/to/home/dir
>>> svn info
>>> git rev-parse --git-dir
>>> git symbolic-ref -q HEAD
>>> git config --get branch.test.merge
>>> git config --get branch.test.remote
>>> git config remote.origin.url
>>> git config remote.origin.url
Failed to execute command: ['git', 'config', 'remote.origin.url']

And when I run git config remote.origin.url, nothing happens.

Can you offer any guidance?

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: Importing users from LDAP

[Joe]

   error_and_exit(e[0]['desc'], 4)
>
> >>  # TODO(junk): remember what this does and comment on it
> >>  if result_data:
> >>    if result_type == ldap.RES_SEARCH_ENTRY:
> >>      results.append(result_data)
>
> >>  # If the group doesn't exist, bail out.
> >>  if not results:
> >>    error_and_exit('Group not found.', 5)
>
> >>  # If the group has no members, bail out.
> >>  if 'memberUid' not in results[0][0][1]:
> >>    error_and_exit('Group has no members', 6)
>
> >>  # Send back our results dictionary.
> >>  return results[0][0][1]['memberUid']
>
> >> def get_member_info(ldap_object, ldap_members):
> >>  """Get user info for each LDAP group member.
>
> >>  Args:
> >>    ldap_object: LDAP object user to connect and query the LDAP server
> >>    ldap_members: list of LDAP group members
> >>  Return:
> >>    ldap_user_info: dictionary of LDAP user info
> >>  """
> >>  search_scope = ldap.SCOPE_SUBTREE
> >>  ldap_user_info = {}
>
> >>  # Search through each member in our list.
> >>  for member in ldap_members:
> >>    # Run our LDAP query against all possible user DNs.
> >>    for dn in LUSER_DN:
> >>      ldap_filter = '%s=%s' % (LUSER_DN[dn][1], member)
> >>      try:
> >>        ldap_result_id = ldap_object.search(LUSER_DN[dn][0],
> >> search_scope,
> >>                                            ldap_filter)
> >>        result_type, result_data = ldap_object.result(ldap_result_id,
> >> 0)
> >>      except ldap.LDAPError, e:
> >>        error_and_exit(e[0]['desc'], 3)
>
> >>    # We don't store first and last names, only gecos.
> >>    if result_data:
> >>      first_name = result_data[0][1]['gecos'][0].split()[0]
> >>      last_name = result_data[0][1]['gecos'][0].split()[-1]
>
> >>    # Add each new user to the list.
> >>    ldap_user_info[member] = [last_name, first_name]
>
> >>  return ldap_user_info
>
> >> def add_rb_members(ldap_user_info):
> >>  """Add group members to ReviewBoard.
>
> >>  Args:
> >>    ldap_user_info: dictionary of LDAP user info to add
> >>  """
> >>  # Get current time in correct format.
> >>  now = time.strftime('%Y-%m-%d %H:%M:%S')
>
> >>  # Create a MySQL connection object to work with.
> >>  mysql_o = MySQLdb.connect(host=RB_HOST, user=RB_USER,
> >>                            passwd=RB_PASS, db=RB_DB)
> >>  cursor = mysql_o.cursor()
>
> >>  for user in ldap_user_info:
> >>    first_name = ldap_user_info[user][1]
> >>    last_name = ldap_user_info[user][0]
> >>    try:
> >>      cursor.execute('INSERT INTO auth_user
> >> (username,first_name,last_name,'
> >>                     'email,password,is_staff,is_active,is_superuser,'
> >>                     'last_login,date_joined) VALUES'
>
> >> '("%s","%s","%s","%...@company.com","!","0","1","0",'
> >>                     '"-00-00' '00:00:00","%s")' %
> >>                     (user, first_name, last_name, user, now))
> >>    # Ignore any exceptions and keep moving.
> >>    except:
> >>      pass
>
> >> def main(argv):
> >>  # Check to make sure our group is an alphabetic string.
> >>  try:
> >>    if not argv[1].isalpha():
> >>      error_and_exit('Group name provided appears invalid.', 2)
> >>    else:
> >>      group = argv[1]
> >>  except IndexError, e:
> >>    error_and_exit('No group specified.', 1)
>
> >>  # Create out LDAP object.
> >>  try:
> >>    ldap_o = ldap.open(L_HOST)
> >>    ldap_o.protocol_verion = ldap.VERSION3
> >>  except ldap.LDAPError, e:
> >>    error_and_exit(e[0]['desc'], 3)
>
> >>  # Get our LDAP group members.
> >>  ldap_members = get_ldap_members(ldap_o, group)
>
> >>  # Get user info for all users.
> >>  ldap_user_info = get_member_info(ldap_o, ldap_members)
>
> >>  # Add all our users to ReviewBoard.
> >>  add_rb_members(ldap_user_info)
>
> 

Re: Importing users from LDAP

[Joe]

Thanks Eric.

How were you able to push the data from ldap into reviewboard database
tables? Can you please provide some information on importing the ldap
data into our reviewboard database?



On May 15, 3:55 pm, Eric Johnson  wrote:
> On our ReviewBoard server, we push the data into the database tables. Has 
> been working quite well. Of course, you have to pay attention to users from 
> LDAP that already exist, and perhaps users who have been disabled in LDAP.
>
> No automated way to do it, other than that, at least that I'm aware.
>
> Eric
>
> On May 13, 2011, at 2:20 PM, Joe  wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > Currently, whenever we had to add an user from ldap to a group, the
> > user has to first login to the system, so that the user is added to
> > the reviewboard database.
> > We want a way to avoid having the user to login in order to use that
> > id from the admin ui.
>
> > So is there any way to import users from LDAP into the reviewboard?
>
> > Thanks
>
> > --
> > 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

Importing users from LDAP

[Joe]

Hi,

Currently, whenever we had to add an user from ldap to a group, the
user has to first login to the system, so that the user is added to
the reviewboard database.
We want a way to avoid having the user to login in order to use that
id from the admin ui.

So is there any way to import users from LDAP into the reviewboard?

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