maas-devel team mailing list archive

[Raphaël Badin <raphael.badin@xxxxxxxxxxxxx>]

On 08/14/2014 05:23 PM, Julian Edwards wrote:
> Dear all
>
> I need to backport a data migration 0099 to 1.6 from trunk, however 1.6
> is currently only on 0088.  All of these would need to get backported as
> well:
>
> 0089_create_nodegroupinterface_name.py
> 0090_initialise_nodegroupinterface_name.py
> 0091_add_boot_type_to_node.py
> 0092_populate_node_boot_type.py
> 0093_add_eventtype_and_event.py
> 0094_add_error_description.py
> 0095_add_event_description.py
> 0096_add_power_state_to_node.py
> 0097_add_largefile_model.py
> 0098_add_bootresource_models.py
>
> However, a quick look at these shows that 0090 needs a code change
> that's not in 1.6 (make_name_from_interface) so I can't just backport
> these en-masse.
>
> Does anyone know if we can just backport the single data migration
> without South breaking?
>
> Failing that, I will have to do something in the packaging to do this
> migration manually :(

As discussed yesterday with Julian, there is a solution worth testing: 
we could backport the 0099 data migration as 0088_2 in 1.6 and create an 
empty 0088_2 migration in trunk.  This is a bit of a hack but since 
we're adding a data migration (and not a schema migration) we shouldn't 
have to modify the other migrations (0089-0098).