Re: Database upgrade from 1.7.27 to 2.5.2

2015-12-07 Thread Christian Hammond 
Hi,

Looks like you have a mix of InnoDB and MyISAM tables. You're going to need
to update all tables in your database to use InnoDB (or configure MySQL to
use MyISAM by default, though InnoDB is preferable).

The workaround you have that results in the "attachment_histories" bit is
due to installing with 2.5.x, and then restoring your database without
wiping the new tables, so it's trying to create tables that were already
created during the 2.5 'rb-site install'. You don't want to go that route,
so be sure to fix the MyISAM vs. InnoDB issue and then upgrade to a brand
new, freshly-created database.

Hope that helps!

Christian

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

On Mon, Dec 7, 2015 at 6:40 PM, rfs  wrote:

> Some additional information after further experimentation:
>
> * I tried upgrading from the same 1.7.27 database to 2.0.18. This worked
> perfectly fine. I ran compressdiffs afterwards as suggested, that worked
> too.
> * I then tried upgrading from 2.0.18 to 2.5.2, but got the same "Can't
> create table 'reviewboard.#'" error.
>
> Next I scripted the upgrade from 1.7.27 to 2.5.2, and tried a few
> variations, including location of the database, etc.
> The process is:
> 1) Create empty database
> 2) Restore my 1.7.27 database
> 3) Run rb-site upgrade
>
> That reliably triggers the "Can't create table" error. However, if I add
> one step:
> 1) Create empty database
> 1.5) Run rb-site install
> 2) Restore my 1.7.27 database
> 3) Run rb-site upgrade
>
> Then the "Can't create table" error is avoided, and it manages to apply
> many django evolutions. Eventually it fails with:
> CommandError: Error applying evolution: (1050, "Table
> 'reviews_reviewrequest_file_attachment_histories' already exists")
> which is not entirely unexpected since I ran rb-site install which likely
> created that table.
>
> I am using mariadb-5.5.44 on CentOS 7.1.
>
> -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.

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

2015-12-07 Thread Stephen Gallagher 
On Mon, Dec 7, 2015 at 11:21 AM 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?
>
>>
>>

Hmm, looks like it should have at least been requiring 0.7.5, not 0.7.1.
Was that a typo or were you looking at the 2.0.18 requirement?

Anyway, I'm building an updated version that explicitly requires
django-evolution 0.7.6.

-- 
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: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

2015-12-07 Thread Stephen Gallagher 
On Sat, Dec 5, 2015 at 10:29 AM Paul Fee  wrote:

> Hi Stephen,
>
> That's great news, I had been wondering if Fedora/RHEL users would be
> seeing RB2.5 soon.
>
> On Fedora, it looks like the Django packages have moved ahead to 1.8, but
> RB still needs 1.6.  Hence ReviewBoard has disappeared from Fedora from F22
> onwards :(
>
>
Yeah, I've dropped it from the official repositories. I *had* been
maintaining it as a separate COPR repository that contains an old version
of Django, but honestly no one seems to actually be using it.
Realistically, I think people just prefer to deploy something important
like Review Board atop RHEL or CentOS rather than Fedora, and since
packaging it on Fedora is basically impossible at this time (not including
deployment via Docker or similar), it just isn't worth the effort to
maintain there.



> Nice to see that the situation on RHEL+EPEL is better.  For users on that
> platform, what can we expect when installing the upgrade?  If I already
> have a 2.0.18 installation and a site populated with users/reviews/comments
> etc. will this migrate without effort up to RB 2.5.2 or is anything else
> required, e.g. database backup/restore?
>
>
The expected behavior is that all existing reviews, users, repositories and
everything else should remain after the upgrade. That being said, if you
are upgrading to a new major release and do NOT do a full backup to be on
the safe side, you have made a grave error in judgement.

Also, as I said in the initial email: this is currently in the testing
repository precisely to catch any such issues before it goes to stable and
everyone running Review Board picks it up on their next yum update. So if
there are bugs preventing the trivial upgrade, let's get them identified
and fixed before I push this to the stable repo.

-- 
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: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

2015-12-07 Thread Stephen Gallagher 
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 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: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

2015-12-07 Thread sean 
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 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: GitLab hosting stopped working

2015-12-07 Thread Christian Hammond 
Hi Ian,

Can you verify that the username associated with those repositories still
has the necessary access permissions on the GitLab server?

I checked the code in question, involving repository verification and how
credentials are used, and it hasn't changed since 2.0.x, so at this point
I'd want to verify the GitLab setup.

Christian

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

On Sun, Dec 6, 2015 at 3:11 PM, Ian  wrote:

> Any idea on how I could fix this?
>
> Ian
>
>
> On Tuesday, November 17, 2015 at 4:56:19 PM UTC-8, Ian wrote:
>>
>> Yes, existing review requests against the repository are loading, I just
>> can't change the repository configuration.
>>
>> Ian
>>
>> On Monday, November 16, 2015 at 11:30:51 PM UTC-8, Christian Hammond
>> wrote:
>>>
>>> Hi Ian,
>>>
>>> Do existing review requests against this repository still work? Is this
>>> solely when changing the repository configuration?
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - chri...@beanbaginc.com
>>> Review Board - https://www.reviewboard.org
>>> Beanbag, Inc. - https://www.beanbaginc.com
>>>
>>> On Mon, Nov 16, 2015 at 7:47 PM, Ian  wrote:
>>>
 I recently updated to ReviewBoard 2.5.1 and now I can't change any of
 my GitLab repositories, when I do it says "A repository with this name was
 not found on this group, or your user may not have access to it."  I
 verified that I can log into my GitLab installation and see the
 repositories from a web browser running on the ReviewBoard server using the
 same account.  I don't suppose this is a known issue?  My config looks like
 this.

 Hosting Service: GitLab
 Service URL: https://gitlab.domain.com
 Account: username
 Repository Type: Git
 Repository Plan: Group
 GitLab Group Name: groupname
 Repository Name: repositoryname

 Ian

 --
 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.
>>>
>>> --
> 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-07 Thread rfs 
Some additional information after further experimentation:

* I tried upgrading from the same 1.7.27 database to 2.0.18. This worked 
perfectly fine. I ran compressdiffs afterwards as suggested, that worked 
too.
* I then tried upgrading from 2.0.18 to 2.5.2, but got the same "Can't 
create table 'reviewboard.#'" error.

Next I scripted the upgrade from 1.7.27 to 2.5.2, and tried a few 
variations, including location of the database, etc.
The process is:
1) Create empty database
2) Restore my 1.7.27 database
3) Run rb-site upgrade

That reliably triggers the "Can't create table" error. However, if I add 
one step:
1) Create empty database
1.5) Run rb-site install
2) Restore my 1.7.27 database
3) Run rb-site upgrade

Then the "Can't create table" error is avoided, and it manages to apply 
many django evolutions. Eventually it fails with:
CommandError: Error applying evolution: (1050, "Table 
'reviews_reviewrequest_file_attachment_histories' already exists")
which is not entirely unexpected since I ran rb-site install which likely 
created that table.

I am using mariadb-5.5.44 on CentOS 7.1.

-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.

RBTools 0.7.4 error 105 POSTing a diff

2015-12-07 Thread Rob Dejournett 
I am doing some development which is tracked by XML files.  It looks like 
these XML files are breaking RBTools (java files post file).

I get a 105 error stating path is not found.  Not really sure what this 
means.  But I strongly suspect its due to parsing of the diff.

Attached is said diff (which i hacked the post.py to display).



-- 
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.


mydiff
Description: Binary data

RBtools 0.7.4 error 105 path not found.

2015-12-07 Thread Rob Dejournett 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>>> RBTools 0.7.4
>>> Python 2.7.5 (default, Mar  9 2014, 22:15:05) 
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)]
>>> Running on Darwin-13.4.0-x86_64-i386-64bit
>>> Home = /Users/rdejournett
>>> Current directory = /Users/rdejournett/mfss-rcm-mirth
>>> Running: git version
>>> Checking for a Git repository...
>>> Running: git rev-parse --git-dir
>>> Running: git config core.bare
>>> Running: git rev-parse --show-toplevel
>>> Running: git symbolic-ref -q HEAD
>>> Running: git config --get branch.RCMSTATE-763.merge
>>> Running: git config --get branch.RCMSTATE-763.remote
>>> Running: git config --get remote.origin.url
>>> repository info: Path: g...@bitbucket.org:mfgit/mfss-rcm-mirth.git, Base path: , Supports changesets: False
>>> Making HTTP GET request to https://rb.dev.medfusion.net/api/
>>> Running: git rev-parse b269f02
>>> Running: git rev-parse b269f02b7feddcba1b53c9e9f6093e7b50374208^
>>> Running: git merge-base 84d258f5e9aa911bf55a048ab6b968bca91098cb origin/development
>>> Running: git rev-parse --git-dir
>>> Running: git -c core.quotepath=false -c diff.noprefix=false diff --no-color --full-index --ignore-submodules -M --no-ext-diff 84d258f5e9aa911bf55a048ab6b968bca91098cb..b269f02b7feddcba1b53c9e9f6093e7b50374208
>>> Making HTTP GET request to https://rb.dev.medfusion.net/api/review-requests/5098/?only-links=diffs%2Cdraft=absolute_url%2Cbugs_closed%2Cid%2Cstatus
>>> Making HTTP GET request to https://rb.dev.medfusion.net/api/review-requests/5098/diffs/?only-fields=
>>> Making HTTP POST request to https://rb.dev.medfusion.net/api/review-requests/5098/diffs/
>>> Got API Error 105 (HTTP code 400): One or more fields had errors
>>> Error data: {u'fields': {u'path': [u'Not Found']}, u'stat': u'fail', u'err': {u'msg': u'One or more fields had errors', u'code': 105}}
Traceback (most recent call last):
  File "/usr/local/bin/rbt", line 8, in 
load_entry_point('RBTools==0.7.4', 'console_scripts', 'rbt')()
  File "/Library/Python/2.7/site-packages/RBTools-0.7.4-py2.7.egg/rbtools/commands/main.py", line 133, in main
command.run_from_argv([RB_MAIN, command_name] + args)
  File "/Library/Python/2.7/site-packages/RBTools-0.7.4-py2.7.egg/rbtools/commands/__init__.py", line 612, in run_from_argv
exit_code = self.main(*args) or 0
  File "/Library/Python/2.7/site-packages/RBTools-0.7.4-py2.7.egg/rbtools/commands/post.py", line 799, in main
base_dir=base_dir)
  File "/Library/Python/2.7/site-packages/RBTools-0.7.4-py2.7.egg/rbtools/commands/post.py", line 481, in post_request
raise CommandError(u'\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff


diff --git a/mfss-rcm-mirth-core/pom.xml b/mfss-rcm-mirth-core/pom.xml
index a90ed7ac3b983670edb3c0068b071df6a57cd48f..88f626bb3bba3c95d1882dd75d5799579251e16b 100644
--- a/mfss-rcm-mirth-core/pom.xml
+++ b/mfss-rcm-mirth-core/pom.xml
@@ -53,7 +53,41 @@
 maven-jar-plugin
 2.6
 
-	${parent.dir}
+	../deploy/custom-lib/Estatements
+
+			
+			
+		
+org.apache.maven.plugins
+maven-clean-plugin
+3.0.0
+
+
+	
+		
+			../deploy/custom-lib/Estatements
+			
+*.jar
+			
+			true
+		
+		
+			deploy
+			
+*
+			
+			true
+		
+
+	
 
 			
 		
diff --git a/mfss-rcm-mirth-core/src/main/java/com/medfusion/estatement/ge/ProcessGE.java b/mfss-rcm-mirth-core/src/main/java/com/medfusion/estatement/ge/ProcessGE.java
index 3c6091fa9105c3b6f879008f0314e969fd8ab2fd..f19b9292f857f2187b5f4776d16f8e2ac2e76a86 100644
--- a/mfss-rcm-mirth-core/src/main/java/com/medfusion/estatement/ge/ProcessGE.java
+++ b/mfss-rcm-mirth-core/src/main/java/com/medfusion/estatement/ge/ProcessGE.java
@@ -3,6 +3,7 @@ package com.medfusion.estatement.ge;
 import java.io.StringReader;
 import java.math.BigDecimal;
 import java.util.ArrayList;
+import java.util.Calendar;
 import java.util.List;
 import java.util.UUID;
 
@@ -40,7 +41,7 @@ public class ProcessGE {
 		//TODO Pradeep to research
 	}
 
-	public String ESTtoXML(String est, String filename, boolean useInsAging) {
+	public String ESTtoXML(String est, String filename, boolean useInsAging, float

Database upgrade from 1.7.27 to 2.5.2

2015-12-07 Thread rfs 
I'm attempting to migrate an existing ReviewBoard database from 1.7.27 to 
2.5.2, on a CentOS 7.1 system using sgallagher's RPMs.
The error looks like a permission problem, but on same system, I am able to 
create a new site with "rb-site install" and it works nicely.
I then dropped dropped the reviewboard database, created a new one, and 
restored from mysqldump of 1.7.27 data. That's where I run into trouble.
Any suggestions on where to look to debug this? The --debug flag did not 
seem to make any difference, BTW.

# rb-site --debug upgrade rb
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

[!] There was an error synchronizing the database. Make sure the
database is created and has the appropriate permissions, and then
continue.
[!] Details: (1005, "Can't create table 'reviewboard.#sql-4db_8'
(errno: 150)")

Press Enter to continue^CTraceback (most recent call last):
  File "/bin/rb-site", line 9, in 
load_entry_point('ReviewBoard==2.5.2', 'console_scripts', 'rb-site')()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
line 1922, in main
command.run()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
line 1724, in run
site.sync_database()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
line 442, in sync_database
force_wait=True)
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
line 1096, in error
input('Press Enter to continue')
KeyboardInterrupt

Thanks,
-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: RBtools 0.7.4 error 105 path not found.

2015-12-07 Thread David Trowbridge 
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+unsubscr...@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-07 Thread Stephen Gallagher 
Did you run this with the recent django-evolution 0.7.6 update? That
specifically addresses some upgrade issues unique to MySQL.

On Mon, Dec 7, 2015, 9:40 PM rfs  wrote:

> Some additional information after further experimentation:
>
> * I tried upgrading from the same 1.7.27 database to 2.0.18. This worked
> perfectly fine. I ran compressdiffs afterwards as suggested, that worked
> too.
> * I then tried upgrading from 2.0.18 to 2.5.2, but got the same "Can't
> create table 'reviewboard.#'" error.
>
> Next I scripted the upgrade from 1.7.27 to 2.5.2, and tried a few
> variations, including location of the database, etc.
> The process is:
> 1) Create empty database
> 2) Restore my 1.7.27 database
> 3) Run rb-site upgrade
>
> That reliably triggers the "Can't create table" error. However, if I add
> one step:
> 1) Create empty database
> 1.5) Run rb-site install
> 2) Restore my 1.7.27 database
> 3) Run rb-site upgrade
>
> Then the "Can't create table" error is avoided, and it manages to apply
> many django evolutions. Eventually it fails with:
> CommandError: Error applying evolution: (1050, "Table
> 'reviews_reviewrequest_file_attachment_histories' already exists")
> which is not entirely unexpected since I ran rb-site install which likely
> created that table.
>
> I am using mariadb-5.5.44 on CentOS 7.1.
>
> -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.