Currently the migrations fail to apply on mysql django.db.utils.OperationalError: (1829, "Cannot drop column 'id': needed in a foreign key constraint 'D1a8c915f90ee0694e71f27b384a7341' of table 'toaster.orm_customimagerecipe_packages'") This is because of mysql doesn't support being able to drop a primary key which is currently 'in use'. orm.0002_auto_20151210_1209 We may need to detect if we're using mysql and do a slightly different migration.
After investigation we have no choice other than to reset migrations I've tried adding an intermediate migration which drops the CustomImageRecipe table and recreates it but this hits a Django bug https://code.djangoproject.com/ticket/24225 I've also tried renaming it and various combinations of removing all the fields which hold the foreign key relationship and then re-creating them with the corrected relationships. We also have a slightly broken migration tree with two migrations 0002 that depend on the initial migration.
If I have a toaster.sqlite from jethro, these migrations break on the existing jethro database. If so, we will need to spell out in the docs that in order to take advantage of the new image customization feature users will need to start with a fresh db.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=8469e5802590551dbf88a26539b9cfe5710c074d (Bitbake rev: 19bd63fc3a28dcbd0f531a5b06a037da34568bac)
Verified while setting up MySQL instance for GDC.