Re: Announcements to Users

[Raja]

I built an extension just for this purpose, its available at
https://github.com/rajasaur/rb-extension-pack/tree/master/rbbroadcastmessage

Instructions to install are also available in the same page, but if you
prefer a pre-built tarball instead of clone and setup.py install, please
let me know. There is one available at
https://github.com/rajasaur/rb-extension-pack/tree/gh-pages/downloads/rbbroadcastmessage,
but I will need to test this again as it was tested a few months ago.

Best regards,
Raja


On Wed, Jun 26, 2013 at 12:40 AM, Christian Hammond wrote:

> Hi Peter,
>
> A MOTD is something I intend to add, but I have no ETA. Hopefully for 1.8.
>
> There's no feature to message all users, but you could whip up a script or
> an extension to do it without much trouble. I'm not opposed to adding such
> a feature, if done right, but I think it's best as an extension.
>
> Christian
>
>
>
> Peter Snelling wrote:
>
>> Is there any way for the administrator to send an e-mail to all
>> reviewboard users? I can just copy all the e-mail addresses manually but I
>> was hoping for something easier than that.
>> Or perhaps to set a short "Message Of the Day" on the top banner?
>> I'm just looking for an easy way tell users about a planned outage.
>>
>> --
>> 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+unsubscribe@**
>> 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+unsubscribe@**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+unsubscribe@**
> 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+unsubscribe@**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: rb-site upgrade fails on database migration

[Erik Lattimore]

Thanks, that solved the issue. Looks like mysql 5.5 defaults to InnoDB but 
our original tables were in the older format. I altered them to InnoDB and 
everything works now. Thanks,
--Erik

On Tuesday, June 25, 2013 4:26:12 PM UTC-4, Christian Hammond wrote:
>
> That error has to do with having a mix of InnoDB and MyISAM tables. You 
> need to make sure all tables are the same format. If MySQL is creating new 
> tables with one, then you should convert the rest.
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>
>
> On Tue, Jun 25, 2013 at 12:44 PM, Erik Lattimore 
> 
> > wrote:
>
>> I'm getting the exact same error. I'm trying to test an upgrade before 
>> actually performing one on the live server and am getting the same Django 
>> stack trace.
>>
>> We are running RB 1.5.2 in production on Ubuntu 12.04. I've been using 
>> easy_install to install ReviewBoard and made sure to force the Django 
>> dependency(1.3.3) since the 1.5.2 package pulls in too new of a version. I 
>> used mysqldump to dump the db from the live server and installed a site by 
>> running rb-site install ... and then seeding the database with the 
>> production data through mysql reviewboard < dump.sql. I then use 
>> easy_install to upgrade to 1.7.1, which completes but the rb-site upgrade 
>> command fails. However, one thing that I did notice is that I have no issue 
>> upgrading an empty install by doing the same steps as before, but not 
>> seeding the backup database and only upgrading an empty site.
>>
>>
>>
>>
>> On Tuesday, January 8, 2013 4:34:42 PM UTC-5, virtualAdmin wrote:
>>>
>>> We've been making regular backups of our RB 1.5.5 database, and I 
>>> decided it was time to verify that we can restore the DB to a new install 
>>> in case our server fails.  The backups are made with mysqlhotcopy, so I 
>>> understand they can be restored by simply stopping the mysql service, 
>>> copying the backup files into the appropriate folder 
>>> (/var/lib/mysql/reviewboard), and starting mysql.
>>>
>>> I installed RB 1.7 on an Ubuntu 12.04 LTS VM.  I got the software all 
>>> installed and removed the fresh 1.7 database, replacing it with our 
>>> backed-up 1.5.5 DB, making sure to set proper privileges on the db files 
>>> and in mysql itself.
>>>
>>> I ran:
>>>
>>> rb-site upgrade -d /var/www/mysite
>>>
>>> Which failed, giving this output:
>>>
>>> --  --
>>> Creating tables ...
>>> Creating table attachments_fileattachment
>>> Creating table diffviewer_filediffdata
>>> Creating table hostingsvcs_**hostingserviceaccount
>>> Creating table reviews_fileattachmentcomment
>>> Creating table site_localsite_users
>>> Traceback (most recent call last):
>>>   File "/usr/local/bin/rb-site", line 9, in 
>>> load_entry_point('ReviewBoard=**=1.7.1', 'console_scripts', 
>>> 'rb-site')()
>>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>>> 1-py2.7.egg/reviewboard/**cmdline/rbsite.py", line 1937, in main
>>> command.run()
>>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>>> 1-py2.7.egg/reviewboard/**cmdline/rbsite.py", line 1778, in run
>>> site.sync_database()
>>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>>> 1-py2.7.egg/reviewboard/**cmdline/rbsite.py", line 366, in sync_database
>>> self.run_manage_command("**syncdb", params)
>>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>>> 1-py2.7.egg/reviewboard/**cmdline/rbsite.py", line 556, in 
>>> run_manage_command
>>> execute_manager(reviewboard.**settings, [__file__, cmd] + params)
>>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>>> py2.7.egg/django/core/**management/__init__.py", line 459, in 
>>> execute_manager
>>> utility.execute()
>>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>>> py2.7.egg/django/core/**management/__init__.py", line 382, in execute
>>> self.fetch_command(subcommand)**.run_from_argv(self.argv)
>>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>>> py2.7.egg/django/core/**management/base.py", line 196, in run_from_argv
>>> self.execute(*args, **options.__dict__)
>>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>>> py2.7.egg/django/core/**management/base.py", line 232, in execute
>>> output = self.handle(*args, **options)
>>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>>> py2.7.egg/django/core/**management/base.py", line 371, in handle
>>> return self.handle_noargs(**options)
>>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>>> py2.7.egg/django/core/**management/commands/syncdb.py"**, line 102, in 
>>> handle_noargs
>>> cursor.execute(statement)
>>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>>> py2.7.egg/django/db/backends/**mysql/base.py", line 114, in execute
>>>

Review Board 1.7.11 released

[Christian Hammond]

Hi everyone,

I just put out a release of Review Board 1.7.11. It's a minor release 
that fixes Python 2.5 compatibility and a small visual bug with HTML 
entities on IE9.


For those still running on Python 2.5, I highly recommend upgrading to 
Python 2.7 as soon as it's convenient. We will be dropping 2.5 support 
for RB 1.8.


http://www.reviewboard.org/news/2013/06/25/review-board-1-7-11-released/

Christian

--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.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: API URLs - browser wants to download instead of display

[Matthew Dawes]

Is RB trying to authenticate against the p4 info server instead of the 
actual proxy? It was able to connect with p4 previously when it pulled 
changelist and performed the diff. 

On Tuesday, June 25, 2013 11:23:09 AM UTC-7, Matthew Dawes wrote:
>
> My Review Board 1.7.10 installation seems to be working for the most part. 
> I can navigate and update all the admin pages and can view the dashboard, 
> groups, submitters, etc but I am having an issue displaying any of the API 
> url's. The browser wants to download them instead of display them. It sees 
> them as type application/vnd.reviewboard.org.root+xml. When I download the 
> files they are properly formatted XML.
>
> On a possibly related note, when I am trying to use rbt post CHG# to post 
> a review I am getting an HTTP 404. I set up my RB installation at 
> /var/www/reviews with the site web root at /. I have installed a previous 
> site with the site web root at /reviews/ but rbt still seems to be looking 
> at http:///reviews/api/ instead of http:///api/. I changed my 
> site web root to /reviews/ to try and match what it was looking for but I 
> think the API URLs not displaying is still causing a problem.
>
> Here is the output of my rbt post -d:
>
> rbt post 9509 -d
> DEBUG:root:Checking for a Subversion repository...
> DEBUG:root:Checking for a Git repository...
> DEBUG:root:Running: git.cmd rev-parse --git-dir
> DEBUG:root:Command exited with rc 128: ['git.cmd', 'rev-parse', 
> '--git-dir']
> fatal: Not a git repository (or any of the parent directories): .git
> ---
> DEBUG:root:Checking for a Mercurial repository...
> DEBUG:root:Checking for a CVS repository...
> DEBUG:root:Checking for a Perforce repository...
> DEBUG:root:Running: p4 info
> DEBUG:root:Running: diff --version
> DEBUG:root:repository info: Path: , Base path: None, 
> Supports changesets: True
> DEBUG:root:Making HTTP GET request to http:///reviews/api/
> Traceback (most recent call last):
>   File "C:\Python27\Scripts\rbt-script.py", line 9, in 
> load_entry_point('RBTools==0.5.1', 'console_scripts', 'rbt')()
>   File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/main.py", line 
> 99, in
>  main
>   File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py", 
> line 15
> 8, in run_from_argv
>   File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/post.py", line 
> 448, i
> n main
>   File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py", 
> line 26
> 0, in get_api
> rbtools.commands.CommandError: Unexpected API Error: HTTP 404
>
> Thanks,
>
> Matt
>

-- 
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: rb-site upgrade fails on database migration

[Christian Hammond]

That error has to do with having a mix of InnoDB and MyISAM tables. You
need to make sure all tables are the same format. If MySQL is creating new
tables with one, then you should convert the rest.

Christian

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


On Tue, Jun 25, 2013 at 12:44 PM, Erik Lattimore wrote:

> I'm getting the exact same error. I'm trying to test an upgrade before
> actually performing one on the live server and am getting the same Django
> stack trace.
>
> We are running RB 1.5.2 in production on Ubuntu 12.04. I've been using
> easy_install to install ReviewBoard and made sure to force the Django
> dependency(1.3.3) since the 1.5.2 package pulls in too new of a version. I
> used mysqldump to dump the db from the live server and installed a site by
> running rb-site install ... and then seeding the database with the
> production data through mysql reviewboard < dump.sql. I then use
> easy_install to upgrade to 1.7.1, which completes but the rb-site upgrade
> command fails. However, one thing that I did notice is that I have no issue
> upgrading an empty install by doing the same steps as before, but not
> seeding the backup database and only upgrading an empty site.
>
>
>
>
> On Tuesday, January 8, 2013 4:34:42 PM UTC-5, virtualAdmin wrote:
>>
>> We've been making regular backups of our RB 1.5.5 database, and I decided
>> it was time to verify that we can restore the DB to a new install in case
>> our server fails.  The backups are made with mysqlhotcopy, so I understand
>> they can be restored by simply stopping the mysql service, copying the
>> backup files into the appropriate folder (/var/lib/mysql/reviewboard), and
>> starting mysql.
>>
>> I installed RB 1.7 on an Ubuntu 12.04 LTS VM.  I got the software all
>> installed and removed the fresh 1.7 database, replacing it with our
>> backed-up 1.5.5 DB, making sure to set proper privileges on the db files
>> and in mysql itself.
>>
>> I ran:
>>
>> rb-site upgrade -d /var/www/mysite
>>
>> Which failed, giving this output:
>>
>> --  --
>> Creating tables ...
>> Creating table attachments_fileattachment
>> Creating table diffviewer_filediffdata
>> Creating table hostingsvcs_**hostingserviceaccount
>> Creating table reviews_fileattachmentcomment
>> Creating table site_localsite_users
>> Traceback (most recent call last):
>>   File "/usr/local/bin/rb-site", line 9, in 
>> load_entry_point('ReviewBoard=**=1.7.1', 'console_scripts',
>> 'rb-site')()
>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>> 1-py2.7.egg/reviewboard/**cmdline/rbsite.py", line 1937, in main
>> command.run()
>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>> 1-py2.7.egg/reviewboard/**cmdline/rbsite.py", line 1778, in run
>> site.sync_database()
>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>> 1-py2.7.egg/reviewboard/**cmdline/rbsite.py", line 366, in sync_database
>> self.run_manage_command("**syncdb", params)
>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>> 1-py2.7.egg/reviewboard/**cmdline/rbsite.py", line 556, in
>> run_manage_command
>> execute_manager(reviewboard.**settings, [__file__, cmd] + params)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/core/**management/__init__.py", line 459, in
>> execute_manager
>> utility.execute()
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/core/**management/__init__.py", line 382, in execute
>> self.fetch_command(subcommand)**.run_from_argv(self.argv)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/core/**management/base.py", line 196, in run_from_argv
>> self.execute(*args, **options.__dict__)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/core/**management/base.py", line 232, in execute
>> output = self.handle(*args, **options)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/core/**management/base.py", line 371, in handle
>> return self.handle_noargs(**options)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/core/**management/commands/syncdb.py"**, line 102, in
>> handle_noargs
>> cursor.execute(statement)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/backends/**mysql/base.py", line 114, in execute
>> return self.cursor.execute(query, args)
>>   File "/usr/lib/python2.7/dist-**packages/MySQLdb/cursors.py", line
>> 174, in execute
>> self.errorhandler(self, exc, value)
>>   File "/usr/lib/python2.7/dist-**packages/MySQLdb/connections.**py",
>> line 36, in defaulterrorhandler
>> raise errorclass, errorvalue
>> django.db.utils.DatabaseError: (1005, "Can't create table
>> 'reviewboard.#s

Re: rb-site upgrade fails on database migration

[Erik Lattimore]

I'm getting the exact same error. I'm trying to test an upgrade before 
actually performing one on the live server and am getting the same Django 
stack trace.

We are running RB 1.5.2 in production on Ubuntu 12.04. I've been using 
easy_install to install ReviewBoard and made sure to force the Django 
dependency(1.3.3) since the 1.5.2 package pulls in too new of a version. I 
used mysqldump to dump the db from the live server and installed a site by 
running rb-site install ... and then seeding the database with the 
production data through mysql reviewboard < dump.sql. I then use 
easy_install to upgrade to 1.7.1, which completes but the rb-site upgrade 
command fails. However, one thing that I did notice is that I have no issue 
upgrading an empty install by doing the same steps as before, but not 
seeding the backup database and only upgrading an empty site.



On Tuesday, January 8, 2013 4:34:42 PM UTC-5, virtualAdmin wrote:
>
> We've been making regular backups of our RB 1.5.5 database, and I decided 
> it was time to verify that we can restore the DB to a new install in case 
> our server fails.  The backups are made with mysqlhotcopy, so I understand 
> they can be restored by simply stopping the mysql service, copying the 
> backup files into the appropriate folder (/var/lib/mysql/reviewboard), and 
> starting mysql.
>
> I installed RB 1.7 on an Ubuntu 12.04 LTS VM.  I got the software all 
> installed and removed the fresh 1.7 database, replacing it with our 
> backed-up 1.5.5 DB, making sure to set proper privileges on the db files 
> and in mysql itself.
>
> I ran:
>
> rb-site upgrade -d /var/www/mysite
>
> Which failed, giving this output:
>
> --  --
> Creating tables ...
> Creating table attachments_fileattachment
> Creating table diffviewer_filediffdata
> Creating table hostingsvcs_hostingserviceaccount
> Creating table reviews_fileattachmentcomment
> Creating table site_localsite_users
> Traceback (most recent call last):
>   File "/usr/local/bin/rb-site", line 9, in 
> load_entry_point('ReviewBoard==1.7.1', 'console_scripts', 'rb-site')()
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py",
>  
> line 1937, in main
> command.run()
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py",
>  
> line 1778, in run
> site.sync_database()
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py",
>  
> line 366, in sync_database
> self.run_manage_command("syncdb", params)
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py",
>  
> line 556, in run_manage_command
> execute_manager(reviewboard.settings, [__file__, cmd] + params)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/__init__.py",
>  
> line 459, in execute_manager
> utility.execute()
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/__init__.py",
>  
> line 382, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py",
>  
> line 196, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py",
>  
> line 232, in execute
> output = self.handle(*args, **options)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py",
>  
> line 371, in handle
> return self.handle_noargs(**options)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/commands/syncdb.py",
>  
> line 102, in handle_noargs
> cursor.execute(statement)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/backends/mysql/base.py",
>  
> line 114, in execute
> return self.cursor.execute(query, args)
>   File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 174, in 
> execute
> self.errorhandler(self, exc, value)
>   File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 36, 
> in defaulterrorhandler
> raise errorclass, errorvalue
> django.db.utils.DatabaseError: (1005, "Can't create table 
> 'reviewboard.#sql-5a2b_5b' (errno: 150)")
>
> Any ideas?
>

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

Re: API URLs - browser wants to download instead of display

[Matthew Dawes]

That makes sense. I wanted to be sure that the APIs not displaying in the 
browser wasn't causing the 404 but it looks like that is not the case. My 
.reviewboardrc was still pointing at the /reviews/. Thanks again.

The last issue with my setup is that we are using a P4 proxy. I am getting 
to the Web API auth step and once I authenticate I am getting the HTTP 403, 
API Error 218 - Unable to authenticate with the repository using the 
provided credentials. I have tried putting the proxy as the Mirror and the 
P4 info server name as the Path as I saw recommended in an earlier thread. 
Is that still the way to go with a proxy setup for P4? I tried reversing it 
as well but I get the 403 either way. Here is the rbt post log:

DEBUG:root:Making HTTP GET request to http:///api/review-requests/
DEBUG:root:Making HTTP POST request to http:///api/review-requests/
==> HTTP Authentication Required
Enter authorization information for "Web API" at 
Username: admin
Password:
Traceback (most recent call last):
  File "C:\Python27\Scripts\rbt-script.py", line 9, in 
load_entry_point('RBTools==0.5.1', 'console_scripts', 'rbt')()
  File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/main.py", line 
99, in
 main
  File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py", 
line 15
8, in run_from_argv
  File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/post.py", line 
489, i
n main
  File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/post.py", line 
342, i
n post_request
rbtools.commands.CommandError: Error creating review request: Unable to 
authenti
cate with the repository using the provided credentials (HTTP 403, API 
Error 218
)


On Tuesday, June 25, 2013 11:23:09 AM UTC-7, Matthew Dawes wrote:
>
> My Review Board 1.7.10 installation seems to be working for the most part. 
> I can navigate and update all the admin pages and can view the dashboard, 
> groups, submitters, etc but I am having an issue displaying any of the API 
> url's. The browser wants to download them instead of display them. It sees 
> them as type application/vnd.reviewboard.org.root+xml. When I download the 
> files they are properly formatted XML.
>
> On a possibly related note, when I am trying to use rbt post CHG# to post 
> a review I am getting an HTTP 404. I set up my RB installation at 
> /var/www/reviews with the site web root at /. I have installed a previous 
> site with the site web root at /reviews/ but rbt still seems to be looking 
> at http:///reviews/api/ instead of http:///api/. I changed my 
> site web root to /reviews/ to try and match what it was looking for but I 
> think the API URLs not displaying is still causing a problem.
>
> Here is the output of my rbt post -d:
>
> rbt post 9509 -d
> DEBUG:root:Checking for a Subversion repository...
> DEBUG:root:Checking for a Git repository...
> DEBUG:root:Running: git.cmd rev-parse --git-dir
> DEBUG:root:Command exited with rc 128: ['git.cmd', 'rev-parse', 
> '--git-dir']
> fatal: Not a git repository (or any of the parent directories): .git
> ---
> DEBUG:root:Checking for a Mercurial repository...
> DEBUG:root:Checking for a CVS repository...
> DEBUG:root:Checking for a Perforce repository...
> DEBUG:root:Running: p4 info
> DEBUG:root:Running: diff --version
> DEBUG:root:repository info: Path: , Base path: None, 
> Supports changesets: True
> DEBUG:root:Making HTTP GET request to http:///reviews/api/
> Traceback (most recent call last):
>   File "C:\Python27\Scripts\rbt-script.py", line 9, in 
> load_entry_point('RBTools==0.5.1', 'console_scripts', 'rbt')()
>   File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/main.py", line 
> 99, in
>  main
>   File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py", 
> line 15
> 8, in run_from_argv
>   File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/post.py", line 
> 448, i
> n main
>   File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py", 
> line 26
> 0, in get_api
> rbtools.commands.CommandError: Unexpected API Error: HTTP 404
>
> Thanks,
>
> Matt
>

-- 
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: Announcements to Users

[Christian Hammond]

Hi Peter,

A MOTD is something I intend to add, but I have no ETA. Hopefully for 1.8.

There's no feature to message all users, but you could whip up a script or an 
extension to do it without much trouble. I'm not opposed to adding such a 
feature, if done right, but I think it's best as an extension.

Christian


Peter Snelling wrote:
Is there any way for the administrator to send an e-mail to all 
reviewboard users? I can just copy all the e-mail addresses manually 
but I was hoping for something easier than that.

Or perhaps to set a short "Message Of the Day" on the top banner?
I'm just looking for an easy way tell users about a planned outage.

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

Announcements to Users

[Peter Snelling]

Is there any way for the administrator to send an e-mail to all reviewboard 
users? I can just copy all the e-mail addresses manually but I was hoping 
for something easier than that. 
Or perhaps to set a short "Message Of the Day" on the top banner?
I'm just looking for an easy way tell users about a planned outage.

-- 
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: API URLs - browser wants to download instead of display

[Christian Hammond]

Hi Matthew,

Yeah, how browsers handle these vendor-specific mimetypes is pretty 
annoying. It doesn't treat them as text/xml or application/json. I keep 
brainstorming around creating browser-friendly encoders for the URLs, 
but it's pretty far down the priority list. In the meantime, curl is 
useful, and I believe there are some browser extensions meant for seeing 
these payloads for development purposes.


For rbt-post, does your .reviewboardrc still point to /reviews/?

Christian


Matthew Dawes wrote:

My Review Board 1.7.10 installation seems to be working for the most
part. I can navigate and update all the admin pages and can view the
dashboard, groups, submitters, etc but I am having an issue displaying
any of the API url's. The browser wants to download them instead of
display them. It sees them as type
application/vnd.reviewboard.org.root+xml. When I download the files they
are properly formatted XML.

On a possibly related note, when I am trying to use rbt post CHG# to
post a review I am getting an HTTP 404. I set up my RB installation at
/var/www/reviews with the site web root at /. I have installed a
previous site with the site web root at /reviews/ but rbt still seems to
be looking at http:///reviews/api/ instead of
http:///api/. I changed my site web root to /reviews/ to try and
match what it was looking for but I think the API URLs not displaying is
still causing a problem.

Here is the output of my rbt post -d:

rbt post 9509 -d
DEBUG:root:Checking for a Subversion repository...
DEBUG:root:Checking for a Git repository...
DEBUG:root:Running: git.cmd rev-parse --git-dir
DEBUG:root:Command exited with rc 128: ['git.cmd', 'rev-parse', '--git-dir']
fatal: Not a git repository (or any of the parent directories): .git
---
DEBUG:root:Checking for a Mercurial repository...
DEBUG:root:Checking for a CVS repository...
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Running: p4 info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: , Base path: None,
Supports changesets: True
DEBUG:root:Making HTTP GET request to http:///reviews/api/
Traceback (most recent call last):
File "C:\Python27\Scripts\rbt-script.py", line 9, in 
load_entry_point('RBTools==0.5.1', 'console_scripts', 'rbt')()
File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/main.py", line
99, in
main
File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py",
line 15
8, in run_from_argv
File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/post.py", line
448, i
n main
File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py",
line 26
0, in get_api
rbtools.commands.CommandError: Unexpected API Error: HTTP 404

Thanks,

Matt

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




--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.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: strange behavior of django-evolution 0.6.9

[Christian Hammond]

Hi Satish,

It's really pretty iffy adding your own columns to our models. Things can, and 
will, break, as you're noticing.

Did you add an evolution file for your columns? It wasn't clear from your 
description.

If you ran --evolve --hint, you're going to have a bad time, as it's just going 
to cause problems with our evolutions. Got a backup?

What version did you upgrade from?

Christian


satish singh wrote:

Hi Team,
Can anyone explain me this behaviour.?

On Tuesday, 25 June 2013 18:39:48 UTC+5:30, satish singh wrote:


I had Review Board 1.7.7.1 on our testing environment running
successfully on production clone db.

I did a model change because of which it asked for running a
evolution manually. We ran it and it was successful.


Now when we went for upgrade on production db, it asked for manual
evolution because of last change. Now when I ran the manual
evolution it gave error.

Error:

Error: Error applying evolution: (1060, "Duplicate column name
'diff_base64'")***- manual evolution failed***

*I reverted the last change we made and evolution was successful,
it doesn't ask for manual evolution*

bash-3.2# /opt/software/bin/rb-site upgrade /var/www/xyz.com



-  --

Creating tables ...

There are unapplied evolutions for auth.

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

Installed 0 object(s) from 0 fixture(s)

Evolution successful.

---  ---

Resetting in-database caches.

Upgrade complete!

*After this I modified to include the last change as part of
enhancement and ran the upgrade again, it asked for manual
evolution and ran successfully:*

bash-3.2# /opt/software/bin/rb-site upgrade /var/www/xyz.com


--  --

Creating tables ...

Project signature has changed - an evolution is required

Installing custom SQL ...

Installing indexes ...

Installed 0 object(s) from 0 fixture(s)

The stored evolutions do not completely resolve all model changes.

Run `./manage.py evolve --hint` to see a suggestion for the
changes required.  asking for manual evolution

The following are the changes that could not be resolved:

In model reviews.FileAttachmentComment:

Field 'severity' has been added  change we made as part of
enhancement

Error: Your models contain changes that Django Evolution cannot
resolve

automatically.

bash-3.2# /opt/software/bin/python2.7 ./reviewboard/manage.py
evolve --hint --execute


/opt/software/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57:
PowmInsecureWarning: Not using mpz_powm_sec.

You should rebuild using libgmp >= 5 to avoid timing attack
vulnerability.

You have requested a database evolution. This will alter tables

and data currently in the 'default' database, and may result in

IRREVERSABLE DATA LOSS. Evolutions should be *thoroughly* reviewed

prior to execution

Are you sure you want to execute the evolutions?

Type 'yes' to continue, or 'no' to cancel: yes

Evolution successful.

*This behavior of django evolution is strange. Why didn't it ran
with the change at once and gave the *"Duplicate column name
'diff_base64'" error.

*Is there any logic for this, why it failed ?*

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

API URLs - browser wants to download instead of display

[Matthew Dawes]

My Review Board 1.7.10 installation seems to be working for the most part. 
I can navigate and update all the admin pages and can view the dashboard, 
groups, submitters, etc but I am having an issue displaying any of the API 
url's. The browser wants to download them instead of display them. It sees 
them as type application/vnd.reviewboard.org.root+xml. When I download the 
files they are properly formatted XML.

On a possibly related note, when I am trying to use rbt post CHG# to post a 
review I am getting an HTTP 404. I set up my RB installation at 
/var/www/reviews with the site web root at /. I have installed a previous 
site with the site web root at /reviews/ but rbt still seems to be looking 
at http:///reviews/api/ instead of http:///api/. I changed my 
site web root to /reviews/ to try and match what it was looking for but I 
think the API URLs not displaying is still causing a problem.

Here is the output of my rbt post -d:

rbt post 9509 -d
DEBUG:root:Checking for a Subversion repository...
DEBUG:root:Checking for a Git repository...
DEBUG:root:Running: git.cmd rev-parse --git-dir
DEBUG:root:Command exited with rc 128: ['git.cmd', 'rev-parse', '--git-dir']
fatal: Not a git repository (or any of the parent directories): .git
---
DEBUG:root:Checking for a Mercurial repository...
DEBUG:root:Checking for a CVS repository...
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Running: p4 info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: , Base path: None, 
Supports changesets: True
DEBUG:root:Making HTTP GET request to http:///reviews/api/
Traceback (most recent call last):
  File "C:\Python27\Scripts\rbt-script.py", line 9, in 
load_entry_point('RBTools==0.5.1', 'console_scripts', 'rbt')()
  File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/main.py", line 
99, in
 main
  File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py", 
line 15
8, in run_from_argv
  File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/post.py", line 
448, i
n main
  File "build/bdist.macosx-10.8-intel/egg/rbtools/commands/__init__.py", 
line 26
0, in get_api
rbtools.commands.CommandError: Unexpected API Error: HTTP 404

Thanks,

Matt

-- 
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: Review Board 1.6.17 and 1.7.10 released

[vk]

Error while upgrading!


root@xxx:/mnt/usb/backup#* rb-site upgrade /var/www/rb/*
Traceback (most recent call last):
  File "/usr/bin/rb-site", line 8, in 
load_entry_point('ReviewBoard==1.7.10', 'console_scripts', 'rb-site')()
  File 
"/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/cmdline/rbsite.py",
 
line 1937, in main
command.run()
  File 
"/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/cmdline/rbsite.py",
 
line 1762, in run
static_media_upgrade_needed = site.get_static_media_upgrade_needed()
  File 
"/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/cmdline/rbsite.py",
 
line 383, in get_static_media_upgrade_needed
siteconfig = SiteConfiguration.objects.get_current()
  File 
"/usr/lib/python2.5/site-packages/Djblets-0.7.15-py2.5.egg/djblets/siteconfig/managers.py",
 
line 47, in get_current
site = Site.objects.get_current()
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/contrib/sites/models.py",
 
line 25, in get_current
current_site = self.get(pk=sid)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/manager.py",
 
line 131, in get
return self.get_query_set().get(*args, **kwargs)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/query.py",
 
line 358, in get
clone = self.filter(*args, **kwargs)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/query.py",
 
line 624, in filter
return self._filter_or_exclude(False, *args, **kwargs)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/query.py",
 
line 642, in _filter_or_exclude
clone.query.add_q(Q(*args, **kwargs))
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/sql/query.py",
 
line 1250, in add_q
can_reuse=used_aliases, force_having=force_having)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/sql/query.py",
 
line 1122, in add_filter
process_extras=process_extras)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/sql/query.py",
 
line 1304, in setup_joins
field, model, direct, m2m = opts.get_field_by_name(name)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/options.py",
 
line 311, in get_field_by_name
cache = self.init_name_map()
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/options.py",
 
line 341, in init_name_map
for f, model in self.get_all_related_m2m_objects_with_model():
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/options.py",
 
line 429, in get_all_related_m2m_objects_with_model
cache = self._fill_related_many_to_many_cache()
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/options.py",
 
line 443, in _fill_related_many_to_many_cache
for klass in get_models(only_installed=False):
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/loading.py",
 
line 181, in get_models
self._populate()
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/loading.py",
 
line 64, in _populate
self.load_app(app_name, True)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/loading.py",
 
line 88, in load_app
models = import_module('.models', app_name)
  File 
"/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/utils/importlib.py",
 
line 35, in import_module
__import__(name)
  File 
"/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/accounts/models.py",
 
line 9, in 
from reviewboard.reviews.models import Group, ReviewRequest
  File 
"/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/reviews/models.py",
 
line 19, in 
from reviewboard.attachments.models import FileAttachment
  File 
"/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/attachments/models.py",
 
line 10, in 
class FileAttachment(models.Model):
  File 
"/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/attachments/models.py",
 
line 41, in FileAttachment
@thumbnail.setter
AttributeError: 'property' object has no attribute 'setter'


On Saturday, June 22, 2013 11:51:45 PM UTC-4, Christian Hammond wrote:
>
> Hi everyone,
>
> We have two new releases out tonight. Both are important security updates 
> for a vulnerability that was reported to us that affects primarily 
> public-facing sites.
>
> 1.7.10 contains some additional bug fixes and improvements.
>
> For more info, see 
> http://www.reviewboard.org/news/2013/06/22/review-board-1617-and-1710-released/
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>  

-- 
Want to help the Review Board p

Re: Review Board 1.6.17 and 1.7.10 released

[Christian Hammond]

Looks like we have a Python 2.5 regression. We'll need to put out a patch 
release. I'll do it today.

Christian


On Jun 25, 2013, at 9:50, v...@newtrax.com wrote:

> Error while upgrading!
> 
> 
> root@xxx:/mnt/usb/backup# rb-site upgrade /var/www/rb/
> Traceback (most recent call last):
>   File "/usr/bin/rb-site", line 8, in 
> load_entry_point('ReviewBoard==1.7.10', 'console_scripts', 'rb-site')()
>   File 
> "/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/cmdline/rbsite.py",
>  line 1937, in main
> command.run()
>   File 
> "/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/cmdline/rbsite.py",
>  line 1762, in run
> static_media_upgrade_needed = site.get_static_media_upgrade_needed()
>   File 
> "/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/cmdline/rbsite.py",
>  line 383, in get_static_media_upgrade_needed
> siteconfig = SiteConfiguration.objects.get_current()
>   File 
> "/usr/lib/python2.5/site-packages/Djblets-0.7.15-py2.5.egg/djblets/siteconfig/managers.py",
>  line 47, in get_current
> site = Site.objects.get_current()
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/contrib/sites/models.py",
>  line 25, in get_current
> current_site = self.get(pk=sid)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/manager.py",
>  line 131, in get
> return self.get_query_set().get(*args, **kwargs)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/query.py",
>  line 358, in get
> clone = self.filter(*args, **kwargs)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/query.py",
>  line 624, in filter
> return self._filter_or_exclude(False, *args, **kwargs)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/query.py",
>  line 642, in _filter_or_exclude
> clone.query.add_q(Q(*args, **kwargs))
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/sql/query.py",
>  line 1250, in add_q
> can_reuse=used_aliases, force_having=force_having)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/sql/query.py",
>  line 1122, in add_filter
> process_extras=process_extras)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/sql/query.py",
>  line 1304, in setup_joins
> field, model, direct, m2m = opts.get_field_by_name(name)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/options.py",
>  line 311, in get_field_by_name
> cache = self.init_name_map()
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/options.py",
>  line 341, in init_name_map
> for f, model in self.get_all_related_m2m_objects_with_model():
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/options.py",
>  line 429, in get_all_related_m2m_objects_with_model
> cache = self._fill_related_many_to_many_cache()
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/options.py",
>  line 443, in _fill_related_many_to_many_cache
> for klass in get_models(only_installed=False):
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/loading.py",
>  line 181, in get_models
> self._populate()
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/loading.py",
>  line 64, in _populate
> self.load_app(app_name, True)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/db/models/loading.py",
>  line 88, in load_app
> models = import_module('.models', app_name)
>   File 
> "/usr/lib/python2.5/site-packages/Django-1.4.5-py2.5.egg/django/utils/importlib.py",
>  line 35, in import_module
> __import__(name)
>   File 
> "/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/accounts/models.py",
>  line 9, in 
> from reviewboard.reviews.models import Group, ReviewRequest
>   File 
> "/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/reviews/models.py",
>  line 19, in 
> from reviewboard.attachments.models import FileAttachment
>   File 
> "/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/attachments/models.py",
>  line 10, in 
> class FileAttachment(models.Model):
>   File 
> "/usr/lib/python2.5/site-packages/ReviewBoard-1.7.10-py2.5.egg/reviewboard/attachments/models.py",
>  line 41, in FileAttachment
> @thumbnail.setter
> AttributeError: 'property' object has no attribute 'setter'
> 
> 
> On Saturday, June 22, 2013 11:51:45 PM UTC-4, Christian Hammond wrote:
>> 
>> Hi everyone,
>> 
>> We have two new releases out tonight. Both are important security updates 
>> for a vulnerability that was reported to us that affects primarily 
>> public-facing sites.

Re: Problems upgrading from 1.6.6 to 1.7.9

[Santiago Gimeno]

Just a little update on this, upgrading to 1.6.16 didn't work either :(


2013/6/21 Santiago Gimeno 

> Hello,
>
> After following the upgrade procedures I'm getting this error:
>
> [Fri Jun 21 13:15:39 2013] [error]
> /usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/views/generic/list_detail.py:10:
> DeprecationWarning: Function-based generic views have been deprecated; use
> class-based views instead.
> [Fri Jun 21 13:15:39 2013] [error]   DeprecationWarning
> [Fri Jun 21 13:15:40 2013] [error]
> /usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/conf/__init__.py:75:
> DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use
> STATIC_URL instead.
> [Fri Jun 21 13:15:40 2013] [error]   "use STATIC_URL instead.",
> DeprecationWarning)
> [Fri Jun 21 13:15:40 2013] [error] ERROR:django.request:Internal Server
> Error: /reviews/dashboard/
> [Fri Jun 21 13:15:40 2013] [error] Traceback (most recent call last):
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/core/handlers/base.py",
> line 89, in get_response
> [Fri Jun 21 13:15:40 2013] [error] response =
> middleware_method(request)
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/accounts/middleware.py",
> line 12, in process_request
> [Fri Jun 21 13:15:40 2013] [error] user =
> Profile.objects.get(user=request.user)
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/db/models/manager.py",
> line 131, in get
> [Fri Jun 21 13:15:40 2013] [error] return
> self.get_query_set().get(*args, **kwargs)
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/db/models/query.py",
> line 361, in get
> [Fri Jun 21 13:15:40 2013] [error] num = len(clone)
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/db/models/query.py",
> line 85, in __len__
> [Fri Jun 21 13:15:40 2013] [error] self._result_cache =
> list(self.iterator())
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/db/models/query.py",
> line 291, in iterator
> [Fri Jun 21 13:15:40 2013] [error] for row in compiler.results_iter():
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/db/models/sql/compiler.py",
> line 763, in results_iter
> [Fri Jun 21 13:15:40 2013] [error] for rows in self.execute_sql(MULTI):
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/db/models/sql/compiler.py",
> line 818, in execute_sql
> [Fri Jun 21 13:15:40 2013] [error] cursor.execute(sql, params)
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Djblets-0.7.15-py2.6.egg/djblets/log/middleware.py",
> line 49, in execute
> [Fri Jun 21 13:15:40 2013] [error] return self.cursor.execute(sql,
> params)
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/local/lib/python2.6/dist-packages/Django-1.4.5-py2.6.egg/django/db/backends/mysql/base.py",
> line 114, in execute
> [Fri Jun 21 13:15:40 2013] [error] return self.cursor.execute(query,
> args)
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/lib/pymodules/python2.6/MySQLdb/cursors.py", line 166, in execute
> [Fri Jun 21 13:15:40 2013] [error] self.errorhandler(self, exc, value)
> [Fri Jun 21 13:15:40 2013] [error]   File
> "/usr/lib/pymodules/python2.6/MySQLdb/connections.py", line 35, in
> defaulterrorhandler
> [Fri Jun 21 13:15:40 2013] [error] raise errorclass, errorvalue
> [Fri Jun 21 13:15:40 2013] [error] DatabaseError: (1054, "Unknown column
> 'accounts_profile.open_an_issue' in 'field list'")
>
>
> So, then I went back to 1.6.6 and tried to upgrade first to 1.6.16 and I
> succeeded, but trying to upgrade again to 1.7.9 failed again withe the same
> error.
>
> I'm running it in a standard debian squeeze machine with no special
> configuration
>
> Any idea what might be happening?
>
> Thanks in advance. Best regards,
>
> Santi
>

-- 
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: Manual server updates required - Permission problems

[Stephen Gallagher]

On 06/25/2013 12:51 PM, Matthew Woehlke wrote:
> On 2013-06-25 12:27, Stephen Gallagher wrote:
>> On 06/25/2013 12:24 PM, Matthew Woehlke wrote:
>>> On 2013-06-25 07:48, Stephen Gallagher wrote:
 Yeah, my TODO list includes working up some SELinux rules for
 ReviewBoard and getting rb-site to be capable of setting them up during
 installation. It's a pretty big task and low on my priority list right
 now, unfortunately.
>>>
>>> Heh. I'm running with SELinux enabled. I can probably dig up the
>>> relevant *compiled* rules if those are of any use. I think I deleted the
>>> 'source' files for them, however. (Yeah, bad decision in retrospect, but
>>> haven't gotten around to trying to recreate them.)
>>>
>>> I don't think there are actually very many (maybe four, but at least one
>>> is git specific; probably need additional rules for other VCS's).
>>
>> If you can figure out what they are, it would be a great start for me.
>>
>> I don't necessarily just need exception rules, though. We may want to
>> introduce new SELinux types for rules so we keep things constrained.
>> (Though since basically everything runs inside apache/mod_wsgi, we're
>> probably going to end up mostly using apache rules).
> 
> By memory and file names... I had to grant httpd (don't recall if that
> was a user, process, context, ...) access to specific sockets for git,
> LDAP and postgres. (Unfortunately, all of those are to some degree
> specific to my setup, e.g. someone else might need none of those, but
> instead need to grant access to MySQL and SVN.)
> 
> I can send you .pp files, but I'm not sure if those are useful to other
> than a running system, or even on another release of Fedora (I'm on 18,
> currently).
> 

Thee compiled .pp files won't be useful, I'm afraid.

-- 
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: Manual server updates required - Permission problems

[Matthew Woehlke]

On 2013-06-25 12:27, Stephen Gallagher wrote:

On 06/25/2013 12:24 PM, Matthew Woehlke wrote:

On 2013-06-25 07:48, Stephen Gallagher wrote:

Yeah, my TODO list includes working up some SELinux rules for
ReviewBoard and getting rb-site to be capable of setting them up during
installation. It's a pretty big task and low on my priority list right
now, unfortunately.


Heh. I'm running with SELinux enabled. I can probably dig up the
relevant *compiled* rules if those are of any use. I think I deleted the
'source' files for them, however. (Yeah, bad decision in retrospect, but
haven't gotten around to trying to recreate them.)

I don't think there are actually very many (maybe four, but at least one
is git specific; probably need additional rules for other VCS's).


If you can figure out what they are, it would be a great start for me.

I don't necessarily just need exception rules, though. We may want to
introduce new SELinux types for rules so we keep things constrained.
(Though since basically everything runs inside apache/mod_wsgi, we're
probably going to end up mostly using apache rules).


By memory and file names... I had to grant httpd (don't recall if that 
was a user, process, context, ...) access to specific sockets for git, 
LDAP and postgres. (Unfortunately, all of those are to some degree 
specific to my setup, e.g. someone else might need none of those, but 
instead need to grant access to MySQL and SVN.)


I can send you .pp files, but I'm not sure if those are useful to other 
than a running system, or even on another release of Fedora (I'm on 18, 
currently).


--
Matthew

--
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: Manual server updates required - Permission problems

[Stephen Gallagher]

On 06/25/2013 12:24 PM, Matthew Woehlke wrote:
> On 2013-06-25 07:48, Stephen Gallagher wrote:
>> Yeah, my TODO list includes working up some SELinux rules for
>> ReviewBoard and getting rb-site to be capable of setting them up during
>> installation. It's a pretty big task and low on my priority list right
>> now, unfortunately.
> 
> Heh. I'm running with SELinux enabled. I can probably dig up the
> relevant *compiled* rules if those are of any use. I think I deleted the
> 'source' files for them, however. (Yeah, bad decision in retrospect, but
> haven't gotten around to trying to recreate them.)
> 
> I don't think there are actually very many (maybe four, but at least one
> is git specific; probably need additional rules for other VCS's).
> 

If you can figure out what they are, it would be a great start for me.

I don't necessarily just need exception rules, though. We may want to
introduce new SELinux types for rules so we keep things constrained.
(Though since basically everything runs inside apache/mod_wsgi, we're
probably going to end up mostly using apache rules).

-- 
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: Manual server updates required - Permission problems

[Matthew Woehlke]

On 2013-06-25 07:48, Stephen Gallagher wrote:

Yeah, my TODO list includes working up some SELinux rules for
ReviewBoard and getting rb-site to be capable of setting them up during
installation. It's a pretty big task and low on my priority list right
now, unfortunately.


Heh. I'm running with SELinux enabled. I can probably dig up the 
relevant *compiled* rules if those are of any use. I think I deleted the 
'source' files for them, however. (Yeah, bad decision in retrospect, but 
haven't gotten around to trying to recreate them.)


I don't think there are actually very many (maybe four, but at least one 
is git specific; probably need additional rules for other VCS's).


--
Matthew

--
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: strange behavior of django-evolution 0.6.9

[satish singh]

Hi Team,
Can anyone explain me this behaviour.?

On Tuesday, 25 June 2013 18:39:48 UTC+5:30, satish singh wrote:
>
>
> I had Review Board 1.7.7.1 on our testing environment running successfully 
> on production clone db.
>
> I did a model change because of which it asked for running a evolution 
> manually. We ran it and it was successful.
>
>
> Now when we went for upgrade on production db, it asked for manual 
> evolution because of last change. Now when I ran the manual evolution it 
> gave error.
>
> Error:
>
> Error: Error applying evolution: (1060, "Duplicate column name 
> 'diff_base64'")*   **- manual evolution failed***
>
> *I reverted the last change we made and evolution was successful, it 
> doesn't ask for manual evolution*
>
> bash-3.2# /opt/software/bin/rb-site upgrade /var/www/xyz.com
>
>
>  -  --
>
> Creating tables ...
>
> There are unapplied evolutions for auth.
>
> 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 ...
>
> Installed 0 object(s) from 0 fixture(s)
>
> Evolution successful.
>
> ---  ---
>
>  Resetting in-database caches.
>
>  Upgrade complete! 
>
> *After this I modified to include the last change as part of enhancement 
> and ran the upgrade again, it asked for manual evolution and ran 
> successfully:*
>
> bash-3.2# /opt/software/bin/rb-site upgrade /var/www/xyz.com
>
> --  --
>
> Creating tables ...
>
> Project signature has changed - an evolution is required
>
> Installing custom SQL ...
>
> Installing indexes ...
>
> Installed 0 object(s) from 0 fixture(s)
>
> The stored evolutions do not completely resolve all model changes.
>
> Run `./manage.py evolve --hint` to see a suggestion for the changes 
> required.    asking for manual evolution
>
> The following are the changes that could not be resolved:
>
> In model reviews.FileAttachmentComment:
>
> Field 'severity' has been 
> added
>  change we made as part of enhancement
>
> Error: Your models contain changes that Django Evolution cannot resolve 
>
>  automatically.
>
> bash-3.2# /opt/software/bin/python2.7 ./reviewboard/manage.py evolve 
> --hint --execute
>
> /opt/software/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57:
>  
> PowmInsecureWarning: Not using mpz_powm_sec. 
>
> You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
>
> You have requested a database evolution. This will alter tables
>
> and data currently in the 'default' database, and may result in
>
> IRREVERSABLE DATA LOSS. Evolutions should be *thoroughly* reviewed
>
> prior to execution
>
> Are you sure you want to execute the evolutions?
>
> Type 'yes' to continue, or 'no' to cancel: yes
>
> Evolution successful.
>
> *This behavior of django evolution is strange. Why didn't it ran with the 
> change at once and gave the * "Duplicate column name 'diff_base64'" error.
>
> *Is there any logic for this, why it failed ?*
>

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

strange behavior of django-evolution 0.6.9

[satish singh]

I had Review Board 1.7.7.1 on our testing environment running successfully 
on production clone db.

I did a model change because of which it asked for running a evolution 
manually. We ran it and it was successful.


Now when we went for upgrade on production db, it asked for manual 
evolution because of last change. Now when I ran the manual evolution it 
gave error.

Error:

Error: Error applying evolution: (1060, "Duplicate column name 
'diff_base64'")*   **- manual evolution failed***

*I reverted the last change we made and evolution was successful, it 
doesn't ask for manual evolution*

bash-3.2# /opt/software/bin/rb-site upgrade /var/www/xyz.com


 -  --

Creating tables ...

There are unapplied evolutions for auth.

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

Installed 0 object(s) from 0 fixture(s)

Evolution successful.

---  ---

 Resetting in-database caches.

 Upgrade complete! 

*After this I modified to include the last change as part of enhancement 
and ran the upgrade again, it asked for manual evolution and ran 
successfully:*

bash-3.2# /opt/software/bin/rb-site upgrade /var/www/xyz.com

--  --

Creating tables ...

Project signature has changed - an evolution is required

Installing custom SQL ...

Installing indexes ...

Installed 0 object(s) from 0 fixture(s)

The stored evolutions do not completely resolve all model changes.

Run `./manage.py evolve --hint` to see a suggestion for the changes 
required.    asking for manual evolution

The following are the changes that could not be resolved:

In model reviews.FileAttachmentComment:

Field 'severity' has been 
added
 change we made as part of enhancement

Error: Your models contain changes that Django Evolution cannot resolve 

 automatically.

bash-3.2# /opt/software/bin/python2.7 ./reviewboard/manage.py evolve --hint 
--execute

/opt/software/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57:
 
PowmInsecureWarning: Not using mpz_powm_sec. 

You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.

You have requested a database evolution. This will alter tables

and data currently in the 'default' database, and may result in

IRREVERSABLE DATA LOSS. Evolutions should be *thoroughly* reviewed

prior to execution

Are you sure you want to execute the evolutions?

Type 'yes' to continue, or 'no' to cancel: yes

Evolution successful.

*This behavior of django evolution is strange. Why didn't it ran with the 
change at once and gave the * "Duplicate column name 'diff_base64'" error.

*Is there any logic for this, why it failed ?*

-- 
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: Manual server updates required - Permission problems

[Stephen Gallagher]

On 06/25/2013 04:54 AM, Matthew Dawes wrote:
> SELinux was enabled. I disabled it and I am back in business. Thank you
> so much for the quick response.
> 
> Matt 
> 
> On Tuesday, June 25, 2013 1:32:16 AM UTC-7, Christian Hammond wrote:
> 
> Can you show the exact error info?
> 
> See if SELinux is enabled, and turn it off.
> 
> Christian
> 
> On Jun 24, 2013, at 22:57, Matthew Dawes  > wrote:
> 
>> I keep running into this same issue with a new install of
>> ReviewBoard. I have created multiple sites but each time I get the
>> error message that there is a permission problem. I have chowned
>> the requested directories so they are owned by the Apache user but
>> Review Board still complains that they are incorrect. What am I
>> missing?
>>
>> Here are my install specs:
>>
>> Server: Fedora 14
>> Review Board: 1.7.10
>> Python: 2.7
>> Django: 1.4.5
>>
>> Thanks in advance.
>>


Yeah, my TODO list includes working up some SELinux rules for
ReviewBoard and getting rb-site to be capable of setting them up during
installation. It's a pretty big task and low on my priority list right
now, unfortunately.

Also, I highly recommend upgrading from Fedora 14, since it's been
unsupported for over eighteen months and almost certainly has security
issues. If you want long-term updates, you'd be better off with RHEL
6/CentOS 6.

-- 
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: Manual server updates required - Permission problems

[Matthew Dawes]

SELinux was enabled. I disabled it and I am back in business. Thank you so 
much for the quick response.

Matt 

On Tuesday, June 25, 2013 1:32:16 AM UTC-7, Christian Hammond wrote:
>
> Can you show the exact error info?
>
> See if SELinux is enabled, and turn it off.
>
> Christian
>
> On Jun 24, 2013, at 22:57, Matthew Dawes > 
> wrote:
>
> I keep running into this same issue with a new install of ReviewBoard. I 
> have created multiple sites but each time I get the error message that 
> there is a permission problem. I have chowned the requested directories so 
> they are owned by the Apache user but Review Board still complains that 
> they are incorrect. What am I missing?
>
> Here are my install specs:
>
> Server: Fedora 14
> Review Board: 1.7.10
> Python: 2.7
> Django: 1.4.5
>
> Thanks in advance.
>
>
>  -- 
> 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: Review Board 1.6.17 and 1.7.10 released

[victoria]

On Mon, Jun 24, 2013 at 6:15 PM, Stephen Gallagher
 wrote:
> On 06/22/2013 11:51 PM, Christian Hammond wrote:
>> Hi everyone,
>>
>> We have two new releases out tonight. Both are important security
>> updates for a vulnerability that was reported to us that affects
>> primarily public-facing sites.
>>
>> 1.7.10 contains some additional bug fixes and improvements.
>>
>> For more info,
>> see 
>> http://www.reviewboard.org/news/2013/06/22/review-board-1617-and-1710-released/
>>
>
>
> Fedora and EPEL 6 packages are now on their way to the updates-testing
> repository. As this contains a fix for a security issue, I'd appreciate
> it if karma could be provided at the below links in order to push it to
> stable ASAP.
>
> **
> IMPORTANT: Fedora 17 is no longer supported for ReviewBoard[1], please
> upgrade to Fedora 18/19 or switch to using easy_install.
> **
>
>
>
>
> Fedora 19:
> https://admin.fedoraproject.org/updates/ReviewBoard-1.7.10-1.fc19
>
> Fedora 18:
> https://admin.fedoraproject.org/updates/ReviewBoard-1.7.10-1.fc18
>
> EPEL 6:
> https://admin.fedoraproject.org/updates/ReviewBoard-1.7.10-1.el6
>
>
>
> If you wish to test these packages before they filter out to the
> mirrors, you can download the RPMs directly and install them with 'yum
> localinstall --nogpgcheck ReviewBoard*.rpm':
>
> Fedora 19:
> http://kojipkgs.fedoraproject.org//packages/ReviewBoard/1.7.10/1.fc19/noarch/ReviewBoard-1.7.10-1.fc19.noarch.rpm
>
> Fedora 18:
> http://kojipkgs.fedoraproject.org//packages/ReviewBoard/1.7.10/1.fc18/noarch/ReviewBoard-1.7.10-1.fc18.noarch.rpm
>
> EPEL 6:
> http://kojipkgs.fedoraproject.org//packages/ReviewBoard/1.7.10/1.el6/noarch/ReviewBoard-1.7.10-1.el6.noarch.rpm
>
>
>
>
>
> [1] Fedora 17 has upgraded to Django 1.4 in the main repo. People who
> have been using ReviewBoard up to this point will have just been holding
> their local Django at 1.3 in yum. However, I can no longer build a new
> copy of ReviewBoard because 1.6.x won't build against Django 1.4 and
> ReviewBoard 1.7.x requires other dependencies that are two new to be
> carried in Fedora 17. If you need long-term supportability for
> ReviewBoard, I recommend using RHEL 6. Otherwise, please upgrade your
> systems to Fedora 18 or 19 (the latter which is in its release-candidate
> stage now and quite stable).
>

Review Board 1.7.10 released on BitNami as well. Installers, virtual
machines and cloud images available in
http://bitnami.org/stack/reviewboard



> --
> 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: Manual server updates required - Permission problems

[Christian Hammond]

Can you show the exact error info?

See if SELinux is enabled, and turn it off.

Christian

On Jun 24, 2013, at 22:57, Matthew Dawes  wrote:

> I keep running into this same issue with a new install of ReviewBoard. I have 
> created multiple sites but each time I get the error message that there is a 
> permission problem. I have chowned the requested directories so they are 
> owned by the Apache user but Review Board still complains that they are 
> incorrect. What am I missing?
> 
> Here are my install specs:
> 
> Server: Fedora 14
> Review Board: 1.7.10
> Python: 2.7
> Django: 1.4.5
> 
> Thanks in advance.
> 
> 
> -- 
> 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.