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 <cjerry2...@gmail.com> 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 <chip...@chipx86.com>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 - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > On Thu, Jan 31, 2013 at 2:47 PM, chuck j <cjerry2...@gmail.com> 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
