Re: unable to save seach index path

2011-02-12 Thread Cristian Andreica
Fun fact: I've made it work :D

I wanted to upgrade to the latest review board and change the server.
So I copied the sqlite db file and reused it in the new instalation.
It solved the error I previously described.

Thank you. Enjoy the weekend, Christian!

On Feb 12, 12:43 pm, Cristian Andreica 
wrote:
> You are correct. The site settings can now be saved.
>
> I installed PyLucene in order to use the search index feature. I
> selected the checkbox to enable search. According to the documentation
> posted online, I have to run the command  reviewboard index -- --full> in order to perform a full index.
>
> This commands raises the following error:
>
> Traceback (most recent call last):
>   File "/usr/bin/rb-site", line 8, in 
>     load_entry_point('ReviewBoard==1.5.3.1', 'console_scripts', 'rb-
> site')()
>   File "/usr/lib/python2.5/site-packages/ReviewBoard-1.5.3.1-py2.5.egg/
> reviewboard/cmdline/rbsite.py", line 1611, in main
>     command.run()
>   File "/usr/lib/python2.5/site-packages/ReviewBoard-1.5.3.1-py2.5.egg/
> reviewboard/cmdline/rbsite.py", line 1545, in run
>     site.run_manage_command(args[0], args[1:])
>   File "/usr/lib/python2.5/site-packages/ReviewBoard-1.5.3.1-py2.5.egg/
> reviewboard/cmdline/rbsite.py", line 397, in run_manage_command
>     execute_manager(reviewboard.settings, [__file__, cmd] + params)
>   File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
> core/management/__init__.py", line 438, in execute_manager
>     utility.execute()
>   File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
> core/management/__init__.py", line 379, in execute
>     self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
> core/management/base.py", line 191, in run_from_argv
>     self.execute(*args, **options.__dict__)
>   File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
> core/management/base.py", line 220, in execute
>     output = self.handle(*args, **options)
>   File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
> core/management/base.py", line 351, in handle
>     return self.handle_noargs(**options)
>   File "/usr/lib/python2.5/site-packages/ReviewBoard-1.5.3.1-py2.5.egg/
> reviewboard/reviews/management/commands/index.py", line 55, in
> handle_noargs
>     if not os.path.exists(store_dir):
>   File "/usr/lib/python2.5/posixpath.py", line 171, in exists
>     st = os.stat(path)
> TypeError: coercing to Unicode: need string or buffer, NoneType found
>
> Cristian Andreica
>
> On Feb 12, 12:00 pm, Christian Hammond  wrote:> What 
> error are you seeing? The fix that went in was to fix the validation
> > errors in the admin UI, which prevented site settings from being saved.
> > Nothing changed for the 'index' command, which hasn't had any code changes
> > in many releases.
>
> > Christian
>
> > --
> > Christian Hammond - chip...@chipx86.com
> > Review Board -http://www.reviewboard.org
> > VMware, Inc. -http://www.vmware.com
>
> > On Sat, Feb 12, 2011 at 1:50 AM, Cristian Andreica <
>
> > cristianandre...@gmail.com> wrote:
> > > I've upgraded reviewboard to 1.5.3.1, but the command  > > var/www/reviewboard index -- --full> throws the same error.
>
> > > I even tried creating a /site/search-index/index file owned by www-
> > > data user. The path is accesible by the user. Still, the command
> > > fails.
>
> > > Cristian Andreica
>
> > > On Feb 11, 10:42 pm, Christian Hammond  wrote:
> > > > My apologies, this wasn't sufficient due to another bug where it doesn't
> > > > even save the entry. I've put out a hot-fix release (1.5.3.1) which you
> > > > should be able to upgrade to in the normal manner. It will fix this.
>
> > > > Christian
>
> > > > --
> > > > Christian Hammond - chip...@chipx86.com
> > > > Review Board -http://www.reviewboard.org
> > > > VMware, Inc. -http://www.vmware.com
>
> > > > On Fri, Feb 11, 2011 at 12:36 PM, Christian Hammond  > > >wrote:
>
> > > > > Hi Jerry,
>
> > > > > I've fixed this in our repository and will be doing a release this
> > > weekend.
> > > > > There is a workaround, though.
>
> > > > > Create an empty file somewhere in a writable directory (your site's
> > > data/
> > > > > directory is good or this) and then set the Search Index field to be 
> > > > > an
> > > > > absolute path to that file. The validation should then work.
>
> > > > > Christian
>
> > > > > --
> > > > > Christian Hammond - chip...@chipx86.com
>
> > > > > Review Board -http://www.reviewboard.org
> > > > > VMware, Inc. -http://www.vmware.com
>
> > > > > On Thu, Feb 10, 2011 at 10:41 AM, Jerry 
> > > wrote:
>
> > > > >> I'm prevented from saving settings unrelated to this, but on the same
> > > > >> page.  I tried to change my time zone and, despite having the "Enable
> > > > >> Search" option unchecked, I still got the error message "Search index
> > > > >> path should be absolute" after clicking "Save".  My time zone setting
> > > > >> i

Re: unable to save seach index path

2011-02-12 Thread Cristian Andreica
You are correct. The site settings can now be saved.

I installed PyLucene in order to use the search index feature. I
selected the checkbox to enable search. According to the documentation
posted online, I have to run the command  in order to perform a full index.

This commands raises the following error:

Traceback (most recent call last):
  File "/usr/bin/rb-site", line 8, in 
load_entry_point('ReviewBoard==1.5.3.1', 'console_scripts', 'rb-
site')()
  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.5.3.1-py2.5.egg/
reviewboard/cmdline/rbsite.py", line 1611, in main
command.run()
  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.5.3.1-py2.5.egg/
reviewboard/cmdline/rbsite.py", line 1545, in run
site.run_manage_command(args[0], args[1:])
  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.5.3.1-py2.5.egg/
reviewboard/cmdline/rbsite.py", line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
  File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
core/management/__init__.py", line 438, in execute_manager
utility.execute()
  File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
core/management/__init__.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
core/management/base.py", line 191, in run_from_argv
self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
core/management/base.py", line 220, in execute
output = self.handle(*args, **options)
  File "/usr/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg/django/
core/management/base.py", line 351, in handle
return self.handle_noargs(**options)
  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.5.3.1-py2.5.egg/
reviewboard/reviews/management/commands/index.py", line 55, in
handle_noargs
if not os.path.exists(store_dir):
  File "/usr/lib/python2.5/posixpath.py", line 171, in exists
st = os.stat(path)
TypeError: coercing to Unicode: need string or buffer, NoneType found

Cristian Andreica

On Feb 12, 12:00 pm, Christian Hammond  wrote:
> What error are you seeing? The fix that went in was to fix the validation
> errors in the admin UI, which prevented site settings from being saved.
> Nothing changed for the 'index' command, which hasn't had any code changes
> in many releases.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
> On Sat, Feb 12, 2011 at 1:50 AM, Cristian Andreica <
>
>
>
>
>
>
>
> cristianandre...@gmail.com> wrote:
> > I've upgraded reviewboard to 1.5.3.1, but the command  > var/www/reviewboard index -- --full> throws the same error.
>
> > I even tried creating a /site/search-index/index file owned by www-
> > data user. The path is accesible by the user. Still, the command
> > fails.
>
> > Cristian Andreica
>
> > On Feb 11, 10:42 pm, Christian Hammond  wrote:
> > > My apologies, this wasn't sufficient due to another bug where it doesn't
> > > even save the entry. I've put out a hot-fix release (1.5.3.1) which you
> > > should be able to upgrade to in the normal manner. It will fix this.
>
> > > Christian
>
> > > --
> > > Christian Hammond - chip...@chipx86.com
> > > Review Board -http://www.reviewboard.org
> > > VMware, Inc. -http://www.vmware.com
>
> > > On Fri, Feb 11, 2011 at 12:36 PM, Christian Hammond  > >wrote:
>
> > > > Hi Jerry,
>
> > > > I've fixed this in our repository and will be doing a release this
> > weekend.
> > > > There is a workaround, though.
>
> > > > Create an empty file somewhere in a writable directory (your site's
> > data/
> > > > directory is good or this) and then set the Search Index field to be an
> > > > absolute path to that file. The validation should then work.
>
> > > > Christian
>
> > > > --
> > > > Christian Hammond - chip...@chipx86.com
>
> > > > Review Board -http://www.reviewboard.org
> > > > VMware, Inc. -http://www.vmware.com
>
> > > > On Thu, Feb 10, 2011 at 10:41 AM, Jerry 
> > wrote:
>
> > > >> I'm prevented from saving settings unrelated to this, but on the same
> > > >> page.  I tried to change my time zone and, despite having the "Enable
> > > >> Search" option unchecked, I still got the error message "Search index
> > > >> path should be absolute" after clicking "Save".  My time zone setting
> > > >> is unchanged after this.
>
> > > >> -- Jerry
>
> > > >> On Feb 9, 9:04 pm, Christian Hammond  wrote:
> > > >> > Hi Henry,
>
> > > >> > I doubt you screwed anything up by not doing rb-site upgrade. It's
> > > >> likely a
> > > >> > flaw in the new validation logic. I'll see if I can work around this
> > and
> > > >> get
> > > >> > you a patch tonight.
>
> > > >> > Christian
>
> > > >> > --
> > > >> > Christian Hammond - chip...@chipx86.com
> > > >> > Review Board -http://www.reviewboard.org
> > > >> > VMware, Inc. 

Re: unable to save seach index path

2011-02-12 Thread Christian Hammond
What error are you seeing? The fix that went in was to fix the validation
errors in the admin UI, which prevented site settings from being saved.
Nothing changed for the 'index' command, which hasn't had any code changes
in many releases.

Christian

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


On Sat, Feb 12, 2011 at 1:50 AM, Cristian Andreica <
cristianandre...@gmail.com> wrote:

> I've upgraded reviewboard to 1.5.3.1, but the command  var/www/reviewboard index -- --full> throws the same error.
>
> I even tried creating a /site/search-index/index file owned by www-
> data user. The path is accesible by the user. Still, the command
> fails.
>
> Cristian Andreica
>
> On Feb 11, 10:42 pm, Christian Hammond  wrote:
> > My apologies, this wasn't sufficient due to another bug where it doesn't
> > even save the entry. I've put out a hot-fix release (1.5.3.1) which you
> > should be able to upgrade to in the normal manner. It will fix this.
> >
> > Christian
> >
> > --
> > Christian Hammond - chip...@chipx86.com
> > Review Board -http://www.reviewboard.org
> > VMware, Inc. -http://www.vmware.com
> >
> > On Fri, Feb 11, 2011 at 12:36 PM, Christian Hammond  >wrote:
> >
> >
> >
> >
> >
> >
> >
> > > Hi Jerry,
> >
> > > I've fixed this in our repository and will be doing a release this
> weekend.
> > > There is a workaround, though.
> >
> > > Create an empty file somewhere in a writable directory (your site's
> data/
> > > directory is good or this) and then set the Search Index field to be an
> > > absolute path to that file. The validation should then work.
> >
> > > Christian
> >
> > > --
> > > Christian Hammond - chip...@chipx86.com
> >
> > > Review Board -http://www.reviewboard.org
> > > VMware, Inc. -http://www.vmware.com
> >
> > > On Thu, Feb 10, 2011 at 10:41 AM, Jerry 
> wrote:
> >
> > >> I'm prevented from saving settings unrelated to this, but on the same
> > >> page.  I tried to change my time zone and, despite having the "Enable
> > >> Search" option unchecked, I still got the error message "Search index
> > >> path should be absolute" after clicking "Save".  My time zone setting
> > >> is unchanged after this.
> >
> > >> -- Jerry
> >
> > >> On Feb 9, 9:04 pm, Christian Hammond  wrote:
> > >> > Hi Henry,
> >
> > >> > I doubt you screwed anything up by not doing rb-site upgrade. It's
> > >> likely a
> > >> > flaw in the new validation logic. I'll see if I can work around this
> and
> > >> get
> > >> > you a patch tonight.
> >
> > >> > Christian
> >
> > >> > --
> > >> > Christian Hammond - chip...@chipx86.com
> > >> > Review Board -http://www.reviewboard.org
> > >> > VMware, Inc. -http://www.vmware.com
> >
> > >> > On Wed, Feb 9, 2011 at 5:46 PM, Henry Yei 
> wrote:
> > >> > > After upgrading from 1.5.2 to 1.5.3, I am unable to save the path
> of
> > >> > > the search index file. Has anyone else hit this problem, or is
> > >> > > specific to my configuration?
> >
> > >> > > The path validation seems to work, but after the path is saved,
> the
> > >> > > path  does not appear in the Admin UI under the Settings->General
> > >> > > section and that field is blank.
> >
> > >> > > The command rb-site manage /var/www/reviewboard index -- --full
> throws
> > >> > > an exception which seems to show that there is no value saved in
> the
> > >> > > variable store_dir which is initialized by that search_index_file
> > >> > > variable:
> >
> > >> > > sh-4.1$ rb-site manage /var/www/reviewboard/ index -- --full
> > >> > > Traceback (most recent call last):
> > >> > >  File "/usr/local/bin/rb-site", line 9, in 
> > >> > >load_entry_point('ReviewBoard==1.5.3', 'console_scripts', 'rb-
> > >> > > site')()
> > >> > >  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.3-
> > >> > > py2.6.egg/reviewboard/cmdline/rbsite.py", line 1611, in main
> >
> > >> > > command.run()
> > >> > >  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.3-
> > >> > > py2.6.egg/reviewboard/cmdline/rbsite.py", line 1545, in run
> > >> > >site.run_manage_command(args[0],
> > >> > > args[1:])
> > >> > >  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.3-
> > >> > > py2.6.egg/reviewboard/cmdline/rbsite.py", line 397, in
> > >> > > run_manage_command
> > >> > >execute_manager(reviewboard.settings, [__file__, cmd] +
> > >> > > params)
> > >> > >  File
> "/usr/local/lib/python2.6/dist-packages/Django-1.2.4-py2.6.egg/
> > >> > > django/core/management/__init__.py", line 438, in execute_manager
> >
> > >> > > utility.execute()
> > >> > >  File
> "/usr/local/lib/python2.6/dist-packages/Django-1.2.4-py2.6.egg/
> > >> > > django/core/management/__init__.py", line 379, in execute
> >
> > >> > > self.fetch_command(subcommand).run_from_argv(self.argv)
> > >> > >  File
> "/usr/local/lib/python2.6/dist-packages/Django-1.2.4-py2.6.egg/
> > >> > > django/core/management/base.py", line 191, in run_from_argv
> > >> > >self.execute(*args,
>

Re: unable to save seach index path

2011-02-12 Thread Cristian Andreica
I've upgraded reviewboard to 1.5.3.1, but the command  throws the same error.

I even tried creating a /site/search-index/index file owned by www-
data user. The path is accesible by the user. Still, the command
fails.

Cristian Andreica

On Feb 11, 10:42 pm, Christian Hammond  wrote:
> My apologies, this wasn't sufficient due to another bug where it doesn't
> even save the entry. I've put out a hot-fix release (1.5.3.1) which you
> should be able to upgrade to in the normal manner. It will fix this.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
> On Fri, Feb 11, 2011 at 12:36 PM, Christian Hammond 
> wrote:
>
>
>
>
>
>
>
> > Hi Jerry,
>
> > I've fixed this in our repository and will be doing a release this weekend.
> > There is a workaround, though.
>
> > Create an empty file somewhere in a writable directory (your site's data/
> > directory is good or this) and then set the Search Index field to be an
> > absolute path to that file. The validation should then work.
>
> > Christian
>
> > --
> > Christian Hammond - chip...@chipx86.com
>
> > Review Board -http://www.reviewboard.org
> > VMware, Inc. -http://www.vmware.com
>
> > On Thu, Feb 10, 2011 at 10:41 AM, Jerry  wrote:
>
> >> I'm prevented from saving settings unrelated to this, but on the same
> >> page.  I tried to change my time zone and, despite having the "Enable
> >> Search" option unchecked, I still got the error message "Search index
> >> path should be absolute" after clicking "Save".  My time zone setting
> >> is unchanged after this.
>
> >> -- Jerry
>
> >> On Feb 9, 9:04 pm, Christian Hammond  wrote:
> >> > Hi Henry,
>
> >> > I doubt you screwed anything up by not doing rb-site upgrade. It's
> >> likely a
> >> > flaw in the new validation logic. I'll see if I can work around this and
> >> get
> >> > you a patch tonight.
>
> >> > Christian
>
> >> > --
> >> > Christian Hammond - chip...@chipx86.com
> >> > Review Board -http://www.reviewboard.org
> >> > VMware, Inc. -http://www.vmware.com
>
> >> > On Wed, Feb 9, 2011 at 5:46 PM, Henry Yei  wrote:
> >> > > After upgrading from 1.5.2 to 1.5.3, I am unable to save the path of
> >> > > the search index file. Has anyone else hit this problem, or is
> >> > > specific to my configuration?
>
> >> > > The path validation seems to work, but after the path is saved, the
> >> > > path  does not appear in the Admin UI under the Settings->General
> >> > > section and that field is blank.
>
> >> > > The command rb-site manage /var/www/reviewboard index -- --full throws
> >> > > an exception which seems to show that there is no value saved in the
> >> > > variable store_dir which is initialized by that search_index_file
> >> > > variable:
>
> >> > > sh-4.1$ rb-site manage /var/www/reviewboard/ index -- --full
> >> > > Traceback (most recent call last):
> >> > >  File "/usr/local/bin/rb-site", line 9, in 
> >> > >    load_entry_point('ReviewBoard==1.5.3', 'console_scripts', 'rb-
> >> > > site')()
> >> > >  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.3-
> >> > > py2.6.egg/reviewboard/cmdline/rbsite.py", line 1611, in main
>
> >> > > command.run()
> >> > >  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.3-
> >> > > py2.6.egg/reviewboard/cmdline/rbsite.py", line 1545, in run
> >> > >    site.run_manage_command(args[0],
> >> > > args[1:])
> >> > >  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.3-
> >> > > py2.6.egg/reviewboard/cmdline/rbsite.py", line 397, in
> >> > > run_manage_command
> >> > >    execute_manager(reviewboard.settings, [__file__, cmd] +
> >> > > params)
> >> > >  File "/usr/local/lib/python2.6/dist-packages/Django-1.2.4-py2.6.egg/
> >> > > django/core/management/__init__.py", line 438, in execute_manager
>
> >> > > utility.execute()
> >> > >  File "/usr/local/lib/python2.6/dist-packages/Django-1.2.4-py2.6.egg/
> >> > > django/core/management/__init__.py", line 379, in execute
>
> >> > > self.fetch_command(subcommand).run_from_argv(self.argv)
> >> > >  File "/usr/local/lib/python2.6/dist-packages/Django-1.2.4-py2.6.egg/
> >> > > django/core/management/base.py", line 191, in run_from_argv
> >> > >    self.execute(*args,
> >> > > **options.__dict__)
> >> > >  File "/usr/local/lib/python2.6/dist-packages/Django-1.2.4-py2.6.egg/
> >> > > django/core/management/base.py", line 220, in execute
> >> > >    output = self.handle(*args,
> >> > > **options)
> >> > >  File "/usr/local/lib/python2.6/dist-packages/Django-1.2.4-py2.6.egg/
> >> > > django/core/management/base.py", line 351, in handle
> >> > >    return
> >> > > self.handle_noargs(**options)
> >> > >  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.5.3-
> >> > > py2.6.egg/reviewboard/reviews/management/commands/index.py", line 55,
> >> > > in
> >> > > handle_noargs
> >> > >    if not
> >> > > os.path.exists(store_dir):
> >> > >  File "/usr/lib/python2.6/genericpath.py", line 18, in
> >> > > exist

Re: Problem posting diff

2011-02-12 Thread Gilles Moris
On Friday 11 February 2011 11:22:47 pm Jerry wrote:
> The relevant lines from reviewboard.log on the server:
> -
> 2011-02-11 14:09:25,121 - DEBUG - Trying discovered key
> 287637e1d8a393fefcc82e2c35f4f567 in /var/www/reviewboard/data/.ssh/
> id_dsa
> 2011-02-11 14:09:25,156 - DEBUG - userauth is OK
> 2011-02-11 14:09:25,192 - INFO - Authentication (publickey)
> successful!
> 2011-02-11 14:09:25,297 - DEBUG - EOF in transport thread
> 2011-02-11 14:09:25,317 - DEBUG - EOF in transport thread
> -
> This log also hasn't changed over the course of 5 minutes.  So it
> looks like adding the ssh key helped (though only in conjunction with
> the fully-qualified path, so that did matter as you suspected it
> might).
>
>
> I just killed the process on the client because I have to leave the
> computer now, but I'm gonna try to come back later tonight and see if
> I can debug it.  Any ideas you have in the meantime will be
> appreciated.  Thanks so much for all your help so far!

Stupid question, but does SSH access ever been tested for Mercurial repos ?
It seems that the support for SSH is relatively recent (Dec 29 2010).

>From what I see, I can clone with standard ssh command using RB private key, 
>but not if I use rbssh.

# sudo -u apache hg clone --config "ui.ssh=rbssh" --debug 
ssh://morisgi@localhost/hello hello.clone
running rbssh morisgi@localhost "hg -R hello serve --stdio"
sending hello command
sending between command
remote: /usr/lib/python2.4/site-packages/paramiko/client.py:94: UserWarning: 
Unknown ssh-rsa host key for localhost: 10b09cfbea8aab56c4df7c9cff5712a7
remote:   warnings.warn('Unknown %s host key for %s: %s' %
remote: Error connecting to server: No authentication methods available
abort: no suitable response from remote hg!

Possibly rbssh/paramiko is to verbose and confuses the mercurial wire protocol.
Or the known host key is not correctly saved when recording the repo 
declaration,
or more precisely is not accessible to rbssh, though Reviewboard knows it.

Note that this fails, but I don't know if it's supposed to work:
# rbssh morisgi@localhost echo
Error connecting to server: No authentication methods available

Regards.
Gilles.

-- 
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: Issue Upgrading.

2011-02-12 Thread Christian Hammond
Hi Sapna,

Review Board is going to show the version of the Review Board code being run
in the Python interpreter for your site. This should be the latest version.
If it's showing 1.0.x, then it sounds like either Review Board 1.5.x wasn't
installed, or it's installed in some non-standard location somehow.

Did you perform the upgrade with 'easy_install -U ReviewBoard', or just
'rb-site upgrade'?

Christian

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


On Fri, Feb 11, 2011 at 4:17 PM, Sapna Vempati wrote:

> Thanks Christian.
>
> If the errors are just warnings, the issue is that we don't see a complete
> installation and upgrade.  The RB servers still shows as 1.0.X. and not
> 1.5.3.
>
> Do you know how I could locate: cmemcache on the file system ?
>
> Thanks,
> Sapna
>
>
> On Fri, Feb 11, 2011 at 12:39 PM, Christian Hammond 
> wrote:
>
>> Hi Sapna,
>>
>> Going back to 1.5.1 from 1.5.3 unfortunately means removing the old
>> version from the filesystem manually. At that point you can do:
>>
>> easy_install -U ReviewBoard==1.5.1
>>
>> However, this won't fix the errors below. Those appear to me to be
>> harmless. Are you hitting any real problems with the site?
>>
>> The mcm_storage_add errors appear to be from the old cmemcache libraries.
>> If you can locate these on the filesystem and remove them, they should go
>> away, as Django will fall back on the new libraries we now install along
>> with Review Board.
>>
>> The current release of RBTools should be compatible with everything from
>> 1.0.x to 1.5.3.
>>
>> Christian
>>
>> --
>> Christian Hammond - chip...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> VMware, Inc. - http://www.vmware.com
>>
>>
>> On Fri, Feb 11, 2011 at 11:21 AM, Sapna Vempati 
>> wrote:
>>
>>> Hi Christian,
>>>
>>> Using the below command for upgrade, upgrades to the latest version
>>> (1.5.3) by default. Is there a way we can upgrade to an older version we
>>> prefer ? Like for example, we want to do install to RB1.5.1. Is it possible
>>> ?
>>>
>>>   easy_install -U ReviewBoard
>>>
>>> Also, from the release notes, looks like this version has a newer
>>> RBTools. Is this compatible with older RB versions ?
>>>
>>> When we try to upgrade using the above command, we got the below error,
>>> so that's the reason we want to go back to older version to see if that
>>> works.
>>>
>>>   #[root@mob-rb-test /]# rb-site --debug upgrade
>>>
>>>
>>>
>>>
>>>   /opt/lampp/htdocs/reviewboard
>>>   Rebuilding directory structure
>>>
>>>
>>>
>>>
>>>   Updating database. This may take a while.
>>>   [NOTICE@1297389237.811425] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>
>>>
>>>
>>>   [NOTICE@1297389237.845006] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>
>>>
>>>
>>>
>>>   [NOTICE@1297389237.866137] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>   [NOTICE@1297389237.900860] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>
>>>
>>>
>>>   [NOTICE@1297389237.934480] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>   [NOTICE@1297389237.967112] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>
>>>
>>>
>>>
>>>   [NOTICE@1297389238.012221] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>   [NOTICE@1297389238.048986] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>
>>>
>>>
>>>
>>>   [NOTICE@1297389238.104145] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>
>>>
>>>
>>>   [NOTICE@1297389238.224780] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>
>>>
>>>
>>>   [NOTICE@1297389238.273282] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>
>>>
>>>
>>>   [NOTICE@1297389238.320729] mcm_storage_cmd():3334: unable to 
>>> store value: add
>>>
>>>No fixtures found.
>>>   /opt/lampp/lib/python2.5/site-packages/pycrypto-2.3-py2.5-
>>> linux-i686.egg/Crypto/Util/randpool.py:40:
>>> RandomPool_DeprecationWarning: This application uses RandomPool, which is
>>> BROKEN in older releases.  See http://www.pycrypto.org/randpool-broken
>>>
>>>   RandomPool_DeprecationWarning)
>>>
>>>No evolution required.
>>>Upgrade complete.
>>> Thanks,
>>> Sapna
>>>
>>> --
>>> 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 Boa