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 <s...@m2mobi.com> 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:* > > ------------------ <begin log output> ------------------ > > 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. > > ------------------- <end log output> ------------------- > > > *the next run reduces this to:* > > > ------------------ <begin log output> ------------------ > > Creating tables ... > > There are unapplied evolutions for webapi. > > Installing custom SQL ... > > Installing indexes ... > > Installed 0 object(s) from 0 fixture(s) > > No evolution required. > > ------------------- <end log output> ------------------- > > > 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. > -- 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.
