Closed (duplicate)
Project:
Provision
Version:
6.x-0.4-alpha3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Jan 2010 at 17:02 UTC
Updated:
5 Jan 2010 at 14:46 UTC
Here's what I'm getting when I try to clone a drupal 5.x site using zengine... I'm trying to clone and update to test the migration but here are the errors I'm getting in the failed aegir task log...
Running: /usr/bin/php /var/aegir/drush/drush.php --root='/var/aegir/platfo... (Expand)Running: /usr/bin/php /var/aegir/drush/drush.php --root='/var/aegir/platforms/drupal-5.7' --redirection='0' --web_host='aegir.nautilusstudios.com' --web_ip='174.143.174.144' --db_host='localhost' --uri='http://royalpalaceballrooms.com' 'provision' 'deploy' 'update.royalpalaceballrooms.nautilusstudios.com' '/var/aegir/backups/royalpalaceballrooms.com-20100104.165005.tar.gz' --backend
Undefined variable: context
Undefined variable: string
X The external command could not be executed due to an application error.
...
Rebuild node type cache
Rebuild module cache
X Drush command could not be completed.
X Output from failed command : Cache cleared. Fatal error: Cannot redeclare... (Expand)Output from failed command : Cache cleared. Fatal error: Cannot redeclare zengine_init() (previously declared in /var/aegir/platforms/drupal-5.7/sites/royalpalaceballrooms.com/themes/engines/zengine/zengine.engine:30) in /var/aegir/platforms/drupal-5.7/sites/update.royalpalaceballrooms.nautilusstudios.com/themes/engines/zengine/zengine.engine on line 32
X An error occurred at function : drush_provision_drupal_provision_clone
Removed unused clone site package
Changes for drush_provision_drupal_pre_provision_clone module have been rolled back.
Command dispatch complete
X Output from failed command :
X An error occurred at function : drush_hosting_hosting_task
Changes for drush_hosting_hosting_task module have been rolled back.
Comments
Comment #1
anarcat commentedThis is a drush bug, see #644126: drush loads duplicate command files.
Comment #2
qbnflaco commentedFYI, if anyone comes across this issue, here was my workaround...
I resorted to quickly switching the theme to garland on production (cringe) and doing the backup and switching back as soon as it's done. Then deploying the staging site and switching back to the original theme. It's a not too pretty workaround, but it worked for me.