Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

2015-12-08 Thread sean
(Didn't have coffee yet.) It resolves the dependency issue but not the 
rb-site upgrade issue.
The log was done after installing django evolution from epel-testing 
(otherwise it broke on version dependency before ever attempting to run the 
upgrade)

On Tuesday, December 8, 2015 at 10:00:18 AM UTC+1, se...@m2mobi.com wrote:
>
> Should've mentioned running exactly that got me past this error already. 
>
> On Monday, December 7, 2015 at 5:21:16 PM UTC+1, Stephen Gallagher wrote:
>>
>> Hmm, I thought I fixed that version. I'll push an update immediately. If 
>> you manually run `yum update python-django-evolution 
>> --enablerepo=epel-testing` and then attempt the upgrade, does that resolve 
>> your upgrade issue? What version of django-evolution do you have right now? 
>> 0.7.5?
>>
>> On Mon, Dec 7, 2015 at 11:17 AM  wrote:
>>
>>> Hello Stephen,
>>>
>>> I've been patiently waiting for this for weeks now. Glad to see it's 
>>> getting close.
>>>
>>> Some issues I found upgrading from EPEL 2.0.18:
>>>
>>> The RPM requires: python-django-evolution >= 0.7.1
>>>
>>> ReviewBoard requires: django-evolution>=0.7.6,<=0.7.999
>>>
>>>
>>> *and during the rb-site upgrade I get the following message:*
>>>
>>> --  --
>>>
>>> Creating tables ...
>>>
>>> Creating table accounts_trophy
>>>
>>> Creating table attachments_fileattachmenthistory
>>>
>>> Creating table diffviewer_rawfilediffdata
>>>
>>> Creating table notifications_webhooktarget_repositories
>>>
>>> Creating table notifications_webhooktarget
>>>
>>> Creating table webapi_webapitoken
>>>
>>> Upgrading Review Board from 2.0.18 to 2.5.2
>>>
>>> There are unapplied evolutions for accounts.
>>>
>>> There are unapplied evolutions for attachments.
>>>
>>> There are unapplied evolutions for diffviewer.
>>>
>>> There are unapplied evolutions for notifications.
>>>
>>> There are unapplied evolutions for reviews.
>>>
>>> There are unapplied evolutions for webapi.
>>>
>>> Adding baseline version for new models
>>>
>>> Evolutions in notifications baseline: webhooktarget_extra_state, 
>>> webhooktarget_extra_data_null
>>>
>>> Project signature has changed - an evolution is required
>>>
>>> Installing custom SQL ...
>>>
>>> Installing indexes ...
>>>
>>> Installed 0 object(s) from 0 fixture(s)
>>>
>>> Evolution successful.
>>>
>>> ---  ---
>>>
>>>
>>> *the next run reduces this to:*
>>>
>>>
>>> --  --
>>>
>>> Creating tables ...
>>>
>>> There are unapplied evolutions for webapi.
>>>
>>> Installing custom SQL ...
>>>
>>> Installing indexes ...
>>>
>>> Installed 0 object(s) from 0 fixture(s)
>>>
>>> No evolution required.
>>>
>>> ---  ---
>>>
>>>
>>> However many times I run the upgrade though, the 'unapplied evolutions 
>>> for webapi' persist and the webpage keeps reporting 2.0.18 as the version.
>>>
>>>
>>> System: CentOS 7
>>>
>>> Webserver: Nginx
>>>
>>> On Saturday, December 5, 2015 at 1:05:06 AM UTC+1, Stephen Gallagher 
>>> wrote:

 Hello, folks! It's time for a big update. As many of you are probably 
 aware, I maintain the RPMs of Review Board that live in Fedora's EPEL 
 project[1] (Extra Packages for Enterprise Linux).

 For some time now, EPEL 7 (which provides community-supported add-on 
 software for RHEL 7 and CentOS 7) has been providing Review Board 2.0.x 
 packages. However, time passes and I now feel that it's worth upgrading 
 EPEL 7 to carry 2.5.2 with all of the enhancements and bugfixes that this 
 entails.

 This is a pretty major update to the server-side of things, so I'd 
 really like to get some serious testing performed if possible before I 
 push 
 this out to the stable repository. (Getting testing for updates has been a 
 problem in the past, which is why updates tend to trail the upstream 
 releases by at least two weeks; EPEL has a policy that it must remain in 
 the testing repository for at least that time unless it receives positive 
 feedback from people testing it).

 So, how can you help? The simplest way to do so would be to install the 
 new RPMs on your RHEL/CentOS 7 systems by installing the EPEL 7 repository 
 and then running:
 `yum install --enablerepo=epel-testing ReviewBoard` or `yum update 
 --enablerepo=epel-testing ReviewBoard` if you have an existing 
 installation. (Note: this was just submitted for the testing repository, 
 so 
 it may take up to 48 hours to reach your local mirror, though usually less 
 than 24).

 Then play around with it; test that it upgrades cleanly and that you 
 can create new sites in your preferred configuration. Once you have 
 feedback to provide (positive *or* negative), please create a Fedora 
 Account at  https://admin.fedoraproject.org/accounts/ and then log in 
 at 

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

2015-12-08 Thread sean
Should've mentioned running exactly that got me past this error already. 

On Monday, December 7, 2015 at 5:21:16 PM UTC+1, Stephen Gallagher wrote:
>
> Hmm, I thought I fixed that version. I'll push an update immediately. If 
> you manually run `yum update python-django-evolution 
> --enablerepo=epel-testing` and then attempt the upgrade, does that resolve 
> your upgrade issue? What version of django-evolution do you have right now? 
> 0.7.5?
>
> On Mon, Dec 7, 2015 at 11:17 AM  wrote:
>
>> Hello Stephen,
>>
>> I've been patiently waiting for this for weeks now. Glad to see it's 
>> getting close.
>>
>> Some issues I found upgrading from EPEL 2.0.18:
>>
>> The RPM requires: python-django-evolution >= 0.7.1
>>
>> ReviewBoard requires: django-evolution>=0.7.6,<=0.7.999
>>
>>
>> *and during the rb-site upgrade I get the following message:*
>>
>> --  --
>>
>> Creating tables ...
>>
>> Creating table accounts_trophy
>>
>> Creating table attachments_fileattachmenthistory
>>
>> Creating table diffviewer_rawfilediffdata
>>
>> Creating table notifications_webhooktarget_repositories
>>
>> Creating table notifications_webhooktarget
>>
>> Creating table webapi_webapitoken
>>
>> Upgrading Review Board from 2.0.18 to 2.5.2
>>
>> There are unapplied evolutions for accounts.
>>
>> There are unapplied evolutions for attachments.
>>
>> There are unapplied evolutions for diffviewer.
>>
>> There are unapplied evolutions for notifications.
>>
>> There are unapplied evolutions for reviews.
>>
>> There are unapplied evolutions for webapi.
>>
>> Adding baseline version for new models
>>
>> Evolutions in notifications baseline: webhooktarget_extra_state, 
>> webhooktarget_extra_data_null
>>
>> Project signature has changed - an evolution is required
>>
>> Installing custom SQL ...
>>
>> Installing indexes ...
>>
>> Installed 0 object(s) from 0 fixture(s)
>>
>> Evolution successful.
>>
>> ---  ---
>>
>>
>> *the next run reduces this to:*
>>
>>
>> --  --
>>
>> Creating tables ...
>>
>> There are unapplied evolutions for webapi.
>>
>> Installing custom SQL ...
>>
>> Installing indexes ...
>>
>> Installed 0 object(s) from 0 fixture(s)
>>
>> No evolution required.
>>
>> ---  ---
>>
>>
>> However many times I run the upgrade though, the 'unapplied evolutions 
>> for webapi' persist and the webpage keeps reporting 2.0.18 as the version.
>>
>>
>> System: CentOS 7
>>
>> Webserver: Nginx
>>
>> On Saturday, December 5, 2015 at 1:05:06 AM UTC+1, Stephen Gallagher 
>> wrote:
>>>
>>> Hello, folks! It's time for a big update. As many of you are probably 
>>> aware, I maintain the RPMs of Review Board that live in Fedora's EPEL 
>>> project[1] (Extra Packages for Enterprise Linux).
>>>
>>> For some time now, EPEL 7 (which provides community-supported add-on 
>>> software for RHEL 7 and CentOS 7) has been providing Review Board 2.0.x 
>>> packages. However, time passes and I now feel that it's worth upgrading 
>>> EPEL 7 to carry 2.5.2 with all of the enhancements and bugfixes that this 
>>> entails.
>>>
>>> This is a pretty major update to the server-side of things, so I'd 
>>> really like to get some serious testing performed if possible before I push 
>>> this out to the stable repository. (Getting testing for updates has been a 
>>> problem in the past, which is why updates tend to trail the upstream 
>>> releases by at least two weeks; EPEL has a policy that it must remain in 
>>> the testing repository for at least that time unless it receives positive 
>>> feedback from people testing it).
>>>
>>> So, how can you help? The simplest way to do so would be to install the 
>>> new RPMs on your RHEL/CentOS 7 systems by installing the EPEL 7 repository 
>>> and then running:
>>> `yum install --enablerepo=epel-testing ReviewBoard` or `yum update 
>>> --enablerepo=epel-testing ReviewBoard` if you have an existing 
>>> installation. (Note: this was just submitted for the testing repository, so 
>>> it may take up to 48 hours to reach your local mirror, though usually less 
>>> than 24).
>>>
>>> Then play around with it; test that it upgrades cleanly and that you can 
>>> create new sites in your preferred configuration. Once you have feedback to 
>>> provide (positive *or* negative), please create a Fedora Account at  
>>> https://admin.fedoraproject.org/accounts/ and then log in at 
>>> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-b8671a8638 and 
>>> use the feedback buttons and comment field to let me know how it went.
>>>
>>> Warning: if I get no feedback at all, I'm just going to push this to 
>>> stable at the end of two weeks, so if you don't want any surprises at your 
>>> next stable update, please help me out here.
>>>
>>>
>>> [1] https://fedoraproject.org/wiki/EPEL
>>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to 

Re: RBtools 0.7.4 error 105 path not found.

2015-12-08 Thread Rob Dejournett
It's reviewboard 2.0.1, we are using Git version 1.9.5.  I am not the 
review board administrator, but I have access to the linux box.  If you can 
point me to where the logs are that'd be really helpful.

Thanks!


On Monday, December 7, 2015 at 5:02:33 PM UTC-5, David Trowbridge wrote:
>
> What version of Review Board? What version control system (and version 
> thereof)? Is there anything in the server log?
>
> -David
>
>
> On Mon, Dec 7, 2015 at 11:43 AM Rob Dejournett  > wrote:
>
>> Sorry if this is a double post.  Getting error with some files posting 
>> using RBTools.  Java files seem to work fine.  I use something called Mirth 
>> Connect which generates XML files as code.  Basically when RBT tries to 
>> upload the diff it fails with the 105 error.  Attached is the diff.
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://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/d/optout.
>>
> -- 
> -David 

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Automatic Merging after successfull review

2015-12-08 Thread Harshal Kulkarni
Hi All,

I am newbie to reviewboard, I have one small question. Does reviewboard has 
the functionality of automatic merging the pull request after successfull 
code review?


Thanks,
Harshal

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Re: RBtools 0.7.4 error 105 path not found.

2015-12-08 Thread Rob Dejournett
Also the server log is here:

2015-12-08 14:49:54,420 - ERROR - None - rdejournett - 
/api/review-requests/5110/diffs/ - Error uploading new diff: Not Found
Traceback (most recent call last):
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/webapi/resources/diff.py",
 
line 292, in create
request.FILES.get('parent_diff_path'))
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/reviews/forms.py",
 
line 116, in create
history)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/diffviewer/forms.py",
 
line 69, in create
request=self.request)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/diffviewer/managers.py",
 
line 156, in create_from_upload
save=save)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/diffviewer/managers.py",
 
line 210, in create_from_data
limit_to=diff_filenames):
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/diffviewer/managers.py",
 
line 300, in _process_files
request=request))):
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/scmtools/models.py",
 
line 238, in get_file_exists
base_commit_id, request)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/scmtools/models.py",
 
line 415, in _get_file_exists_uncached
base_commit_id=base_commit_id)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/hostingsvcs/bitbucket.py",
 
line 177, in get_file_exists
self._api_get_src(repository, path, revision, base_commit_id)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/hostingsvcs/bitbucket.py",
 
line 214, in _api_get_src
return self._api_get(url, raw_content=True)
  File 
"/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/hostingsvcs/bitbucket.py",
 
line 265, in _api_get
raise Exception(e.read())
Exception: Not Found


On Tuesday, December 8, 2015 at 9:03:25 AM UTC-5, Rob Dejournett wrote:
>
> It's reviewboard 2.0.1, we are using Git version 1.9.5.  I am not the 
> review board administrator, but I have access to the linux box.  If you can 
> point me to where the logs are that'd be really helpful.
>
> Thanks!
>
>
> On Monday, December 7, 2015 at 5:02:33 PM UTC-5, David Trowbridge wrote:
>>
>> What version of Review Board? What version control system (and version 
>> thereof)? Is there anything in the server log?
>>
>> -David
>>
>>
>> On Mon, Dec 7, 2015 at 11:43 AM Rob Dejournett  
>> wrote:
>>
>>> Sorry if this is a double post.  Getting error with some files posting 
>>> using RBTools.  Java files seem to work fine.  I use something called Mirth 
>>> Connect which generates XML files as code.  Basically when RBT tries to 
>>> upload the diff it fails with the 105 error.  Attached is the diff.
>>>
>>> -- 
>>> Supercharge your Review Board with Power Pack: 
>>> https://www.reviewboard.org/powerpack/
>>> Want us to host Review Board for you? Check out RBCommons: 
>>> https://rbcommons.com/
>>> Happy user? Let us know! https://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/d/optout.
>>>
>> -- 
>> -David 
>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Re: Database upgrade from 1.7.27 to 2.5.2

2015-12-08 Thread rfs
On Monday, December 7, 2015 at 10:55:42 PM UTC-5, Stephen Gallagher wrote:
>
> Did you run this with the recent django-evolution 0.7.6 update? That 
> specifically addresses some upgrade issues unique to MySQL.
>

Yes, I am using python-django-evolution-0.7.6-1.el7.noarch with your fix 
from Dec 4th.

Christian has spotted the culprit, mixed MyISAM versus InnoDB database 
tables.

-Ralph

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Re: Database upgrade from 1.7.27 to 2.5.2

2015-12-08 Thread rfs
Hi Christian,

Thanks, that was exactly the problem. After switching to InnoDB, the 
upgrade to 2.5.2 completes, and I have a working install.
The one other change I had to make was the memcached backend name in 
settings_local.py (CacheClass -> MemcacheCache).

I did notice a difference in the "condensediffs" operation, under 2.0.18 it 
reported 21% savings, while under 2.5.2 it reported around 40% -- in both 
cases I started from the same 1.7.27 database. If that is something of 
concern, I can provide more details.

-Ralph

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Failed to upgrade from 1.7.12 to 1.7.28 and 2.x

2015-12-08 Thread Kevin Yin
So I got this reviewboard 1.7.12 server assigned to me. We have the need 
for some new features from newer versions of reviewboard. So I simply did 
easy_install -U ReviewBoard and rb-site upgrade. It failed. I did not have 
a recent backup, but luckily rolling back the ReviewBoard python package 
version worked. So I read a bunch of discussions here. I decided to upgrade 
to 1.7.28 first. But it fails too, with following error same as 
https://groups.google.com/forum/#!searchin/reviewboard/Downgrading$20Reviewboard$202.0RC2%7Csort:relevance/reviewboard/pxQ3eyYPhzE/PxEj_0_Oi9YJ:

--  --
Creating tables ...

[!] Unable to execute the manager command syncdb: No module named
db.fields

[!] Unable to execute the manager command evolve: No module named
db.fields
---  ---

So I compared some schema and content, figured out it is from 
reviewboard.django_project_version. Then I took dumpdb this time, and 
deleted the last record of reviewboard.django_project_version, retried 
upgrading, it now fails with


-  --
Creating tables ...
Upgrading Review Board from 1.7.12 to 1.7.28
There are unapplied evolutions for accounts.
There are unapplied evolutions for attachments.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for site.
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
The stored evolutions do not completely resolve all model changes.
Run `./manage.py evolve --hint` to see a suggestion for the changes 
required.

The following are the changes that could not be resolved:
In model attachments.FileAttachment:
Field 'orig_filename' has been added
In model hostingsvcs.HostingServiceAccount:
Field 'hosting_url' has been added
The model auth.Message has been deleted
In model reviews.FileAttachmentComment:
Field 'extra_data' has been added
In model reviews.ReviewRequest:
Field 'last_review_activity_timestamp' has been added
Field 'depends_on' has been added
Field 'last_review_timestamp' has been deleted
In model reviews.ReviewRequestDraft:
Field 'depends_on' has been added
In model accounts.Profile:
Field 'timezone' has been added
Field 'open_an_issue' has been added
Field 'extra_data' has been added
In model diffviewer.DiffSetHistory:
Field 'last_diff_updated' has been added
In model diffviewer.FileDiff:
Field 'diff_hash' has been added
Field 'parent_diff_hash' has been added
Field 'diff64' has been added
Field 'parent_diff64' has been added
Field 'parent_diff' has been deleted
Field 'diff' has been deleted
Error: Your models contain changes that Django Evolution cannot resolve 
automatically.

How can I proceed? I have a backup before this happens (quite old so not 
possible to load back).

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Re: There are unapplied evolutions when upgrade from 2.0.21 to 2.5.2

2015-12-08 Thread Christian Hammond
Hi Weibo,

There should be a note right before the log output saying to ignore those
errors unless the upgrade fails. It looks like it was completely successful.

What I'd do now is check the Apache error log and the reviewboard.log (if
enabled), and look at the errors there. There should be a traceback and
more log details, which we can use to help diagnose this.

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Tue, Dec 8, 2015 at 7:34 PM, Weibo Li  wrote:

> Running ReviewBoard 2.0.21 on centos 6 with python 2.6.6. When upgrade
> with *rb-site upgrade*, it outputs:
>
> *Rebuilding directory structure*
> *Updating database. This may take a while.*
>
> *The log output below, including warnings and errors,*
> *can be ignored unless upgrade fails.*
>
> *--  --*
> *Creating tables ...*
> *Creating table accounts_trophy*
> *Creating table attachments_fileattachmenthistory*
> *Creating table diffviewer_rawfilediffdata*
> *Creating table notifications_webhooktarget_repositories*
> *Creating table notifications_webhooktarget*
> *Creating table webapi_webapitoken*
> *Upgrading Review Board from 2.0.21 to 2.5.2*
> *There are unapplied evolutions for accounts.*
> *There are unapplied evolutions for attachments.*
> *There are unapplied evolutions for diffviewer.*
> *There are unapplied evolutions for notifications.*
> *There are unapplied evolutions for reviews.*
> *There are unapplied evolutions for webapi.*
> *Adding baseline version for new models*
> *Evolutions in notifications baseline: webhooktarget_extra_state,
> webhooktarget_extra_data_null*
> *Project signature has changed - an evolution is required*
> *Installing custom SQL ...*
> *Installing indexes ...*
> *Installed 0 object(s) from 0 fixture(s)*
> *Evolution successful.*
> *---  ---*
>
> *Resetting in-database caches.*
>
> *Upgrade complete!*
>
> I got 500 Internal Server Error when apache, memcached and MySQL
> restarted.
>
> How can I solve this problem?
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://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/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Re: RBtools 0.7.4 error 105 path not found.

2015-12-08 Thread Christian Hammond
Hi Rob,

We've made a lot of improvements to Bitbucket support since we released
2.0.1 in May of last year. You might find 2.0.21 to work better for you.

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Tue, Dec 8, 2015 at 6:52 AM, Rob Dejournett 
wrote:

> Also the server log is here:
>
> 2015-12-08 14:49:54,420 - ERROR - None - rdejournett -
> /api/review-requests/5110/diffs/ - Error uploading new diff: Not Found
> Traceback (most recent call last):
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/webapi/resources/diff.py",
> line 292, in create
> request.FILES.get('parent_diff_path'))
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/reviews/forms.py",
> line 116, in create
> history)
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/diffviewer/forms.py",
> line 69, in create
> request=self.request)
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/diffviewer/managers.py",
> line 156, in create_from_upload
> save=save)
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/diffviewer/managers.py",
> line 210, in create_from_data
> limit_to=diff_filenames):
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/diffviewer/managers.py",
> line 300, in _process_files
> request=request))):
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/scmtools/models.py",
> line 238, in get_file_exists
> base_commit_id, request)
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/scmtools/models.py",
> line 415, in _get_file_exists_uncached
> base_commit_id=base_commit_id)
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/hostingsvcs/bitbucket.py",
> line 177, in get_file_exists
> self._api_get_src(repository, path, revision, base_commit_id)
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/hostingsvcs/bitbucket.py",
> line 214, in _api_get_src
> return self._api_get(url, raw_content=True)
>   File
> "/usr/lib/python2.6/site-packages/ReviewBoard-2.0.1-py2.6.egg/reviewboard/hostingsvcs/bitbucket.py",
> line 265, in _api_get
> raise Exception(e.read())
> Exception: Not Found
>
>
> On Tuesday, December 8, 2015 at 9:03:25 AM UTC-5, Rob Dejournett wrote:
>>
>> It's reviewboard 2.0.1, we are using Git version 1.9.5.  I am not the
>> review board administrator, but I have access to the linux box.  If you can
>> point me to where the logs are that'd be really helpful.
>>
>> Thanks!
>>
>>
>> On Monday, December 7, 2015 at 5:02:33 PM UTC-5, David Trowbridge wrote:
>>>
>>> What version of Review Board? What version control system (and version
>>> thereof)? Is there anything in the server log?
>>>
>>> -David
>>>
>>>
>>> On Mon, Dec 7, 2015 at 11:43 AM Rob Dejournett 
>>> wrote:
>>>
 Sorry if this is a double post.  Getting error with some files posting
 using RBTools.  Java files seem to work fine.  I use something called Mirth
 Connect which generates XML files as code.  Basically when RBT tries to
 upload the diff it fails with the 105 error.  Attached is the diff.

 --
 Supercharge your Review Board with Power Pack:
 https://www.reviewboard.org/powerpack/
 Want us to host Review Board for you? Check out RBCommons:
 https://rbcommons.com/
 Happy user? Let us know! https://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/d/optout.

>>> --
>>> -David
>>
>> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://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/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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 

Re: Automatic Merging after successfull review

2015-12-08 Thread Christian Hammond
Hi Harshal,

Review Board does not handle the merging of code into a codebase. Many
companies have different policies on when something is ready to merge, and
many different setups for how code ends up in the codebase, and on top of
that, there's different sets of problems for different SCMs (git, svn,
Perforce, etc.) that all result in some real challenges in this area.

Instead, we focus on the code review experience, and leave it up to the
author of the code or maintainer of the codebase to handle merges. We make
this easier with RBTools, using the "rbt land" command (
https://www.reviewboard.org/docs/rbtools/0.7/rbt/commands/land/).

Down the road, we may offer some click-to-merge support, but it won't
happen before 3.0, which is a ways out.

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Tue, Dec 8, 2015 at 6:40 AM, Harshal Kulkarni 
wrote:

> Hi All,
>
> I am newbie to reviewboard, I have one small question. Does reviewboard
> has the functionality of automatic merging the pull request after
> successfull code review?
>
>
> Thanks,
> Harshal
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://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/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Re: Not able to update Bitnami one-click install Reviewboard v2.0.18 to v2.0.21.

2015-12-08 Thread Christian Hammond
Hi,

You'll need to reach out to the Bitnami support group. They have a custom
way that Review Board is installed, and it looks like issuing an
easy_install command is not sufficient to update the version Apache is
using. Unfortunately, I don't know the answer to that, but they would.

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Tue, Dec 8, 2015 at 5:54 AM, Weibo Li  wrote:

> We are running Bitnami one-click installed Reviewboard v2.0.18 and about
> to upgrade it to v2.0.21.
> I logged in with root user and issued the following commands:
>
> $easy_install -U ReviewBoard==2.0.21
> $rb-site upgrade /data/rb/apps/reviewboard/rb-sites/reviewboard/
>
>
> the output was:
>
>
> ---
>
> Rebuilding directory structure
>
> Updating database. This may take a while.
>
>
> The log output below, including warnings and errors,
>
> can be ignored unless upgrade fails.
>
>
> --  --
>
> Creating tables ...
>
> Installing custom SQL ...
>
> Installing indexes ...
>
> Installed 0 object(s) from 0 fixture(s)
>
> No evolution required.
>
> ---  ---
>
>
> Resetting in-database caches.
>
>
> Upgrade complete!
>
>
> ---
>
>
> Then I restart apache, memcached and mysql then visit it again. But it
> says:
>
>
> Review Board version mismatch
>
> The version of Review Board running does not match the version the site
>> was last upgraded to. You are running *2.0.18* and the site was last
>> upgraded to *2.0.21*.
>
> Please upgrade your site to fix this by running:
>>
>> $ rb-site upgrade /data/rb/apps/reviewboard/rb-sites/reviewboard
>>
>>
> How could this happend? It there some version configure that I need to
> change as well?
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://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/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.


Re: Database upgrade from 1.7.27 to 2.5.2

2015-12-08 Thread Christian Hammond
Hi Ralph,

Glad to hear it!

The condensediffs savings should definitely be better in 2.5.x.

In 2.0, we condensed by de-duplicating diffs (if you uploaded 3 revisions
of a diff, but a diff for a file remained the same between revisions, we no
longer store multiple copies of it).

In 2.5.x, we moved from a base64 encoding of diffs (previously needed due
to lack of binary field support in Django + encoding issues with databases)
to gzip-compressed storage of diffs. This offers a much greater savings.
We've seen it as high as 80% on a real-world install.

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Tue, Dec 8, 2015 at 8:01 AM, rfs  wrote:

> Hi Christian,
>
> Thanks, that was exactly the problem. After switching to InnoDB, the
> upgrade to 2.5.2 completes, and I have a working install.
> The one other change I had to make was the memcached backend name in
> settings_local.py (CacheClass -> MemcacheCache).
>
> I did notice a difference in the "condensediffs" operation, under 2.0.18
> it reported 21% savings, while under 2.5.2 it reported around 40% -- in
> both cases I started from the same 1.7.27 database. If that is something of
> concern, I can provide more details.
>
> -Ralph
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://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/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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/d/optout.