Re: Installation of extension

2013-03-13 Thread Raja 
Hi,
http://www.reviewboard.org/docs/codebase/dev/extending/extensions/#python-egg 
contains instructions on how to install the custom extension. Once you have 
a setup.py, run 
setup.py install 
after writing your extension and restart the server. 

For activating the extension, goto Admin --> Extensions, where you can see 
all the extensions installed. Click Enable on your extension, which should 
enable your extension (provided there arent any errors).

Hope that helps
Raja


On Thursday, March 14, 2013 10:38:04 AM UTC+5:30, Aditi Sarkar wrote:
>
> Hey everyone,
>  I m new to to reviewboard. We are doing a college project 
> on reviewboard. And the requirement of the project is to extend the 
> features of reviewboard. From the official site's guidance we are able to 
> write the extension. We have put all the extension files in a folder. The 
> problem we are facing is we don't know where to place the extension folder 
> and what steps to do to install new extension. Please help.
>
> Thank you,
> Aditi
>

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

Installation of extension

2013-03-13 Thread Aditi Sarkar 
Hey everyone,
 I m new to to reviewboard. We are doing a college project 
on reviewboard. And the requirement of the project is to extend the 
features of reviewboard. From the official site's guidance we are able to 
write the extension. We have put all the extension files in a folder. The 
problem we are facing is we don't know where to place the extension folder 
and what steps to do to install new extension. Please help.

Thank you,
Aditi

-- 
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: Error while adding perforce 2012.2 repository to reviewboard 1.7.4

2013-03-13 Thread David Trowbridge 
Chuck,

This seems to be missing most of the p4python build. In particular I'd like
to see the output (and any output files) from the configure step.


-David


On Tue, Feb 26, 2013 at 1:53 AM, chuck j  wrote:

> Thanks David,
>
> please find the attached log file for the below steps. do let me know if
> any thing is missing from my end,
>
> -Chuck
>
>
>
> On Tue, Feb 26, 2013 at 12:51 AM, David Trowbridge wrote:
>
>> Can you get full logs of the output of all of those steps and attach
>> them/pastebin them somewhere?
>>
>>
>> -David
>>
>>
>> On Wed, Feb 20, 2013 at 2:27 AM, chuck j  wrote:
>>
>>> Thanks David for responding my email.
>>>
>>> Here are the steps which i followed.
>>>
>>> My Linux box has el5 has following openssl package.
>>>
>>> openssl097a-0.9.7a-9.el5_2.1
>>> openssl-devel-0.9.8e-12.el5
>>> openssl097a-0.9.7a-9.el5_2.1
>>> openssl-0.9.8e-12.el5
>>> openssl-0.9.8e-12.el5
>>> openssl-devel-0.9.8e-12.el5
>>>
>>> To compile p4python, i need to have openssl 1.0.1
>>>
>>> So i downloaded openssl 1.0.1c,
>>> ./config
>>> make
>>> make test
>>> make install
>>>
>>> Openssl gets installed at /usr/local/ssl location.
>>>
>>> I downloaded p4python and p4api from perforce.org site.
>>>
>>> python setup.py build --apidir /home/me/p4api --ssl /usr/local/ssl/lib
>>> python setup.py install
>>>
>>> Then i assume that p4python gets installed.
>>>
>>> I tested with the steps in python prompt
>>>
>>> import P4
>>> p4 = P4.P4()
>>> p4.connect()
>>> Traceback (most recent call last):
>>>   File "", line 1, in 
>>>   File "/usr/local/lib/python2.7/site

 -packages/P4.py", line 642, in connect
 P4API.P4Adapter.connect( self )
 P4.P4Exception: [P4.connect()] Connect to server failed; check $P4PORT.
 SSL library must be at least version 1.0.1.

>>>
>>> Please let me know if you need any thing else.
>>>
>>> Regards,
>>> Chuck
>>>
>>> On Tue, Feb 19, 2013 at 6:25 AM, David Trowbridge wrote:
>>>
 Can you show me a log of exactly which commands you used to build and
 install p4python?


 -David


 On Wed, Feb 13, 2013 at 12:00 PM, chuck j  wrote:

> Dear  All,
>
> Its seems i have got some success while configuring ssl.
>
> Now that our perforce server is running on ssl
>
> I am try to add the repository, while doing so i am getting below
> error message.
>
>
>- *The specified Perforce port includes ssl:, but the p4python
>library was built without SSL support or the system library path is
>incorrect. *
>
> As we have not able to find rpm for RHEL 2.6 OpenSSL 1.0.1, we have to
> build openssl 1.0.1, which eventually got installed at /usr/local/ssl/bin/
> /usr/local/ssl/ then we have build p4python with --ssl option.
>
> But its seems that still reviewboard reports about the above error
> message. Please help us know where to add the path of new build openssl
> library for which reviewboard server is looking for, if some pointer will
> be highly appreciated.
>
> -Chuck
>
>
>
>
>
> On Wed, Feb 13, 2013 at 7:24 AM, chuck j  wrote:
>
>>
>> Does my p4 info output gave expected output.
>>
>>
>>
>> [root@svrrb1 works]# p4 info
>> User name: chuckj
>> Client name: svrrb1
>> Client host: svrrb1.na.software.com
>> Client unknown.
>> Current directory: /works
>> Peer address: 182.16.43.144:42238
>> Client address: 
>> Server address: :1666
>> Server root: /PFMETA/p4root
>> Server date: 2013/02/12 01:09:47 -0800 PST
>> Server uptime: 286:15:29
>> Server version: P4D/LINUX26X86_64/2012.2/50 (2013/01/18)
>> Server encryption: encrypted
>> Server cert expires: Jan 31 10:22:47 2015 GMT
>> Server license: Software Corporation users (expires 2013/02/21)
>> Server license-ip: :1666
>> Case Handling: sensitive
>>
>>>
>>>
>> On Tuesday, February 12, 2013 4:49:40 PM UTC+5:30, chuck j wrote:
>>>
>>> Since i couldn't find openssl 1.0.1 rpm, I have to manually compile
>>> and build then install it to the default path, then later i have build
>>> p4python.
>>>
>>> root@svrrb1 p4python-2012.2.549493# python setup.py build --apidir
>>> /works/p4api-2012.2.585708/ --ssl /usr/local/
>>> root@svrrb1 p4python-2012.2.549493# python setup.py install
>>> --apidir /works/p4api-2012.2.585708/
>>>
>>> Assuming everything above working fine i test by providing below
>>> command line.
>>>
>>> >>> import P4
>>> >>> p4 = P4.P4()
>>> >>> p4.connect()
>>> Traceback (most recent call last):
>>>   File "", line 1, in 
>>>   File "/usr/local/lib/python2.7/**site-packages/P4.py", line 642,
>>> in connect
>>> P4API.P4Adapter.connect( self )
>>> P4.P4Exception: [P4.connect()] Connect to server failed; check
>>> $P4PORT.
>>> SSL library must be at least version

Re: Upgrade from 1.5.7 to 1.7.0.1

2013-03-13 Thread Christian Hammond 
Oh, because of 1.7.0.1. Right, newer versions hard-code a specific version.

Christian


On Mar 13, 2013, at 1:30, kvr  wrote:

> I have just done normal upgrade but it installed django-pipeline-1.3.6 and 
> django-pipeline-1.3.6 caused this error, after installing 1.2.17 or 1.7.22, 
> it got fixed.
> 
> On Wednesday, March 13, 2013 12:01:32 PM UTC+5:30, Christian Hammond wrote:
>> 
>> How did you upgrade Review Board? The proper, supported version should have 
>> been taken care of for you (and lessc should never be invoked).
>> 
>> Christian
>> 
>> -- 
>> Christian Hammond - chi...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> VMware, Inc. - http://www.vmware.com
>> 
>> On Mar 12, 2013, at 11:30 PM, kvr  wrote:
>> 
>>> 
>>> Resolved this by installing django-pipeline version-1.2.17
>>> 
>>> On Wednesday, March 13, 2013 11:17:44 AM UTC+5:30, kvr wrote:
 
 Hi ,
 
 We are upgrading our Review Board 1.5.7 to 1.7.0.1.
 
 Upgrade was successful but while accessing the site, we encountered the 
 following error.
 
 CompilerError at /dashboard/
 
 /usr/bin/env: lessc: No such file or directory
 
 This points to {% compressed_css "admin" %} in templates/admin/base.html
 
 Please help me to solve this.
 
 Regards,
 kvr
>>> 
>>> 
>>> -- 
>>> 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
>>> --- 
>>> 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/groups/opt_out.
> -- 
> 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.
>  
>  

-- 
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: Fwd: Django Evolution 0.6.9 released

2013-03-13 Thread Stephen Gallagher 
On Wed 13 Mar 2013 05:47:29 AM EDT, Christian Hammond wrote:
> This should help those of you who have had problems upgrading old
> installs of Review Board.
>
> Thanks to everyone who helped me test this!
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com 
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> -- Forwarded message --
> From: *Christian Hammond*  >
> Date: Wed, Mar 13, 2013 at 2:40 AM
> Subject: Django Evolution 0.6.9 released
> To: django-evolut...@googlegroups.com
> 
> Cc: Stephen Gallagher  >
>
>
> Hi everyone,
>
> Django Evolution 0.6.9 is out. This added some more introspection when
> applying evolutions so that a mutation isn't applied if the old
> database signature for that model already matches the new signature.
>
> Basically, this means if you have a very old database, and a new model
> has been introduced since then *and* new evolutions were added to that
> model, you shouldn't have any confusing errors when trying to run the
> evolutions. Previously, it would install a baseline for the new models
> that matched the latest version of the model, and then try to apply
> (now old) mutations to that model, which would fail. This shouldn't
> happen anymore.
>
> As usual, you can install the latest release by doing:
>
> $ sudo easy_install -U django_evolution
>
> or
>
> $ sudo pip install -U django_evolution
>
> I'm planning to move the sourcecode for Django Evolution onto GitHub.
> While I haven't done it yet, you should expect that the next release
> will come off of http://github.com/reviewboard/django-evolution/.
> Hopefully this won't impact anyone. Let me know if you think it will.
>


Additionally, I've just submitted this for Fedora 18 and EPEL 6, so 
within 24 hours (for the mirrors to sync) you will be able to run:

yum install --enablerepo=updates-testing python-django-evolution


Bodhi update links:
https://admin.fedoraproject.org/updates/python-django-evolution-0.6.9-1.fc18
https://admin.fedoraproject.org/updates/python-django-evolution-0.6.9-1.el6.1

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

Fwd: Django Evolution 0.6.9 released

2013-03-13 Thread Christian Hammond 
This should help those of you who have had problems upgrading old installs
of Review Board.

Thanks to everyone who helped me test this!

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


-- Forwarded message --
From: Christian Hammond 
Date: Wed, Mar 13, 2013 at 2:40 AM
Subject: Django Evolution 0.6.9 released
To: django-evolut...@googlegroups.com
Cc: Stephen Gallagher 


Hi everyone,

Django Evolution 0.6.9 is out. This added some more introspection when
applying evolutions so that a mutation isn't applied if the old database
signature for that model already matches the new signature.

Basically, this means if you have a very old database, and a new model has
been introduced since then *and* new evolutions were added to that model,
you shouldn't have any confusing errors when trying to run the evolutions.
Previously, it would install a baseline for the new models that matched the
latest version of the model, and then try to apply (now old) mutations to
that model, which would fail. This shouldn't happen anymore.

As usual, you can install the latest release by doing:

$ sudo easy_install -U django_evolution

or

$ sudo pip install -U django_evolution

I'm planning to move the sourcecode for Django Evolution onto GitHub. While
I haven't done it yet, you should expect that the next release will come
off of http://github.com/reviewboard/django-evolution/. Hopefully this
won't impact anyone. Let me know if you think it will.

Thanks,

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com

-- 
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: Upgrade from 1.5.7 to 1.7.0.1

2013-03-13 Thread kvr 
I have just done normal upgrade but it installed django-pipeline-1.3.6 and 
django-pipeline-1.3.6 caused this error, after installing 1.2.17 or 1.7.22, 
it got fixed.

On Wednesday, March 13, 2013 12:01:32 PM UTC+5:30, Christian Hammond wrote:
>
> How did you upgrade Review Board? The proper, supported version should 
> have been taken care of for you (and lessc should never be invoked).
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com 
>
> On Mar 12, 2013, at 11:30 PM, kvr > wrote:
>
>
> Resolved this by installing django-pipeline version-1.2.17
>
> On Wednesday, March 13, 2013 11:17:44 AM UTC+5:30, kvr wrote:
>>
>> Hi ,
>>
>> We are upgrading our Review Board 1.5.7 to 1.7.0.1.
>>
>> Upgrade was successful but while accessing the site, we encountered the 
>> following error.
>>
>> CompilerError at /dashboard/
>>
>> /usr/bin/env: lessc: No such file or directory
>>
>> This points to {% compressed_css "admin" %} in templates/admin/base.html
>>
>> Please help me to solve this.
>>
>> Regards,
>> kvr
>>
>
> -- 
> 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
> --- 
> 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/groups/opt_out.
>  
>  
>
>
>

-- 
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: LDAP setting in ReviewBoard

2013-03-13 Thread 李海梅 
Meanwhile, I use this command to check: vi
./usr/local/lib/python2.7//site-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/admin/checks.py

def get_can_enable_ldap():
"""Checks whether LDAP authentication can be enabled."""
try:
imp.find_module("ldap")
return (True, None)
except ImportError:
return (False, _(
'LDAP authentication requires the python-ldap library, which '
'is not installed.'
))

Any suggestion?


On Wed, Mar 13, 2013 at 3:46 PM, 李海梅  wrote:

> Hello all,
>
> when i want to configurate LDAP in reviewboard. i meet this problems.
> First, the red words remind me to install python-ldap library.
>
> And then, i goto reviewboard server to build python-ldap by :yum install
> python26 python26-ldap . The installation is successfull.
>
> And then, i restart apache by : /etc/init.d/httpd restart. The restart is
> successful.
>
> I go back to reviewboard web page and refresh it, it still gives me the
> remind which is the same with first step.
>
> How to fix the problem?
>
> Thanks for your suggestion.
>
>
> --
> Haimei Li
> CISCO,Hangzhou,China
> E-Mail: lihaimei880...@gmail.com
>



-- 
Haimei Li
CISCO,Hangzhou,China
E-Mail: lihaimei880...@gmail.com

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

LDAP setting in ReviewBoard

2013-03-13 Thread 李海梅 
Hello all,

when i want to configurate LDAP in reviewboard. i meet this problems.
First, the red words remind me to install python-ldap library.

And then, i goto reviewboard server to build python-ldap by :yum install
python26 python26-ldap . The installation is successfull.

And then, i restart apache by : /etc/init.d/httpd restart. The restart is
successful.

I go back to reviewboard web page and refresh it, it still gives me the
remind which is the same with first step.

How to fix the problem?

Thanks for your suggestion.


-- 
Haimei Li
CISCO,Hangzhou,China
E-Mail: lihaimei880...@gmail.com

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