Closed (fixed)
Project:
OpenPublish
Version:
7.x-1.0-alpha5
Component:
Miscellaneous
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
22 Feb 2012 at 16:53 UTC
Updated:
10 Mar 2012 at 05:10 UTC
The openpublish installation profile links to core http://ftp.drupal.org/files/projects/openpublish-7.x-1.0-alpha5-core.tar.gz instead of http://ftp.drupal.org/files/projects/openpublish-7.x-1.0-alpha5.tar.gz. This means drush_make downloads the wrong file and cannot find the openpublish.make file resulting in a broken installation.
Comments
Comment #1
jec006 commentedComment #2
jec006 commentedI think I understand what you're saying, but I'm not 100% sure.
openpublish.make includes core which causes sites built with a command like
drush make openpublish.make ../openpublish/htmlto not have an openpublish profile.This is the expected behavior I think - the next step to complete the build would be to symlink the directory that you built out of (the profile itself) into the profiles directory of your new site.
Alternatively you can use the build-openpublish.make file which will redownload the profile into the profiles directory for you.
Hopefully that was the question/problem
Comment #3
jec006 commentedAh ok, I think after some further investigation I think I have a better idea of what you're talking about.
The new packaging system on Drupal allows us to distribute fully built distributions - so we have downloads that include core.
Its possible with drush dl or make to download this version instead of just the regular profile, generally, specifying no version or 1.0-alpha5 outside of a drupal install (using drush 5) will download the version with core. Our make file specifies a git checkout for openpublish however, so it shouldn't suffer from this issue.
If you tell me how exactly you are building your site I can hopefully help you work around / make use of these new features and changes.
Based on my research though - there is no problem with the Openpublish build, simply new features.
Comment #4
dude4linux commentedI have a stub make file, openpublish-site.make, that up until a few days ago would download the latest openpublish profile and build the site accordingly.
That no longer works, unless I specify the version number, and if I do that, I must edit the file everytime a new version of openpublish is released. In my opinion, that is not a desirable feature. Distributions and profiles should NOT be mixed IMHO.
Comment #5
dude4linux commentedI just checked and even specifying the version in the make file does not work.
This effectively prevents drush make from ever accessing the profile.
Can you tell me who is responsible for the changes in drupal.org packaging so I can discuss this with them? I'm afraid this will soon by affecting all profiles.
Comment #6
dude4linux commentedOkay, I found your version of the stub-make file, build-openpublish.make
This seemed to work okay. I see that you are downloading the profile via 'git' rather than 'get' which apparently avoids the problem I was seeing. I was trying to avoid downloading an entire profile in order to obtain the stub-make file and so I use a script to generate a stub-make file on-the-fly.
Comment #7
jec006 commentedHey,
I definitely agree this is not the preferable behavior - however, this is something controlled by drush and not any particular distro. Here is the relevant issue for drush #1452672: Make downloads the wrong tarball for profiles.
The workaround for now is exactly what you have (that is - a git checkout). Sorry for the annoyance.
Comment #8
dude4linux commentedOkay, good to know it's a known problem. Hope it gets fixed before the final release of 5.0. I was just caught off guard when it worked one day and failed the next.