Re: The current directory does not contain a checkout... (problem posting from perforce)

[Greg Dean]

Thanks David, that gets me going.

On Saturday, February 15, 2014 5:03:45 PM UTC-8, David Trowbridge wrote:
>
> Greg,
>
> You're probably getting hit by case mismatches (
> https://code.google.com/p/reviewboard/issues/detail?id=3221). We'll be 
> fixing this for 0.5.8.
>
> -David
>
>
> On Wed, Feb 12, 2014 at 5:14 PM, Greg Dean 
> > wrote:
>
>> Hi there, I've updated to 0.5.7 and I'm running from cygwin and I get the 
>> same result. Can rbt be run from cygwin? Here is what I get:
>>
>>
>> $ rbt post -d -o 299074
>> DEBUG:root:Checking for a Subversion repository...
>> DEBUG:root:Checking for a Git repository...
>> 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:Checking for a Plastic repository...
>> DEBUG:root:Checking for a ClearCase repository...
>> DEBUG:root:Checking for a Bazaar repository...
>> ERROR:root:The current directory does not contain a checkout from a 
>> supported source code repository.
>>
>>
>> On Tuesday, February 4, 2014 1:14:16 PM UTC-8, Karl Nordstrom wrote:
>>>
>>> Thanks for the quick fix! 0.5.7 did it.
>>>
>>> Karl
>>>
>>> On Monday, 3 February 2014 13:50:03 UTC-8, Karl Nordstrom wrote:
>>>>
>>>> Okay, looking forward to getting the fix.
>>>>
>>>> Thanks,
>>>> Karl
>>>>
>>>> On Monday, 3 February 2014 13:28:17 UTC-8, David Trowbridge wrote:
>>>>>
>>>>> Karl,
>>>>>
>>>>> It looks like we introduced a regression in 0.5.6 where it only will 
>>>>> post from the client root. We'll get this sorted out asap.
>>>>>
>>>>> -David
>>>>>
>>>>>
>>>>> On Mon, Feb 3, 2014 at 1:17 PM, Karl Nordstrom wrote:
>>>>>
>>>>>> I am attempting to generate a diff using rbt diff from a perforce 
>>>>>> workspace. I get the same error when I do rbt post.
>>>>>>
>>>>>> (Thank you for helping with the previous problem I was having, it 
>>>>>> appears to be resolved with RBTools 0.5.6.)
>>>>>>
>>>>>> My p4config is as follows:
>>>>>>
>>>>>> P4PORT=stork:1666
>>>>>> P4USER=knordstrom
>>>>>> P4CLIENT=knordstrom_passenger
>>>>>>
>>>>>> The p4config appears to be setup correctly. I can do p4 diff from 
>>>>>> the commandline and generate a diff without errors. Unfortunately, this 
>>>>>> diff is not in a format that ReviewBoard understands.
>>>>>>
>>>>>> My .reviewboard rc file is as follows (just one line):
>>>>>>
>>>>>> REVIEWBOARD_URL = "http://reviewboard/";
>>>>>>
>>>>>> I have tried the following on the commandline:
>>>>>>
>>>>>> rbt diff -d
>>>>>> rbt diff -d 25012   (the latest changelist number)
>>>>>> rbt post -d
>>>>>> rbt post -d 25012
>>>>>>
>>>>>> In all cases I get the same result:
>>>>>>
>>>>>> DEBUG:root:Checking for a Subversion repository...
>>>>>> DEBUG:root:Checking for a Git repository...
>>>>>> 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:Checking for a Plastic repository...
>>>>>> DEBUG:root:Checking for a ClearCase repository...
>>>>>> DEBUG:root:Checking for a Bazaar repository...
>>>>>> ERROR:root:The current directory does not contain a checkout from a 
>>>>>> supported source code repository.
>>>>>>
>>>>>> When I do p4 info it provides relevant information. I'm hesitant to 
>>>>>> post it here as it shows company specific information.
>>>>>>
>>>>>> Is there something that I need to do in the configuration?
>>>>>>
>>>>>> Is this something to do with the way that Perforce works? As far as I 
>>>>>> can tell, Perforce works on work

Re: The current directory does not contain a checkout... (problem posting from perforce)

[Greg Dean]

Hi there, I've updated to 0.5.7 and I'm running from cygwin and I get the 
same result. Can rbt be run from cygwin? Here is what I get:


$ rbt post -d -o 299074
DEBUG:root:Checking for a Subversion repository...
DEBUG:root:Checking for a Git repository...
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:Checking for a Plastic repository...
DEBUG:root:Checking for a ClearCase repository...
DEBUG:root:Checking for a Bazaar repository...
ERROR:root:The current directory does not contain a checkout from a 
supported source code repository.


On Tuesday, February 4, 2014 1:14:16 PM UTC-8, Karl Nordstrom wrote:
>
> Thanks for the quick fix! 0.5.7 did it.
>
> Karl
>
> On Monday, 3 February 2014 13:50:03 UTC-8, Karl Nordstrom wrote:
>>
>> Okay, looking forward to getting the fix.
>>
>> Thanks,
>> Karl
>>
>> On Monday, 3 February 2014 13:28:17 UTC-8, David Trowbridge wrote:
>>>
>>> Karl,
>>>
>>> It looks like we introduced a regression in 0.5.6 where it only will 
>>> post from the client root. We'll get this sorted out asap.
>>>
>>> -David
>>>
>>>
>>> On Mon, Feb 3, 2014 at 1:17 PM, Karl Nordstrom wrote:
>>>
 I am attempting to generate a diff using rbt diff from a perforce 
 workspace. I get the same error when I do rbt post.

 (Thank you for helping with the previous problem I was having, it 
 appears to be resolved with RBTools 0.5.6.)

 My p4config is as follows:

 P4PORT=stork:1666
 P4USER=knordstrom
 P4CLIENT=knordstrom_passenger

 The p4config appears to be setup correctly. I can do p4 diff from the 
 commandline and generate a diff without errors. Unfortunately, this diff 
 is 
 not in a format that ReviewBoard understands.

 My .reviewboard rc file is as follows (just one line):

 REVIEWBOARD_URL = "http://reviewboard/";

 I have tried the following on the commandline:

 rbt diff -d
 rbt diff -d 25012   (the latest changelist number)
 rbt post -d
 rbt post -d 25012

 In all cases I get the same result:

 DEBUG:root:Checking for a Subversion repository...
 DEBUG:root:Checking for a Git repository...
 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:Checking for a Plastic repository...
 DEBUG:root:Checking for a ClearCase repository...
 DEBUG:root:Checking for a Bazaar repository...
 ERROR:root:The current directory does not contain a checkout from a 
 supported source code repository.

 When I do p4 info it provides relevant information. I'm hesitant to 
 post it here as it shows company specific information.

 Is there something that I need to do in the configuration?

 Is this something to do with the way that Perforce works? As far as I 
 can tell, Perforce works on workspaces (a collection of files that are 
 being edited) rather than directories. That said, I would have thought 
 that 
 RBTools could find it via p4 diff, which references p4config. 

 Ideally, I want to post to reviewboard based on changed files rather 
 than an already committed changelist, but right now any solution would be 
 welcome.

 Does anyone have an example of how to configure RBTools to work with 
 Perforce? I have searched all over and have not found any concrete 
 examples.

 Thanks,
 Karl

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

>>>
>>>

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

Re: Support for Oracle Database

[Dean Berry]

Thanks for the response.

On Friday, August 3, 2012 1:50:31 PM UTC-5, Christian Hammond wrote:

> Hi Dean,
>
> While Django supports Oracle, Django-Evolution (our database schema 
> migration module) does not. We'd welcome a patch that adds it, but at this 
> time, we can't claim Oracle support.
>
> You can always install MySQL separately and use that. It works fine, and 
> is well-tested.
>
> Christian
>
> -- 
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Fri, Aug 3, 2012 at 9:35 AM, Dean Berry  wrote:
>
>> We are using CollabNet Teamforge on Red Hat Linus with a Oracle 
>> database.  Is Review Board compatible with Oracle?  I did not see it listed 
>> in the install doc's, so I'm just trying to confirm.  Thanks! 
>>
>> -- 
>> Want to help the Review Board project? Donate today at 
>> http://www.reviewboard.org/donate/
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> -~--~~~~--~~--~--~---
>> To unsubscribe from this group, send email to 
>> reviewboard+unsubscr...@googlegroups.com
>> For more options, visit this group at 
>> http://groups.google.com/group/reviewboard?hl=en
>
>
>

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

Support for Oracle Database

[Dean Berry]

We are using CollabNet Teamforge on Red Hat Linus with a Oracle database.  
Is Review Board compatible with Oracle?  I did not see it listed in the 
install doc's, so I'm just trying to confirm.  Thanks!

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

At this point, we have gotten past the post-review questions and one
extra where we learned to include the "http://reviewboard"; prefix. I
am handing over to production this week.
We appreciate all your assistance (and patience) getting us here!

Dean

On Apr 20, 10:39 pm, Christian Hammond  wrote:
> It should work on any and all distros.
>
> Can you show me the debug output? It'll help in figuring out what URL is
> being accessed. Likely, it's just a configuration problem.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
> On Wed, Apr 20, 2011 at 9:28 PM, Dean  wrote:
> > So far, everything is working really well with the exception of the
> > client-side post-review tool.
>
> > Is there a list of distributions on which post-review works? In our
> > case, we are hoping the post-review can be used on distros for Fedora
> > 9 - Fedora 12.
>
> > We are seeing the "Error creating review request: HTTP 404 " coming
> > from post-review being used the way the documentation describes in the
> > "Posting Committed Code" section.
>
> > On Apr 16, 8:04 am, Stephen Gallagher 
> > wrote:
> > > On Sat, Apr 16, 2011 at 10:02 AM, Stephen Gallagher <
>
> > > step...@gallagherhome.com> wrote:
>
> > > > On Fri, Apr 15, 2011 at 3:16 PM, Dean  wrote:
>
> > > >> Success! Many thanks! It's now working on a Scientific Linux v6 32-bit
> > > >> prototype box.
> > > >> I expect to have them drive it around a bit and then build a 64-bit
> > > >> server for it.
>
> > > >> I'm heading over to the documentation to see if I can upgrade it to v
> > > >> 1.5.5
>
> > > >> Is there any advice you might have for doing this?
>
> > > > I just pushed the 1.5.5 RPM to the stable repository yesterday, so do
> > 'yum
> > > > update ReviewBoard' and then when that's complete, run 'rb-site upgrade
> > > > /path/to/site' as Christian said.
>
> > > FYI, I usually have the new releases available in the testing repository
> > > within three days of the upstream release, so if you're anxious to move
> > to
> > > the latest and greatest, you can usually do 'yum update
> > > --enablerepo=epel-testing ReviewBoard'.
>
> > > By EPEL policy, updates have to either sit in the epel-testing repo for
> > two
> > > weeks or receive sufficient positive karma in the Fedora Update System.
>
> > --
> > Want to help the Review Board project? Donate today at
> >http://www.reviewboard.org/donate/
> > Happy user? Let us know athttp://www.reviewboard.org/users/
> > -~--~~~~--~~--~--~---
> > To unsubscribe from this group, send email to
> > reviewboard+unsubscr...@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/reviewboard?hl=en

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

So far, everything is working really well with the exception of the
client-side post-review tool.

Is there a list of distributions on which post-review works? In our
case, we are hoping the post-review can be used on distros for Fedora
9 - Fedora 12.

We are seeing the "Error creating review request: HTTP 404 " coming
from post-review being used the way the documentation describes in the
"Posting Committed Code" section.


On Apr 16, 8:04 am, Stephen Gallagher 
wrote:
> On Sat, Apr 16, 2011 at 10:02 AM, Stephen Gallagher <
>
>
>
> step...@gallagherhome.com> wrote:
>
> > On Fri, Apr 15, 2011 at 3:16 PM, Dean  wrote:
>
> >> Success! Many thanks! It's now working on a Scientific Linux v6 32-bit
> >> prototype box.
> >> I expect to have them drive it around a bit and then build a 64-bit
> >> server for it.
>
> >> I'm heading over to the documentation to see if I can upgrade it to v
> >> 1.5.5
>
> >> Is there any advice you might have for doing this?
>
> > I just pushed the 1.5.5 RPM to the stable repository yesterday, so do 'yum
> > update ReviewBoard' and then when that's complete, run 'rb-site upgrade
> > /path/to/site' as Christian said.
>
> FYI, I usually have the new releases available in the testing repository
> within three days of the upstream release, so if you're anxious to move to
> the latest and greatest, you can usually do 'yum update
> --enablerepo=epel-testing ReviewBoard'.
>
> By EPEL policy, updates have to either sit in the epel-testing repo for two
> weeks or receive sufficient positive karma in the Fedora Update System.

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

Success! Many thanks! It's now working on a Scientific Linux v6 32-bit
prototype box.
I expect to have them drive it around a bit and then build a 64-bit
server for it.

I'm heading over to the documentation to see if I can upgrade it to v
1.5.5

Is there any advice you might have for doing this?

On Apr 14, 1:32 am, Gilles Moris  wrote:
> On Thursday 14 April 2011 02:10:42 am Dean wrote:
>
> > After creating a database named reviewboard and creating a UID called
> > "rbadmin" to have full access to it, I added rights for rbadmin to
> > have full rights to it:
>
> > mysql> USE reviewboard;
> > Database changed
> > mysql> GRANT ALL PRIVILEGES ON reviewboard TO 'rbdbuser'@'localhost'
> > IDENTIFIED BY 'password' WITH GRANT OPTION;
> > Query OK, 0 rows affected (0.00 sec)
>
> First you start talking about a "rbadmin" user but then seems to actually
> create and use a "rbdbuser". May be you mixed both ?
>
> Another possibility is that you had a syntax error in your GRANT query. When
> you want to grant access to all tables, the syntax is reviewboard.* . Without
> the ".*", you may just referring to the reviewboard table in the current
> database.
> mysql> GRANT ALL PRIVILEGES ON reviewboard.* TO 'rbdbuser'@'localhost' ...
>
> Regards.
> Gilles.
>
> > Tried to run:
> > rb-site install /var/www/reviewboard
>
> > ...and got:
>
> > * Installing the site...
> > Building site directories ... OK
> > Building site configuration files ... OK
> > Creating database ... Creating table django_admin_log
> > Traceback (most recent call last):
> >   File "/usr/bin/rb-site", line 9, in 
> >     load_entry_point('ReviewBoard==1.5.4', 'console_scripts', 'rb-
> > site')()
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 1626, in main
> >     command.run()
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 1177, in run
> >     self.show_install_status()
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 1436, in show_install_status
> >     site.sync_database)
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 703, in step
> >     func()
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 339, in sync_database
> >     self.run_manage_command("syncdb", params)
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 397, in run_manage_command
> >     execute_manager(reviewboard.settings, [__file__, cmd] + params)
> >   File "/usr/lib/python2.6/site-packages/django/core/management/
> > __init__.py", line 438, in execute_manager
> >     utility.execute()
> >   File "/usr/lib/python2.6/site-packages/django/core/management/
> > __init__.py", line 379, in execute
> >     self.fetch_command(subcommand).run_from_argv(self.argv)
> >   File "/usr/lib/python2.6/site-packages/django/core/management/
> > base.py", line 191, in run_from_argv
> >     self.execute(*args, **options.__dict__)
> >   File "/usr/lib/python2.6/site-packages/django/core/management/
> > base.py", line 220, in execute
> >     output = self.handle(*args, **options)
> >   File "/usr/lib/python2.6/site-packages/django/core/management/
> > base.py", line 351, in handle
> >     return self.handle_noargs(**options)
> >   File "/usr/lib/python2.6/site-packages/django/core/management/
> > commands/syncdb.py", line 99, in handle_noargs
> >     cursor.execute(statement)
> >   File "/usr/lib/python2.6/site-packages/django/db/backends/mysql/
> > base.py", line 86, in execute
> >     return self.cursor.execute(query, args)
> >   File "/usr/lib/python2.6/site-packages/MySQLdb/cursors.py", line
> > 173, in execute
> >     self.errorhandler(self, exc, value)
> >   File "/usr/lib/python2.6/site-packages/MySQLdb/connections.py", line
> > 36, in defaulterrorhandler
> >     raise errorclass, errorvalue
> > _mysql_exceptions.OperationalError: (1142, "CREATE command denied to
> > user 'rbdbuser'@'localhost' for table 'django_admin_log'")
>
> > Thanks for your help.
>
> > What can I fix to finish this correctly?
> > Where can I go to find more granular instructions fo

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

After creating a database named reviewboard and creating a UID called
"rbadmin" to have full access to it, I added rights for rbadmin to
have full rights to it:

mysql> USE reviewboard;
Database changed
mysql> GRANT ALL PRIVILEGES ON reviewboard TO 'rbdbuser'@'localhost'
IDENTIFIED BY 'password' WITH GRANT OPTION;
Query OK, 0 rows affected (0.00 sec)

Tried to run:
rb-site install /var/www/reviewboard

...and got:

* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
Creating database ... Creating table django_admin_log
Traceback (most recent call last):
  File "/usr/bin/rb-site", line 9, in 
load_entry_point('ReviewBoard==1.5.4', 'console_scripts', 'rb-
site')()
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 1626, in main
command.run()
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 1177, in run
self.show_install_status()
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 1436, in show_install_status
site.sync_database)
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 703, in step
func()
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 339, in sync_database
self.run_manage_command("syncdb", params)
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
  File "/usr/lib/python2.6/site-packages/django/core/management/
__init__.py", line 438, in execute_manager
utility.execute()
  File "/usr/lib/python2.6/site-packages/django/core/management/
__init__.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.6/site-packages/django/core/management/
base.py", line 191, in run_from_argv
self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.6/site-packages/django/core/management/
base.py", line 220, in execute
output = self.handle(*args, **options)
  File "/usr/lib/python2.6/site-packages/django/core/management/
base.py", line 351, in handle
return self.handle_noargs(**options)
  File "/usr/lib/python2.6/site-packages/django/core/management/
commands/syncdb.py", line 99, in handle_noargs
cursor.execute(statement)
  File "/usr/lib/python2.6/site-packages/django/db/backends/mysql/
base.py", line 86, in execute
return self.cursor.execute(query, args)
  File "/usr/lib/python2.6/site-packages/MySQLdb/cursors.py", line
173, in execute
self.errorhandler(self, exc, value)
  File "/usr/lib/python2.6/site-packages/MySQLdb/connections.py", line
36, in defaulterrorhandler
raise errorclass, errorvalue
_mysql_exceptions.OperationalError: (1142, "CREATE command denied to
user 'rbdbuser'@'localhost' for table 'django_admin_log'")

Thanks for your help.

What can I fix to finish this correctly?
Where can I go to find more granular instructions for this
installation?
Once I have this test box working, is there a set of instructions I
can find for upgrading it to version 1.5.5?


On Apr 13, 12:30 am, Gilles Moris  wrote:
> On Tuesday 12 April 2011 11:29:54 pm Dean wrote:
>
>
>
> > On SL6:
> > LSB Version:    :core-4.0-ia32:core-4.0-noarch:graphics-4.0-
> > ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch
> > Distributor ID: Scientific
> > Description:    Scientific Linux release 6.0 (Carbon)
> > Release:        6.0
> > Codename:       Carbon
>
> > I added mysql, mysql-server, httpd. I installed the EPEL epel-
> > release-6-5.noarch.rpm.
> > Installed Reviewboard. Installed memcached and MySQL-python and then
> > used:
>
> > rb-site install /var/www/reviewboard...
>
> > and got:
> > * Installing the site...
> > Building site directories ... OK
> > Building site configuration files ... OK
> > Creating database ... Traceback (most recent call last):
> >   File "/usr/bin/rb-site", line 9, in 
> >     load_entry_point('ReviewBoard==1.5.4', 'console_scripts', 'rb-
> > site')()
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 1626, in main
> >     command.run()
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 1177, in run
> >     self.show_install_status()
> >   File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
> > rbsite.py", line 1436, in show_install_status
> > 

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

On SL6:
LSB Version::core-4.0-ia32:core-4.0-noarch:graphics-4.0-
ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch
Distributor ID: Scientific
Description:Scientific Linux release 6.0 (Carbon)
Release:6.0
Codename:   Carbon

I added mysql, mysql-server, httpd. I installed the EPEL epel-
release-6-5.noarch.rpm.
Installed Reviewboard. Installed memcached and MySQL-python and then
used:

rb-site install /var/www/reviewboard...

and got:
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
Creating database ... Traceback (most recent call last):
  File "/usr/bin/rb-site", line 9, in 
load_entry_point('ReviewBoard==1.5.4', 'console_scripts', 'rb-
site')()
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 1626, in main
command.run()
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 1177, in run
self.show_install_status()
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 1436, in show_install_status
site.sync_database)
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 703, in step
func()
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 339, in sync_database
self.run_manage_command("syncdb", params)
  File "/usr/lib/python2.6/site-packages/reviewboard/cmdline/
rbsite.py", line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
  File "/usr/lib/python2.6/site-packages/django/core/management/
__init__.py", line 438, in execute_manager
utility.execute()
  File "/usr/lib/python2.6/site-packages/django/core/management/
__init__.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.6/site-packages/django/core/management/
base.py", line 191, in run_from_argv
self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.6/site-packages/django/core/management/
base.py", line 219, in execute
self.validate()
  File "/usr/lib/python2.6/site-packages/django/core/management/
base.py", line 249, in validate
num_errors = get_validation_errors(s, app)
  File "/usr/lib/python2.6/site-packages/django/core/management/
validation.py", line 102, in get_validation_errors
connection.validation.validate_field(e, opts, f)
  File "/usr/lib/python2.6/site-packages/django/db/backends/mysql/
validation.py", line 14, in validate_field
db_version = self.connection.get_server_version()
  File "/usr/lib/python2.6/site-packages/django/db/backends/mysql/
base.py", line 313, in get_server_version
self.cursor()
  File "/usr/lib/python2.6/site-packages/django/db/backends/
__init__.py", line 75, in cursor
cursor = self._cursor()
  File "/usr/lib/python2.6/site-packages/django/db/backends/mysql/
base.py", line 297, in _cursor
self.connection = Database.connect(**kwargs)
  File "/usr/lib/python2.6/site-packages/MySQLdb/__init__.py", line
81, in Connect
return Connection(*args, **kwargs)
  File "/usr/lib/python2.6/site-packages/MySQLdb/connections.py", line
187, in __init__
super(Connection, self).__init__(*args, **kwargs2)
_mysql_exceptions.OperationalError: (1049, "Unknown database
'reviewboard'")

This was a test run on a 3GB RAM machine with a fresh install of SL v
6 for i386. Am I still missing something?

Thanks for your help.

On Apr 12, 5:11 am, Stephen Gallagher 
wrote:
> On Tue, Apr 12, 2011 at 2:38 AM, Dean  wrote:
> > Ah Ha! I'd been waiting for Centos 6.  How do you guess I might do
> > with Scientific Linux 6 in 64-bit?
>
> Well, in theory Scientific Linux is identical to RHEL 6 (just recompiled),
> so I suspect it should work just fine.

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

Ah Ha! I'd been waiting for Centos 6.  How do you guess I might do
with Scientific Linux 6 in 64-bit?

On Apr 11, 6:59 pm, Stephen Gallagher 
wrote:
> > * Required modules are missing
>
> >    You are missing Python modules that are needed before the
> >    installation process. You will need to install the necessary
> >    modules and restart the install.
>
> >    Databases (required):
> >        * sqlite3 (pysqlite2, sqlite3)
> >        * MySQL (MySQLdb)
> >        * PostgreSQL (psycopg2)
>
> > Do I start here with some way to install the python-mysqldb ?
> > After that, will the rb-site drop Reviewboard recommended information
> > for configuration data in a file in /etc/httpd/config.d ?
>
> The package you're looking for is
> MySQL-python.
> Unfortunately, I just remembered 
> abouthttps://partner-bugzilla.redhat.com/show_bug.cgi?id=555868which means 
> that
> the version shipped in RHEL 5 (and CentOS) is too old for use with Django
> and ReviewBoard right now. So you'll probably need to rebuild this package
> with version 1.2.1p2 or later. Probably the easiest way to accomplish this
> would be to 
> downloadhttp://kojipkgs.fedoraproject.org/packages/MySQL-python/1.2.3/1.fc14/...
> then use 'rpmbuild --rebuild ' to rebuild it for your platform.
> ('yum-builddep ' is also useful for installing any prerequisites
> needed for building)

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

I went back through my notes and backed out everything I had installed
following the original install instructions and then added the EPEL
repo. The EPEL repo and its ReviewBoard installed smoothly. I found
that I needed to re-install mysql-server. That completed, I set the
permissions on the mysql db and started at the rb-install script
again:

# rb-site install /var/www/reviewboard


* Welcome to the Review Board site installation wizard

This will prepare a Review Board site installation in:

/var/www/reviewboard

We need to know a few things before we can prepare your site for
installation. This will only take a few minutes.


* Required modules are missing

You are missing Python modules that are needed before the
installation process. You will need to install the necessary
modules and restart the install.

Databases (required):
* sqlite3 (pysqlite2, sqlite3)
* MySQL (MySQLdb)
* PostgreSQL (psycopg2)

Do I start here with some way to install the python-mysqldb ?
After that, will the rb-site drop Reviewboard recommended information
for configuration data in a file in /etc/httpd/config.d ?

On Apr 8, 9:59 am, Stephen Gallagher 
wrote:
> On 04/08/2011 11:57 AM, Dean wrote:> If I use this method (very attractive) 
> do you recommend I back out the
> > steps I've made prior to using your yum/rpm install?
>
> It's always a good idea to start from a clean state, yes. However
> RPM/yum *should* be able to handle things for you here.

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

If I use this method (very attractive) do you recommend I back out the
steps I've made prior to using your yum/rpm install?

On Apr 8, 6:20 am, Stephen Gallagher 
wrote:
> On 04/07/2011 07:02 PM, Dean wrote:
>
> > I'm following the v1.5 admin installation doc, and ran into trouble on
> > the "mysql-python" step.
> > I've been installing as root, and am down to wondering if there are
> > environment setting I have omitted because everybody know python but
> > me...
>
> Make your life easier: use the pre-build ReviewBoard RPMs I created for
> EPEL 5.
>
> Add the EPEL repository (instructions 
> here:http://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F)
>
> Then 'yum install ReviewBoard' and you'll get everything you need. No
> need to use easy_install or understand python.

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: installing Reviewboard on Centos 5.5 64-bit

[Dean]

Thanks! I'll report back on progress.

On Apr 7, 5:07 pm, David Trowbridge  wrote:
> It looks like you need to install a -devel package for mysql in order to get
> the headers.
>
> -David
>
> On Thu, Apr 7, 2011 at 4:02 PM, Dean  wrote:
> > I'm following the v1.5 admin installation doc, and ran into trouble on
> > the "mysql-python" step.
> > I've been installing as root, and am down to wondering if there are
> > environment setting I have omitted because everybody know python but
> > me...
>
> > I get these errors:
>
> > easy_install mysql-python
> > Searching for mysql-python
> > Readinghttp://pypi.python.org/simple/mysql-python/
> > Readinghttp://sourceforge.net/projects/mysql-python/
> > Readinghttp://sourceforge.net/projects/mysql-python
> > Best match: MySQL-python 1.2.3
> > Downloading
> >http://download.sourceforge.net/sourceforge/mysql-python/MySQL-python...
> > Processing MySQL-python-1.2.3.tar.gz
> > Running MySQL-python-1.2.3/setup.py -q bdist_egg --dist-dir /tmp/
> > easy_install-nX4ESs/MySQL-python-1.2.3/egg-dist-tmp-mHwDDq
> > warning: no files found matching 'MANIFEST'
> > warning: no files found matching 'ChangeLog'
> > warning: no files found matching 'GPL'
> > _mysql.c:36:23: error: my_config.h: No such file or directory
> > _mysql.c:38:19: error: mysql.h: No such file or directory
> > _mysql.c:39:26: error: mysqld_error.h: No such file or directory
> > _mysql.c:40:20: error: errmsg.h: No such file or directory
> > _mysql.c:76: error: expected specifier-qualifier-list before ‘MYSQL’
> > _mysql.c:90: error: expected specifier-qualifier-list before
> > ‘MYSQL_RES’
> > _mysql.c: In function ‘_mysql_Exception’:
> > _mysql.c:120: warning: implicit declaration of function ‘mysql_errno’
> > _mysql.c:120: error: ‘_mysql_ConnectionObject’ has no member named
> > ‘connection’
> > _mysql.c:123: error: ‘CR_MAX_ERROR’ undeclared (first use in this
> > function)
> > _mysql.c:123: error: (Each undeclared identifier is reported only once
> > _mysql.c:123: error: for each function it appears in.)
> > _mysql.c:131: error: ‘CR_COMMANDS_OUT_OF_SYNC’ undeclared (first use
> > in this function)
> > _mysql.c:132: error: ‘ER_DB_CREATE_EXISTS’ undeclared (first use in
> > this function)
> > _mysql.c:133: error: ‘ER_SYNTAX_ERROR’ undeclared (first use in this
> > function)
> > _mysql.c:134: error: ‘ER_PARSE_ERROR’ undeclared (first use in this
> > function)
> > _mysql.c:135: error: ‘ER_NO_SUCH_TABLE’ undeclared (first use in this
> > function)
> > _mysql.c:136: error: ‘ER_WRONG_DB_NAME’ undeclared (first use in this
> > function)
> > _mysql.c:137: error: ‘ER_WRONG_TABLE_NAME’ undeclared (first use in
> > this function)
> > _mysql.c:138: error: ‘ER_FIELD_SPECIFIED_TWICE’ undeclared (first use
> > in this function)
> > _mysql.c:139: error: ‘ER_INVALID_GROUP_FUNC_USE’ undeclared (first use
> > in this function)
> > _mysql.c:140: error: ‘ER_UNSUPPORTED_EXTENSION’ undeclared (first use
> > in this function)
> > _mysql.c:141: error: ‘ER_TABLE_MUST_HAVE_COLUMNS’ undeclared (first
> > use in this function)
> > _mysql.c:170: error: ‘ER_DUP_ENTRY’ undeclared (first use in this
> > function)
> > _mysql.c:213: warning: implicit declaration of function ‘mysql_error’
> > _mysql.c:213: error: ‘_mysql_ConnectionObject’ has no member named
> > ‘connection’
> > _mysql.c:213: warning: passing argument 1 of ‘PyString_FromString’
> > makes pointer from integer without a cast
> > _mysql.c: In function ‘_mysql_server_init’:
> > _mysql.c:308: warning: label ‘finish’ defined but not used
> > _mysql.c:234: warning: unused variable ‘item’
> > _mysql.c:233: warning: unused variable ‘groupc’
> > _mysql.c:233: warning: unused variable ‘i’
> > _mysql.c:233: warning: unused variable ‘cmd_argc’
> > _mysql.c:232: warning: unused variable ‘s’
> > _mysql.c: In function ‘_mysql_ResultObject_Initialize’:
> > _mysql.c:363: error: ‘MYSQL_RES’ undeclared (first use in this
> > function)
> > _mysql.c:363: error: ‘result’ undeclared (first use in this function)
> > _mysql.c:368: error: ‘MYSQL_FIELD’ undeclared (first use in this
> > function)
> > _mysql.c:368: error: ‘fields’ undeclared (first use in this function)
> > _mysql.c:377: error: ‘_mysql_ResultObject’ has no member named ‘use’
> > _mysql.c:380: warning: implicit declaration of function
> > ‘mysql_use_result’
> > _mysql.c:380: error: ‘_mysql_ConnectionObject’ has no member named
> > ‘connection’
> > _mysql.c:382: warning

installing Reviewboard on Centos 5.5 64-bit

[Dean]

I'm following the v1.5 admin installation doc, and ran into trouble on
the "mysql-python" step.
I've been installing as root, and am down to wondering if there are
environment setting I have omitted because everybody know python but
me...

I get these errors:

easy_install mysql-python
Searching for mysql-python
Reading http://pypi.python.org/simple/mysql-python/
Reading http://sourceforge.net/projects/mysql-python/
Reading http://sourceforge.net/projects/mysql-python
Best match: MySQL-python 1.2.3
Downloading 
http://download.sourceforge.net/sourceforge/mysql-python/MySQL-python-1.2.3.tar.gz
Processing MySQL-python-1.2.3.tar.gz
Running MySQL-python-1.2.3/setup.py -q bdist_egg --dist-dir /tmp/
easy_install-nX4ESs/MySQL-python-1.2.3/egg-dist-tmp-mHwDDq
warning: no files found matching 'MANIFEST'
warning: no files found matching 'ChangeLog'
warning: no files found matching 'GPL'
_mysql.c:36:23: error: my_config.h: No such file or directory
_mysql.c:38:19: error: mysql.h: No such file or directory
_mysql.c:39:26: error: mysqld_error.h: No such file or directory
_mysql.c:40:20: error: errmsg.h: No such file or directory
_mysql.c:76: error: expected specifier-qualifier-list before ‘MYSQL’
_mysql.c:90: error: expected specifier-qualifier-list before
‘MYSQL_RES’
_mysql.c: In function ‘_mysql_Exception’:
_mysql.c:120: warning: implicit declaration of function ‘mysql_errno’
_mysql.c:120: error: ‘_mysql_ConnectionObject’ has no member named
‘connection’
_mysql.c:123: error: ‘CR_MAX_ERROR’ undeclared (first use in this
function)
_mysql.c:123: error: (Each undeclared identifier is reported only once
_mysql.c:123: error: for each function it appears in.)
_mysql.c:131: error: ‘CR_COMMANDS_OUT_OF_SYNC’ undeclared (first use
in this function)
_mysql.c:132: error: ‘ER_DB_CREATE_EXISTS’ undeclared (first use in
this function)
_mysql.c:133: error: ‘ER_SYNTAX_ERROR’ undeclared (first use in this
function)
_mysql.c:134: error: ‘ER_PARSE_ERROR’ undeclared (first use in this
function)
_mysql.c:135: error: ‘ER_NO_SUCH_TABLE’ undeclared (first use in this
function)
_mysql.c:136: error: ‘ER_WRONG_DB_NAME’ undeclared (first use in this
function)
_mysql.c:137: error: ‘ER_WRONG_TABLE_NAME’ undeclared (first use in
this function)
_mysql.c:138: error: ‘ER_FIELD_SPECIFIED_TWICE’ undeclared (first use
in this function)
_mysql.c:139: error: ‘ER_INVALID_GROUP_FUNC_USE’ undeclared (first use
in this function)
_mysql.c:140: error: ‘ER_UNSUPPORTED_EXTENSION’ undeclared (first use
in this function)
_mysql.c:141: error: ‘ER_TABLE_MUST_HAVE_COLUMNS’ undeclared (first
use in this function)
_mysql.c:170: error: ‘ER_DUP_ENTRY’ undeclared (first use in this
function)
_mysql.c:213: warning: implicit declaration of function ‘mysql_error’
_mysql.c:213: error: ‘_mysql_ConnectionObject’ has no member named
‘connection’
_mysql.c:213: warning: passing argument 1 of ‘PyString_FromString’
makes pointer from integer without a cast
_mysql.c: In function ‘_mysql_server_init’:
_mysql.c:308: warning: label ‘finish’ defined but not used
_mysql.c:234: warning: unused variable ‘item’
_mysql.c:233: warning: unused variable ‘groupc’
_mysql.c:233: warning: unused variable ‘i’
_mysql.c:233: warning: unused variable ‘cmd_argc’
_mysql.c:232: warning: unused variable ‘s’
_mysql.c: In function ‘_mysql_ResultObject_Initialize’:
_mysql.c:363: error: ‘MYSQL_RES’ undeclared (first use in this
function)
_mysql.c:363: error: ‘result’ undeclared (first use in this function)
_mysql.c:368: error: ‘MYSQL_FIELD’ undeclared (first use in this
function)
_mysql.c:368: error: ‘fields’ undeclared (first use in this function)
_mysql.c:377: error: ‘_mysql_ResultObject’ has no member named ‘use’
_mysql.c:380: warning: implicit declaration of function
‘mysql_use_result’
_mysql.c:380: error: ‘_mysql_ConnectionObject’ has no member named
‘connection’
_mysql.c:382: warning: implicit declaration of function
‘mysql_store_result’
_mysql.c:382: error: ‘_mysql_ConnectionObject’ has no member named
‘connection’
_mysql.c:383: error: ‘_mysql_ResultObject’ has no member named
‘result’
_mysql.c:386: error: ‘_mysql_ResultObject’ has no member named
‘converter’
_mysql.c:389: warning: implicit declaration of function
‘mysql_num_fields’
_mysql.c:390: error: ‘_mysql_ResultObject’ has no member named
‘nfields’
_mysql.c:391: error: ‘_mysql_ResultObject’ has no member named
‘converter’
_mysql.c:392: warning: implicit declaration of function
‘mysql_fetch_fields’
_mysql.c:438: error: ‘_mysql_ResultObject’ has no member named
‘converter’
_mysql.c: In function ‘_mysql_ResultObject_traverse’:
_mysql.c:450: error: ‘_mysql_ResultObject’ has no member named
‘converter’
_mysql.c:451: error: ‘_mysql_ResultObject’ has no member named
‘converter’
_mysql.c: In function ‘_mysql_ResultObject_clear’:
_mysql.c:462: error: ‘_mysql_ResultObject’ has no member named
‘converter’
_mysql.c:462: error: ‘_mysql_ResultObject’ has no member named
‘converter’
_mysql.c:462: error: ‘_mysql_ResultObject’ has no member named
‘converter’
_mysql.c:

reviewboard.settings and exporting db

[Dean]

I do not think we ran any install scripts for reviewboard when
following the Getting Started and Ubuntu instructions... So I have
some questions:
1) Can I run "ez_setup.py" or "setup.py" now without damaging the data
we have been playing with?

2) If not, what might I have missed in the instructions to create the
reviewboard.settings and sample apache2 conf files?

3) Once we have worked with Reviewboard for a bit and decided we want
to move it into production, what procedure I can use to export our
data from sqlite in order to migrate it to mysql?

Our setup: Fedora8, /usr/lib/python2.5, django Revision: 8471,
reviewboard Revision: 1453.

Thanks for your help,

Dean
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---