Using the Debian-provided Aegir 1.6: thanks for sorting out the site-comparison issue!

But now I have an issue that I cannot understand: Aegir Clone reports that the target Platform is in error as module date-7.x-2.0-alpha4 (7000) is an unsuitable target for source Package date-7.x-2.0-alpha4 (7001) but .... I am baffled because, for one thing, how did the production Platform pick up schema_version 7001 and, another, how did the drush make create one with schema_version 7000?

The target Platform was created from a makefile resulting from drush @production.site.com generate-makefile newMake.make after I re-verified the production Platform; the production Site; the target new Site in that order and still the schema_version is reported.

I have every reason to believe that the date modules are the same on both source and target Platforms; the makefile was generated with version numbers and the production Platform's date module was the result of drush @production.site.com dl date-7.x-2.0-alpha4

So ..... is this a bug: Aegir incorrectly picking up scheme_versions or .... in any case what are the possible remedies/ further diagnostics?

Comments

aleksey.tk’s picture

aleksey.tk commented

Strange that no one saw this bug before because i'm experiencing exactly the same problem - i have exact clone of two platforms (in different branches in git, though) and have some modules with different schemas reported by 'compare platform' feature:

admin_menu 6.x-1.8 (6302) - admin_menu 6.x-1.8 (6001)
apachesolr 6.x-2.0-beta3 (6007) - apachesolr	6.x-2.0-beta3 (6005)

Are there anything i can do to force Aegir to think that they're the same? Why this is happening?

aleksey.tk’s picture

aleksey.tk commented
Status: Active » Fixed

Ok, in fact the only thing that you need to do is to be sure that the site you're cloning already have all the schema updates in database. So to fix schema versions incompatibility you only need to run update.php before cloning original website.

themusician’s picture

themusician commented

cyberpunk, that is right. If things get out of sync as they sometimes can you can "rollback" for Aegir. I did a small write-up for my users. http://maxbronsema.com/blog/2012/01/19/mitigating-errors-when-migrating-...

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

anarcat’s picture

anarcat commented
Category: bug » support
anarcat’s picture

anarcat commented
Issue summary: View changes

"after" I re-verified ... to be absolutely clear