Closed (fixed)
Project:
DrupalPro
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
27 Jun 2012 at 05:24 UTC
Updated:
20 Nov 2012 at 04:40 UTC
When running: drush qc --domain=foo.dev (without using switch --makefile=*.make)
This error occurs:
Command failed: Makefile /home/drupalpro/.drush/default.make not found.
A fix has been committed to 7.x-3.x branch. This update includes later problems s discovered through comment #16 on this issue.
Press (F4) Key to open a terminal, then copy and paste these lines:
cd ~/drupalpro/setup_scripts git add . # add any changes to index so we can stash everything git stash save "stash my changes (probably just logs) before pulling in update" git pull --rebase # update drupalpro ./update.sh # run update script
Comments
Comment #2
kkecha commentedAfter applying the above mentioned procedure, "qc" is not recognized as a drush command any more.
Comment #3
heyyo commentedSame error
Comment #4
pwieck commentedDrush "qc" command still is not recognized after doing 7.x-3.x branch update. Neither is drush quickstart-create.
Comment #5
kkecha commentedIn order to correct the above, change the symbolic link folder named "quickstart" under
/home/drupalpro/.drush (be careful! the hidden .drush folder)
to point to
/home/drupalpro/drupalpro/drush_addons
You may also notice that mail is not dispatched under /home/drupalpro/websites/logs/mail, as expected. In order to correct this
1) copy sendmail.php from /home/drupalpro/drupalpro/resources to /home/drupalpro/websites/config, as this is the place of the file according to php.ini
2) change the permissions of the folder /home/drupalpro/websites/logs/mail as to be writable by everyone
Comment #6
kihap commentedI made changes as suggested at the top. Still problems. Then made changes in #5. Got me almost there. The last changes I made were to redirect the symbolic links to make files in /home/drupalpro/.drush to the make files in /home/drupalpro/drupalpro/drush_addons/make_templates. That seems to be the ticket for me.
Comment #7
rootworkYep, that worked for me too, thanks kkecha and kihap!
Lots of typing, though, would be great to see this committed to dev so it could be pulled in through the update.
Comment #8
ckurmann commentedThanks to the above for your help.
I'm a newbie here and took a few attempts to get it done.
So here for the other simples ;-)
Press F4 to get into the console.
cd /home/drupalpro/drupalpro(do the git stuff here)
cd /home/drupalpro/.drushls -la(this shows all the links in red as these are now wrong and must be fixed)rm d6git.make d6.make d7git.make d7.make d8git.make default.make quickstart(this deletes all the now false symbolic links)(recreate all the links to the new drush_addons directory)
cp /home/drupalpro/drupalpro/resources/sendmail.php /home/drupalpro/websites/config/chmod 777 /home/drupalpro/websites/logs/mail/(changes the permissions on the folder to allow all to all.)Comment #9
chrisschaub commentedCan a beta3 get posted that has these fixes in place?
Comment #10
JFreed commentedThanks ckurmann. Totally sorted me out.
Comment #11
ahimsauziTotally sort me out too! Clearing drush cache (drush cache-clear drush) was needed in my case.
Any you call yourself a newbie :)
Thanks for the writeup!
~Uzi
Comment #12
rootworkCan this get posted as an updated dev or something? Or is there another beta forthcoming soon?
Comment #13
mike stewart commentedthanks #8 for the detailed writeup. my plan is to have a release early next week that fixes all this. (As I recall I think the new image simply works as intended and its a new directory structure in the new image that is the culprit of these problems).
sorry to anyone that needs to use the old image in the meantime :(
Comment #14
mike stewart commentedchanging status so I remember to test in new image
Comment #15
vlad.dancerckurmann, Thanks a lot!
Comment #16
mike stewart commentedI just noticed the last line of #8 -- the permissions are incorrect, and 777 is too loose. generally speaking 750 for a folder is suffient. and 640 for files. it obviously depends, but both of those are safer than 777.
at any rate, I finally looked into #5 -- and sendmail setup is just borked. I just created an update and committed it, it should fix existing installations. Please make a snapshot before running, as I don't have a setup I can easily test. (my working image is actually pre-beta)
Run the update in a terminal
Comment #17
seanhe commentedFirst of all I would like to thank you Mike for this excellent Ubuntu config. You have helped me get away from Windows for drupal dev. I am still having some issues with sendmail. I completed all the fixes in this post, including your latest update script and it still does not seem to be working. When I try to test sendmail in the Terminal, I get "Please install an MTA on this system if you want to use sendmail!". Do I need to do anything else, possibly in my php.ini file? Currently, the loaded php.ini has the sendmail path at "sendmail_path = /home/drupalpro/drupalpro/resources/sendmail.php" which exists although is at odds with the fixes in this post. The update script successfully changed the file permissions in the log folder to read-write, however whenever a new email is attempted, that email is set again to read-only. Not sure if that is the issue.
Thanks in advance.
Comment #18
mike stewart commentedsendmail is not part of DrupalPro (or quickstart for that matter). if you truly need sendmail, search the web for a tutorial on setting up "sendmail on ubuntu 12.04"
What my update does is fix issues with drush / path changes / and also fix the php setup that redirects any php emails to a text file in
$HOME/websites/logs/mailfolder. for details see~/drupalpro/resources/sendmail.php(its a pretty basic, yet nifty little setup)Comment #19
rootworkJust curious, is there still another release planned as you mentioned in #13? I know from things you've said that you're eager to move on to other ways of doing this kind of thing, Mike :) So just wondering if there will be another version or if b2 is it for the foreseeable future.
Thanks as always for your hard work on this.
Comment #20
mike stewart commentedI'm definitely working towards a "final" release ... although beta is quite stable -- and has updates.
I've tested and now closing this since having an update script on the DrupalPro project homepage covers this fix (and other similar or future issues).
Comment #21.0
(not verified) commentedupdate directions