Closed (fixed)
Project:
Drush
Component:
Make
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Nov 2010 at 14:14 UTC
Updated:
14 Dec 2012 at 19:20 UTC
Using build files to create Drupal installations with some contrib projects added. For some reason, I can use:
drush dl acquia_slate
without an issue. When placing the theme into a .make/.build file however (drush make.module) the build fails on acquia_slate
Project information for acquia_slate retrieved. [ok]
Unable to determine project type for acquia_slate. [error]
I've tried cheating by providing the project type
projects[acquia_slate][type] = "theme"
projects[acquia_slate][subdir] = ""
No luck :/
Comments
Comment #1
jeremycaldwell commentedNot sure about this one.. maybe try also including "fusion" since the Fusion theme is required to run the Acquia Slate theme. I doubt it would affect the make file though since it wouldn't know about the need for a base theme in this case but worth a try. Perhaps someone else has some idea?
Comment #2
leenx commentedFor completeness, I have included a complete make file for build.
test.make ... Run with drush make test.make test --verbose
I have also tried older and dev version using ...
and
But get the following error ...
Work around that seem to work fine yesterday ...
The standard make file worked fine around 2010-11-12. Plus fusion, acquia_marina and acquia_prosper themes all work fine. Hope this is not too much info.
Comment #3
uberellis commentedThis workaround works for me, thanks leenx :) It's certainly good enough as a temporary measure
Comment #4
stephthegeek commentedDoes anyone know if this is still an issue for Acquia Slate?
Comment #5
leenx commentedDid a build today and it works correctly, but we have updated to drush 4.4 and make 2.2, can't tell you if the theme was updated or if the update drush/make fixed the problem.
Hope this helps.
Mailed
LeeT
Comment #7
danepowell commentedThe problem is that the Acquia Slate project is not officially classified as a "Theme". You (maintainer) need to go to the project page, click "edit", and set the project type as "Themes". I have no idea how that could have become unset- it should have failed validation- but you really need to fix it ASAP.
A temporary workaround for makefiles is to add the following line:
projects[acquia_slate][type] = "theme"Comment #8
stephthegeek commentedWow that is so weird, no idea how that happened. Fixed!
Comment #9
danepowell commentedThanks!
Comment #10
TwoMice commentedActually, at this moment it's again not set, I think.
downloads it as a module.
Also, d.o site search doesn't list it under "themes" (doesn't actually list it anywhere except "All").
Comment #11
stephthegeek commentedRe-fixed, and reported an issue :\ #1155670: Project type keeps getting UNset
Comment #13
danepowell commentedThis bug seems to be back yet again...
Comment #14
danepowell commentedComment #16
danepowell commentedIt's baaaaack. :/
Comment #17
mac_weber commentedThis problem is on Drush.
I'm having the same problem with a custom module based on a local folder.
I changed from
projecttolibraryas suggested on #3 then I got it working.Comment #18
jonhattanDrush make guess a project type based on the info in the update service. If a update service is not used to download a project you need to specify its type manually.