Hi Kelvin, ... you can't do that anymore (pulling from develop immediately)... you have to first upgrade your instance (aka database schema with Fineract 1.6.0... the release that is... exactly that version)... and only after that you can do the upgrade with the current develop branch (we try to keep this as error free as possible, but develop is considered unstable until we release).
Hope that helps. Cheers, Aleks On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome <kel...@ciniter.com> wrote: > Hi Arnold, > > We pulled in from the develop branch > > On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics <galovicsarn...@gmail.com> > wrote: > >> Hi Kelvin, Sifiso, >> >> *Kelvin: * >> Could you please share a little more info which version of Fineract >> you're trying to use? >> >> The thing is, the latest release version (1.6.0) doesn't have Liquibase >> at all, it still runs Flyway migrations. Only the develop branch (later to >> be 1.7.0) got switched to Liquibase. >> >> *Sifiso:* >> Could you please start another thread on your problems? A database >> upgrade seems to be another thing to take care of. Also, make sure to share >> the kind of errors you're experiencing. >> >> Best, >> Arnold >> >> On Mon, Mar 7, 2022 at 8:59 AM <sif...@skyburgsystems.org> wrote: >> >>> Hi Kelvin, >>> >>> >>> >>> We are actually in the same predicament as you. However we have upgraded >>> our database from MySQL 5.7 as advised to MariaDB 10.6. If we use data from >>> version 18.03.01 it fails to migrate our data. If we use databases running >>> on 1.5.0 release it completes the startup but the system login fails. >>> >>> >>> >>> Let’s hear from the others what challenges they’ve experienced, maybe >>> there is a workaround already. >>> >>> >>> >>> Regards, >>> >>> Sifiso >>> >>> >>> >>> *From:* Kelvin Ikome <kel...@ciniter.com> >>> *Sent:* Monday, 07 March 2022 9:29 AM >>> *To:* dev@fineract.apache.org >>> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade >>> >>> >>> >>> Hi everyone, >>> >>> >>> >>> We have upgraded from Fineract 1.5.0 to 1.6.0. >>> >>> After dropping the flyway migrations table (schema_version), Liquibase >>> runs it's own migrations which fails (in recreating tables which already >>> exist) because we are aiming to re-use DB with existing data from Fineract >>> 1.5.0. >>> >>> >>> >>> Any ideas on how to address this would be greatly appreciated. >>> >>> >>> >>> Kind regards >>> >>> >>> >>> -- >>> >>> *Kelvin Ikome* >>> Chief Executive Officer >>> >>> [image: facebook icon] <https://www.facebook.com/ciniter.ltd> [image: >>> twitter icon] <https://twitter.com/ciniter_ltd> [image: youtube icon] >>> <https://www.youtube.com/channel/UCfOgsIgX3l1TT4G79NBUt-A> [image: >>> linkedin icon] <https://www.linkedin.com/company/ciniter> >>> >>> >>> *t:* >>> *m:* >>> *e:* >>> *a:* >>> >>> +(237) 677-666-659 >>> kel...@ciniter.com >>> Ciniter, Molyko, Buea, South West, Cameroon >>> *www.ciniter.com* <http://www.ciniter.com/> >>> >>> >>> >> > > -- > Kelvin Ikome > Chief Executive Officer [image: facebook icon] > <https://www.facebook.com/ciniter.ltd> [image: twitter icon] > <https://twitter.com/ciniter_ltd> [image: youtube icon] > <https://www.youtube.com/channel/UCfOgsIgX3l1TT4G79NBUt-A> [image: > linkedin icon] <https://www.linkedin.com/company/ciniter> > > > t: > m: > e: > a: +(237) 677-666-659 > kel...@ciniter.com > Ciniter, Molyko, Buea, South West, Cameroon > www.ciniter.com >
