When installing a new package EBox::MigrationBase assumess always that his version is zero

[javier.amor.garcia@…]

THe version is retrevied from a gconf key, if there isn't the entry it is assumed to be zero. (see EBox::MigrationBase::_checkCurrentGConfVersion for details)

THis means that a freshly installed module should pass by all migration stages which can be a good source of bugs and inconsistenvies

[juruen@…]

That's the expected behaviour.

I cannot see how a migration script could cause inconsistencies unless it is broken.

Migration scripts might be used to either:

• Adapt older data model into a newer one (No previous data, no actions are taken apart from marking the current data version. Note that not marking data model version actually is a source of bugs and inconsistencies)
• Populate with new data which do not depends on previous data.

Please provide an example of script which is not broken and causes data inconsistency for further discussion.

[juruen@…]

If necessary we could trigger the execution of the migration scripts on software upgrades as long as we set the current data model in fresh installations.

[ejhernandez@…]

This issue may arise from the preconfigured data in a model. That problem comes from MIME and Extension filter models which requires some preconfigured data and it may cause inconsistencies.

[Xyovzuzqlia]

Pvvgch  http://rusprivatfrands.yolasite.com/ nbsibvz  http://rusprivatdating.yolasite.com/ tjiqzkv  http://rusintimznakomstvo.yolasite.com/ spkeghh.

[Ugrdcghszzz]

Wwzcpa  http://rueroznakomstvo.yolasite.com/ iqmqids  http://ruerofrands.yolasite.com/ vfzcsvh  http://rusprivatznakomstvo.yolasite.com/ fkyvltf.

[Qhdpqkupxyt]

Lsirwn  http://ruseromeeting.yolasite.com/ vcwuegu  http://ruserofrands.yolasite.com/ viqybmj  http://ruserodating.yolasite.com/ opzljhf.