I tried to follow the instruction on http://drupal.org/node/1717546 but then realised that this method is only supported by drush 5 which is not available on BOA. Is there a way to get latest panopoly from git as it contains latest Drupal version (particularly 7.20 and 7.21) and panopoly patches. One way is to build a platform on local workstation with drush 5 installed and then upload it to /data/disk/o1/static but if it can be done on BOA server it may be easier.


aanjaneyam’s picture

Even drush dl panopoly-7.x-1.x-dev does not work.(it works in drush 5). Does panopoly distribution included in BOA contains latest patches (as I saw it definitely has Drupal 7.21).

omega8cc’s picture

Category:support» feature
Status:Active» Fixed

BOA-2.0.6-dev includes Panopoly 1.0-rc3, just the core is replaced with 7.21.1, but it is not built with makefile. Note that BOA-2.0.6-dev comes with Drush 5 and Drush 6 available on command line.

aanjaneyam’s picture

When I use drush5 (on virtualbox vm) to build panopoly profile (according to link above) I get error:

o1.ftp:[panopoly-7.21.1-P001]$ drush5 make --prepare-install --no-gitinfofile --contrib-destination=profiles/panopoly profiles/panopoly/build-panopoly.make
opendir(/opt/tools/drush/5/drush/commands): failed to open dir: Permission denied filesystem.inc:629                                                         [warning]
The drush command 'make profiles/panopoly/build-panopoly.make' could not be found.  Run `drush cache-clear drush` to clear the commandfile cache if you have [error]
installed new extensions.

o1.ftp:[panopoly-7.21.1-P001]$ drush5 cache-clear drush
The drush command 'cache-clear drush' could not be found.  Run `drush cache-clear drush` to clear the commandfile cache if you have installed new extensions.[error]
A Drupal installation directory could not be found   

Am I missing something.

omega8cc’s picture

aanjaneyam’s picture

Thanks. It started working after the following commit (I suppose):


Status:Fixed» Closed (fixed)

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