The fresh installation of 4.0.12 was to move away from system packages to source
I'm all ready to upgrade to 4.0.13, but on make upgrade-database, is it best to run it as upgrade from 4.0.12 or from 4.0.4 which was the previous system package? I reckon from 4.0.4 but I don't want to cause any other damage along the way. On Thursday 04 Jul 2013 21:35:43 Joop wrote: > Samuel Jones wrote: > > Would the regular upgrade path from 4.0.12 --> 4.0.13 resolve the issues, > > leave the data where it is and update RT around it? > > > > 4.0.12 was a fresh empty install and then the data imported as the > > documents say to do. (just importing the mysql essentially, with some > > scripting to adjust it from SQLite to MySQL) > > No, that won't probably not work. If the imported data is from 4.0.3 > then you'll need to run 'make upgrade-database' and fill in the > requested pieces of information. In short, you'll need the source > package and it will apply the updates that are in ./etc/upgrade/.. from > the version you have to the version you specify or till the last that is > available, thats is if you have 4.0.13 source it will stop at 4.0.13 > Without reading back I'm suspecting that you're using a rt package > (debian?) and then I don't know if you can run 'make upgrade-database'. > Someone on the list will probably know what todo then (got some ideas > but they are rather hackish, I use RT from source, then no such problems) > > Regards, > > Joop