Sure please see below:
# Site-specific configuration settings for Review Board
# Definitions of these settings can be found at
# http://docs.djangoproject.com/en/dev/ref/settings/
# Database configuration
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'svrrb',
'USER': 'username',
'PASSWORD': 'password',
'HOST': 'localhost',
'PORT': '',
},
}
# Unique secret key. Don't share this with anybody.
SECRET_KEY = 'key value ########'
# Cache backend settings.
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': 'localhost:11211',
},
}
# Extra site information.
SITE_ID = 1
SITE_ROOT = '/svrrb/'
FORCE_SCRIPT_NAME = ''
DEBUG = True
On Wed, Feb 6, 2013 at 3:32 PM, Christian Hammond <[email protected]>wrote:
Can you provide your settings_local.py file? Make sure to remove your
database information and your SECRET_KEY first!
Christian
--
Christian Hammond - [email protected]
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Feb 6, 2013 at 3:28 PM, chuck j <[email protected]> wrote:
> Also SElinux is turned off.
>
> #selinuxenabled && echo enabled || echo disabled
> disabled
>
>
>
> On Wed, Feb 6, 2013 at 3:22 PM, chuck j <[email protected]> wrote:
>
>> Thank you !!,
>>
>> yes it is happening for all the review request, also after restart i am
>> not able to open login page also and it crashed with the same compilation
>> error.
>>
>> CompilerError at /svrrb/dashboard/
>>
>>
>> /usr/bin/env: lessc: No such file or directory
>>
>> Request Method: GET
>> Request URL: http://svrrb1.na.software.com/svrrb/dashboard/
>> Django Version: 1.4.3
>> Exception Type: CompilerError
>>
>> Exception Value:
>>
>> /usr/bin/env: lessc: No such file or directory
>>
>> Exception Location:
>> /usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/__init__.py
>> in execute_command, line 101
>> Python Executable: /usr/bin/python
>>
>> One question though while we try to fix this issue.
>>
>> Can we install reviewboard fresh and then perform database base upgrade,
>> do we have such option? in case we land up no where :(
>>
>> Thing are looking dark now
>>
>>
>>
>> On Wed, Feb 6, 2013 at 3:10 PM, Christian Hammond <[email protected]>wrote:
>> All the files match correctly, so I'm left to believe that Review
>> Board/Apache's unable to open them, and is trying to fall back on creating
>> new ones (using lessc).
>>
>> Does this happen for all review requests? I'd imagine it'd have to.
>>
>> Is SELinux turned on? Try turning it off.
>>
>> You also may want to try restarting memcached, in case something bad is
>> cached somewhere.
>>
>> Christian
>>
>>
>> --
>> Christian Hammond - [email protected]
>> Review Board - http://www.reviewboard.org
>> VMware, Inc. - http://www.vmware.com
>>
>>
>> On Wed, Feb 6, 2013 at 2:44 PM, chuck j <[email protected]> wrote:
>>
>>> Yes, i have restarted the Apache afterward.
>>>
>>>
>>> Here you go:
>>>
>>> here is the content of ccs /var/www/svrrb/htdocs/static/rb/css
>>> admin.1f278e6382ef.css admin.min.c8a349cc3f7d.css
>>> dashboard.cb3f25c48eb7.css diffviewer.css
>>> js-tests.70d6ede4e69e.css reviews.css
>>> syntax.5f96383e25b8.css
>>> admin.60fbb7d18d8e.less admin.min.css
>>> dashboard.cebe4c36b08b.less diffviewer.less
>>> js-tests.9844a908a7ed.less reviews.less syntax.css
>>> admin.css common.2273b0c06c33.css
>>> dashboard.css docs.css
>>> js-tests.css reviews.min.af2c67b6345a.css
>>> admin-dashboard.0d89aa70a294.less common.7ace5f78ab0a.less
>>> dashboard.less docs.d72d2b5acebd.css
>>> js-tests.less reviews.min.css
>>> admin-dashboard.38adf3895ca1.css common.css
>>> defs.d9851fd5c124.less ie_hacks.css
>>> js-tests.min.70d6ede4e69e.css search.0553e42c0d00.less
>>> admin-dashboard.css common.less
>>> defs.less ie_hacks.e31a795a9b81.css
>>> js-tests.min.css search.47a5f4d644fe.css
>>> admin-dashboard.less common.min.8d7bf2d2a824.css
>>> diffviewer.0df7f678336d.less iphone.css
>>> reviews.222d0930c962.less search.css
>>> admin.less common.min.css
>>> diffviewer.b6c23a8b7583.css iphone.e915fbaf08c1.css
>>> reviews.6b97b76026b7.css search.less
>>>
>>>
>>> /var/www/svrrb/htdocs/static/djblets/css
>>> [root@svrrb1 css]# ls
>>> admin.67612c83bb86.css admin.css datagrid.1a0aafea202a.css
>>> datagrid.css extensions.43c3ee635a23.css extensions.css
>>>
>>> *Linux distribution:*
>>>
>>> Red Hat Enterprise Linux Server release 5.4 (Tikanga)
>>> Kernel \r on an \m
>>>
>>> Thank you for you help.
>>>
>>> Please let me know if you need actual files to look into, i will sent it
>>> to you.
>>>
>>> -CJ
>>>
>>> On Wed, Feb 6, 2013 at 2:33 PM, Christian Hammond
>>> <[email protected]>wrote:
>>> And you restarted Apache afterward?
>>>
>>> I'll need to see the contents of the css directories.
>>>
>>> I also still need to know what version of what Linux distro you're using.
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - [email protected]
>>> Review Board - http://www.reviewboard.org
>>> VMware, Inc. - http://www.vmware.com
>>>
>>>
>>> On Wed, Feb 6, 2013 at 2:24 PM, chuck j <[email protected]> wrote:
>>>
>>>> yes you are correct i followed the upgrade instruction from
>>>> www.reviewboard.org
>>>>
>>>> To verify, when you upgraded using easy_install -U ReviewBoard, you
>>>> then ran 'rb-site upgrade /path/to/site'
>>>>
>>>> I also saw below message,
>>>>
>>>> [root@svrrb1 www]# rb-site upgrade /var/www/svrrb
>>>>
>>>> /usr/local/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.
>>>> Rebuilding directory structure
>>>> Upgrading site settings_local.py
>>>> Updating database. This may take a while.
>>>>
>>>> The log output below, including warnings and errors,
>>>> can be ignored unless upgrade fails.
>>>>
>>>> ------------------ <begin log output> ------------------
>>>> Creating tables ...
>>>> Creating table extensions_registeredextension
>>>> Creating table diffviewer_filediffdata
>>>> Creating table hostingsvcs_hostingserviceaccount
>>>> Upgrading Review Board from 1.6.1 to 1.7.4
>>>> 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.
>>>> Adding baseline version for new models
>>>> Project signature has changed - an evolution is required
>>>> Installing custom SQL ...
>>>> Installing indexes ...
>>>> Installed 0 object(s) from 0 fixture(s)
>>>> Evolution successful.
>>>> ------------------- <end log output> -------------------
>>>>
>>>>
>>>> I am using linux: 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009
>>>> x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>> [root@svrrb1 rb]# pwd
>>>> /var/www/svrrb/htdocs/static/rb
>>>> [root@svrrb1 rb]# ls -l
>>>> total 12
>>>> drwxr-xr-x 2 root root 4096 Feb 5 23:15 css
>>>> drwxr-xr-x 5 root root 4096 Feb 5 23:15 images
>>>> drwxr-xr-x 5 root root 4096 Feb 5 23:15 js
>>>>
>>>> [root@svrrb1 static]# pwd
>>>> /var/www/svrrb/htdocs/static
>>>> [root@svrrb1 static]# ls -lrt
>>>> total 16
>>>> lrwxrwxrwx 1 root root 95 Feb 5 23:18 rb ->
>>>> /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/rb
>>>> lrwxrwxrwx 1 root root 96 Feb 5 23:18 lib ->
>>>> /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/lib
>>>> lrwxrwxrwx 1 root root 77 Feb 5 23:18 djblets ->
>>>> /usr/local/lib/python2.7/site-packages/Djblets-0.7.9-py2.7.egg/djblets/static
>>>> lrwxrwxrwx 1 root root 98 Feb 5 23:18 admin ->
>>>> /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/admin
>>>>
>>>> What to do !!
>>>>
>>>> On Wed, Feb 6, 2013 at 2:12 PM, Christian Hammond
>>>> <[email protected]>wrote:
>>>> Yep, it's looking for lessc, which it shouldn't be. That means it's not
>>>> finding the generated static media files, probably. Or some other strange
>>>> configuration problem. Probably an installation problem.
>>>>
>>>> To verify, when you upgraded using easy_install -U ReviewBoard, you
>>>> then ran 'rb-site upgrade /path/to/site', correct?
>>>>
>>>> If you did do the rb-site upgrade when you installed 1.7.4, then can
>>>> you show me what's in your $sitedir/htdocs/static/rb/css/ and
>>>> $sitedir/htdocs/static/djblets/css/ directories?
>>>>
>>>> What version of what distro are you using?
>>>>
>>>> Christian
>>>>
>>>> --
>>>> Christian Hammond - [email protected]
>>>> Review Board - http://www.reviewboard.org
>>>> VMware, Inc. - http://www.vmware.com
>>>>
>>>>
>>>> On Wed, Feb 6, 2013 at 2:04 PM, chuck j <[email protected]> wrote:
>>>>
>>>>> Here are the logs
>>>>>
>>>>> its seems it searching for lessc executable.
>>>>>
>>>>> Environment:
>>>>>
>>>>>
>>>>> Request Method: GET
>>>>> Request URL: http://scrrb1.na.software.com/svrrb/dashboard/?view=to-me
>>>>>
>>>>> Django Version: 1.4.3
>>>>> Python Version: 2.7.2
>>>>> Installed Applications:
>>>>> ['django.contrib.admin',
>>>>> 'django.contrib.auth',
>>>>> 'django.contrib.contenttypes',
>>>>> 'django.contrib.markup',
>>>>> 'django.contrib.sites',
>>>>> 'django.contrib.sessions',
>>>>> 'django.contrib.staticfiles',
>>>>> 'djblets.datagrid',
>>>>> 'djblets.extensions',
>>>>> 'djblets.feedview',
>>>>> 'djblets.gravatars',
>>>>> 'djblets.log',
>>>>> 'djblets.pipeline',
>>>>> 'djblets.siteconfig',
>>>>> 'djblets.util',
>>>>> 'djblets.webapi',
>>>>> 'pipeline',
>>>>> 'reviewboard.accounts',
>>>>> 'reviewboard.admin',
>>>>> 'reviewboard.attachments',
>>>>> 'reviewboard.changedescs',
>>>>> 'reviewboard.diffviewer',
>>>>> 'reviewboard.extensions',
>>>>> 'reviewboard.hostingsvcs',
>>>>> 'reviewboard.notifications',
>>>>> 'reviewboard.reviews',
>>>>> 'reviewboard.reviews.ui',
>>>>> 'reviewboard.scmtools',
>>>>> 'reviewboard.site',
>>>>> 'reviewboard.ssh',
>>>>> 'reviewboard.webapi',
>>>>> 'django_evolution']
>>>>> Installed Middleware:
>>>>> ['django.middleware.gzip.GZipMiddleware',
>>>>> 'reviewboard.admin.middleware.InitReviewBoardMiddleware',
>>>>> 'django.middleware.common.CommonMiddleware',
>>>>> 'django.middleware.doc.XViewMiddleware',
>>>>> 'django.middleware.http.ConditionalGetMiddleware',
>>>>> 'django.middleware.locale.LocaleMiddleware',
>>>>> 'django.contrib.sessions.middleware.SessionMiddleware',
>>>>> 'django.contrib.auth.middleware.AuthenticationMiddleware',
>>>>> 'django.contrib.messages.middleware.MessageMiddleware',
>>>>> 'djblets.siteconfig.middleware.SettingsMiddleware',
>>>>> 'reviewboard.admin.middleware.LoadSettingsMiddleware',
>>>>> 'djblets.extensions.middleware.ExtensionsMiddleware',
>>>>> 'djblets.log.middleware.LoggingMiddleware',
>>>>> 'reviewboard.accounts.middleware.TimezoneMiddleware',
>>>>> 'reviewboard.admin.middleware.CheckUpdatesRequiredMiddleware',
>>>>> 'reviewboard.admin.middleware.X509AuthMiddleware',
>>>>> 'reviewboard.site.middleware.LocalSiteMiddleware']
>>>>>
>>>>>
>>>>> Template error:
>>>>> In template
>>>>> /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/templates/base.html,
>>>>> error at line 39
>>>>> /usr/bin/env: lessc: No such file or directory
>>>>>
>>>>> 29 : },
>>>>>
>>>>>
>>>>> 30 : {% if not user.is_anonymous %}
>>>>>
>>>>>
>>>>> 31 : gUserName = "{{user.username}}",
>>>>>
>>>>>
>>>>> 32 : gUserFullName = "{{user|user_displayname}}",
>>>>>
>>>>>
>>>>> 33 : {% endif %}
>>>>>
>>>>>
>>>>> 34 : gUserAuthenticated = {{user.is_authenticated|lower}};
>>>>>
>>>>>
>>>>> 35 : {% block jsconsts %}{% endblock %}
>>>>>
>>>>>
>>>>> 36 : </script>
>>>>>
>>>>>
>>>>> 37 : <link rel="shortcut icon" type="image/x-icon" href="{%
>>>>> static "rb/images/favicon.ico" %}" />
>>>>>
>>>>>
>>>>> 38 : <link rel="apple-touch-icon-precomposed" type="image/png"
>>>>> href="{% static "rb/images/apple-home-icon.png" %}" />
>>>>>
>>>>>
>>>>> 39 : {% compressed_css "common" %}
>>>>>
>>>>>
>>>>> 40 : {% block css %}{% endblock %}
>>>>>
>>>>>
>>>>> 41 : {% template_hook_point "base-css" %}
>>>>>
>>>>>
>>>>> 42 : <!--[if lt IE 7.]>
>>>>>
>>>>>
>>>>> 43 : <style type="text/css">
>>>>>
>>>>>
>>>>> 44 : body {
>>>>>
>>>>>
>>>>> 45 : behavior: url("{% static "lib/js/csshover2.htc" %}");
>>>>>
>>>>>
>>>>> 46 : }
>>>>>
>>>>>
>>>>> 47 :
>>>>>
>>>>>
>>>>> 48 : img,
>>>>>
>>>>>
>>>>> 49 : table.sidebyside .commentflag,
>>>>>
>>>>>
>>>>> Traceback:
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/core/handlers/base.py"
>>>>> in get_response
>>>>> 111. response = callback(request,
>>>>> *callback_args, **callback_kwargs)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Djblets-0.7.9-py2.7.egg/djblets/auth/util.py"
>>>>> in _checklogin
>>>>> 47. return view_func(request, *args, **kwargs)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/accounts/decorators.py"
>>>>> in _check_valid_prefs
>>>>> 52. return view_func(request, *args, **kwargs)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/reviews/views.py"
>>>>> in dashboard
>>>>> 854. 'sidebar_hooks': DashboardHook.hooks,
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Djblets-0.7.9-py2.7.egg/djblets/datagrid/grids.py"
>>>>> in render_to_response
>>>>> 777.
>>>>> context))
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/shortcuts/__init__.py"
>>>>> in render_to_response
>>>>> 20. return HttpResponse(loader.render_to_string(*args,
>>>>> **kwargs), **httpresponse_kwargs)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/loader.py"
>>>>> in render_to_string
>>>>> 171. return t.render(Context(dictionary))
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/base.py"
>>>>> in render
>>>>> 140. return self._render(context)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/base.py"
>>>>> in _render
>>>>> 134. return self.nodelist.render(context)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/base.py"
>>>>> in render
>>>>> 823. bit = self.render_node(node, context)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/debug.py"
>>>>> in render_node
>>>>> 74. return node.render(context)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/loader_tags.py"
>>>>> in render
>>>>> 123. return compiled_parent._render(context)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/base.py"
>>>>> in _render
>>>>> 134. return self.nodelist.render(context)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/base.py"
>>>>> in render
>>>>> 823. bit = self.render_node(node, context)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/debug.py"
>>>>> in render_node
>>>>> 74. return node.render(context)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/templatetags/compressed.py"
>>>>> in render
>>>>> 34. paths = self.packager.compile(package.paths)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/packager.py"
>>>>> in compile
>>>>> 95. return self.compiler.compile(paths, force=force)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/__init__.py"
>>>>> in compile
>>>>> 40. compiler.compile_file(infile, outfile,
>>>>> outdated=outdated, force=force)
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/less.py"
>>>>> in compile_file
>>>>> 22. return self.execute_command(command, cwd=dirname(infile))
>>>>> File
>>>>> "/usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/__init__.py"
>>>>> in execute_command
>>>>> 101. raise CompilerError(error)
>>>>>
>>>>> Exception Type: CompilerError at /svrrb/dashboard/
>>>>> Exception Value: /usr/bin/env: lessc: No such file or directory
>>>>>
>>>>> Please help.
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Feb 6, 2013 at 1:47 PM, chuck j <[email protected]> wrote:
>>>>>
>>>>>> While sent an email to you, I face one issue.
>>>>>>
>>>>>> When i clicked to any of the old review request i see error message:
>>>>>>
>>>>>> Something broke! (Error 500)
>>>>>>
>>>>>> It appears something broke when you tried to go to here. This is
>>>>>> either a bug in Review Board or a server configuration error. Please
>>>>>> report
>>>>>> this to your administrator.
>>>>>>
>>>>>> What is this weird message....has upgrade went fine?
>>>>>>
>>>>>> Thanks,
>>>>>> - Chuck
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 6, 2013 at 1:40 PM, chuck j <[email protected]> wrote:
>>>>>>
>>>>>>> Hi Christian,
>>>>>>>
>>>>>>> I would like to thank you for your response about upgrade.
>>>>>>>
>>>>>>> I went through with your comments and i was able to bring my server
>>>>>>> to 1.7.4.
>>>>>>>
>>>>>>> Also also want to bring to your notice regarding below warning i got
>>>>>>> after while upgrading my site.
>>>>>>>
>>>>>>> /usr/local/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.
>>>>>>>
>>>>>>> How to resolve this? Do i need to build it libgmp again as message
>>>>>>> shows, will it make RB server report more issues.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> -Chuck
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Feb 1, 2013 at 6:58 PM, chuck j <[email protected]>wrote:
>>>>>>>
>>>>>>>> Thanks Christian for the response.
>>>>>>>>
>>>>>>>> Good to hear that upgrade is possible from 1.6.1 to 1.7.4 RB
>>>>>>>> version, apart from the database backup do we need to take care of any
>>>>>>>> thing else which will disturb our production setup and in case of any
>>>>>>>> issue
>>>>>>>> we should be able to go back to our original state, if you point us
>>>>>>>> action
>>>>>>>> item it would be really great.
>>>>>>>>
>>>>>>>> Few queries though
>>>>>>>>
>>>>>>>> 1. How does upgrade takes place, does it replace files by files ( I
>>>>>>>> mean python scripts etc ) apart from db.
>>>>>>>> 2. The Release note of 1.7.2 its been mentioned about below
>>>>>>>>
>>>>>>>> >>>>> However, this requires that p4python is specially compiled
>>>>>>>> with OpenSSL support, and that the system has development headers for
>>>>>>>> OpenSSL 1.0.1. P4PythonInstaller doesn’t do this, so users who need
>>>>>>>> this
>>>>>>>> feature will currently have to compile p4python manually, providing the
>>>>>>>> path to the SSL directory using --ssl
>>>>>>>> >>>>>
>>>>>>>>
>>>>>>>> Do we have any tech note for the above steps which end user needs
>>>>>>>> to perform.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Chuck
>>>>>>>>
>>>>>>>> On Thu, Jan 31, 2013 at 2:50 PM, Christian Hammond <
>>>>>>>> [email protected]> wrote:
>>>>>>>> Hi Chuck,
>>>>>>>>
>>>>>>>> I always recommend backing up your database first, but you should
>>>>>>>> be able to upgrade from 1.6.1 to 1.7.4 without any real problems.
>>>>>>>>
>>>>>>>> There is a bug that some people hit a while back in older versions
>>>>>>>> that introduced some stale upgrade data in the database. I meant to
>>>>>>>> get a
>>>>>>>> final fix out in 1.7.4, but it slipped. If your 'rb-site upgrade'
>>>>>>>> complains
>>>>>>>> about fields that already exist or something, e-mail and I'll give you
>>>>>>>> the
>>>>>>>> solution. Otherwise, you shouldn't have any problems.
>>>>>>>>
>>>>>>>> Christian
>>>>>>>>
>>>>>>>> --
>>>>>>>> Christian Hammond - [email protected]
>>>>>>>> Review Board - http://www.reviewboard.org
>>>>>>>> VMware, Inc. - http://www.vmware.com
>>>>>>>>
>>>>>>>> On Thu, Jan 31, 2013 at 2:47 PM, chuck j <[email protected]>wrote:
>>>>>>>>
>>>>>>>>> Dear All,
>>>>>>>>>
>>>>>>>>> There has been lots of improvement done on RB server from version
>>>>>>>>> 1.6.1 till date, hence i would like to know if the upgrade from 1.6.1
>>>>>>>>> to
>>>>>>>>> latest version is supported? If not then how should I bring my RB
>>>>>>>>> server
>>>>>>>>> 1.6.1 to latest state without loosing the existing data from my
>>>>>>>>> existing
>>>>>>>>> database. We need to upgrade because 1.7.2 has SSL feature implement
>>>>>>>>> and we
>>>>>>>>> have planned to upgrade perforce server to 2012.2.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Please help.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Appreciated your response and help
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> Chuck.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
--
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
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
