Re: changing the host name / URL reference for reviewboard

ruary 2019 10:02:47 UTC+5:30, harish varadarajan wrote: > > Hi, > > I want to understand the best practices to be followed when a given > ReviewBoard server name gets changed, but there are no other intended > changes. > Inputs in this regard will be highly helpfu

changing the host name / URL reference for reviewboard

Hi, I want to understand the best practices to be followed when a given ReviewBoard server name gets changed, but there are no other intended changes. Inputs in this regard will be highly helpful. The scenario is as below. - Unix host A which hosts RB instance (referred through http://A

Upgrade to ReviewBoard 2.5.13.1

Hi, We intend to upgrade to RB 2.5.13.1 (from 2.5.6.1) and below is the list of steps that is intended to be followed on the day of migration. Please help review and let know if there is anything specific that needs to be accounted for the upgrade. (1) Create sql backup, using mysqldump. (2)

Mercurial + Got API Error 207 (HTTP code 400): The file was not found in the repository.

Hi, we have a reviewboard setup for Mercurial and get the below error when posting a review request. Any inputs on this will be helpful. >>> Got API Error 207 (HTTP code 400): The file was not found in the repository. >>> Error data: {u'stat': u'fail', u'file': u'$file_name', u'err': {u'msg':

Re: abort: The file was not found in the repository. (207)

Hi Divakar, Was there a resolution to this issue. We are encountering the same issue and any pointers on fixing this will be helpful. Thanks. -- Harish On Friday, 26 February 2016 20:51:16 UTC+5:30, Divakar K wrote: > > Can someone please able to help me to proceed further. its blocking. > >

Re: rbt post within a mercurial repository does not work: API Error 207 file was not found

Hi, We get a similar error with reviewboard while posting reviews for a change in mercurial repository. Is there a reason for occurrence of this type of error, and if yes, what can possibly address this. Thanks. -- Harish On Monday, 9 November 2015 22:35:09 UTC+5:30, Fabian Sturm wrote: > >

Re: Reviewboard 2.5.6.1 & comment severity

king without it, > you have a bigger issue to solve on the server. > > Christian > > > On Tuesday, September 6, 2016, harish varadarajan <harish.va...@gmail.com > > wrote: > >> Hi Christian, >> >> reinstalling through easy_install and running instal

Re: Reviewboard 2.5.6.1 & comment severity

, go into the Review Board admin page -> > Extensions and make sure none of the extensions are reporting any errors. > If they are, let me know which ones and what the error says. > > > Christian > > > -- > Christian Hammond > President/CEO of Beanbag <https://www.b

Re: Reviewboard 2.5.6.1 & comment severity

have them copied from the > extension. > > Try erasing the contents of $sitedir/static and then do: > > rb-site upgrade $sitedir > rb-site manage $sitedir install-extension-media -- --force > > Christian > > > On Tuesday, September 6, 2016, harish varadarajan

Re: Reviewboard 2.5.6.1 & comment severity

gt; > -David > > On Mon, Sep 5, 2016 at 8:07 AM harish varadarajan <harish.va...@gmail.com > > wrote: > >> Post installing reviewboard 2.6.6.1 and extension Comment Severity 0.5.1, >> when trying to run collectstatic, the following error is seen. >> The version

Reviewboard 2.5.6.1 & comment severity

Post installing reviewboard 2.6.6.1 and extension Comment Severity 0.5.1, when trying to run collectstatic, the following error is seen. The version of lessc is 2.7.1 File "/usr/lib/python2.7/site-packages/pipeline/compilers/__init__.py", line 99, in execute_command raise

Re: Changes with update diff in 2.5.6.1

n > prompt you for them. > > -David > On Sun, Sep 4, 2016 at 1:40 AM harish varadarajan <harish.va...@gmail.com > > wrote: > >> The documentation of 2.5, >> https://www.reviewboard.org/docs/manual/2.5/users/review-requests/uploading-diffs/ >> does >>

Re: Changes with update diff in 2.5.6.1

The documentation of 2.5, https://www.reviewboard.org/docs/manual/2.5/users/review-requests/uploading-diffs/ does have information. Is there a way to mimic the older behavior ? Thanks. Harish On Sunday, 4 September 2016 13:51:26 UTC+5:30, harish varadarajan wrote: > > Hi, > >

Changes with update diff in 2.5.6.1

Hi, we recently updated to RB 2.5.6.1 from 2.0.15 and find a difference in behavior for "Update" -> "Update diff" ( "Upload diff" )of reviews while in 2.0.15, entries were present to have "Parent Diff" and "Base commit id", this is not seen in 2.5.6.1 Is this the intended behavior. If not,

Re: Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"

; > Makers of Review Board <https://www.reviewboard.org/> > > On Fri, Jul 29, 2016 at 7:12 PM, harish varadarajan < > harish.va...@gmail.com > wrote: > >> Further, the reviewboard database was created with UTF8 character set. >> >> MariaDB [review

Re: Backup and Restore of Reviewboard 2.0 failing (mysqldump issues)

wrong? >> >> Thanks, >> >> Christian >> >> -- >> Christian Hammond >> President/CEO of Beanbag <https://www.beanbaginc.com/> >> Makers of Review Board <https://www.reviewboard.org/> >> >> On Fri, Jul 29, 2016 at 7:34 PM, h

Re: Backup and Restore of Reviewboard 2.0 failing (mysqldump issues)

Hi Eric, Thanks for your post, that I could understand the issue that was happening at my reviewboard instance. Did you figure out the solution for this. With your approach to turning the Debug = True, I am currently able to access the repositories / enter the edit screen. But unfortunately,

Re: Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"

The specific error from the server log seems to be DjangoUnicodeDecodeError: 'utf8' codec can't decode byte 0x8b in position 0: invalid start byte. You passed in () On Friday, 29 July 2016 20:26:38 UTC+5:30, harish varadarajan wrote: > > Hi, > > > I am pretty new to re

Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"

Hi, I am pretty new to reviewboard and have attempted to migrate reviewboard instance across hosts and versions. Our older RB version was and the upgrade was to 2.5.6.1 Steps followed for the upgrade were (1) Dump data on the older server (mysql) (2) Drop the previously created reviewboard