I'm on a Media Temple DV with drush-5.0-dev installed and I am getting this error when I try to install Drupal 7.0. I installed drush to /var/www/vhosts/neetzstudios.com/drush/drush but i'm not sure that is the proper place , I tried /drush/drush as well with the same results.

# drush dl drupal-7.0
Source directory /tmp/drush_tmp_1300349867/drupal is not readable or does not exist.
Project drupal (7.0) could not be downloaded to /var/www/vhosts/neetzstudios.com/httpdocs/drupal.

My drush status

PHP config : /etc/php.ini
Drush Version : 5.0-dev

I downloaded drush-7.x.4.4 and drush dl drupal-7.0 with success so I know this has to be a bug with the new dev version.

Comments

kotnik’s picture

anon100101001’s picture

Status: Active » Fixed
j. ayen green’s picture

I just updated:

Drush successfully updated to version All-versions-5.x-dev

and get this:

# drush dl drupal-7.x
Source directory /tmp/drush_tmp_1301191398/drupal is not readable or [error]
does not exist.
Project drupal (7.x-dev) could not be downloaded to [error]
/var/www/mydomain/drupal.

j. ayen green’s picture

Status: Fixed » Active
kotnik’s picture

Status: Active » Closed (duplicate)

Ayen,

All-versions-5.x-dev version is still affected, this has been fixed in HEAD. You can grab it here: http://ftp.drupal.org/files/projects/drush-All-Versions-HEAD.tar.gz

droomagentur’s picture

Status: Closed (duplicate) » Active

sorry to reopen but the problem is not solved (at least not for me) with the HEAD archive kotnik posted, I still get

Source directory /tmp/drush_tmp_1301418210/drupal is not readable or does not exist.

OS is Ubuntu (latest stable all updates, including PHP, server etc.)

doublejosh’s picture

Yep. Same problem here. Drush 4.2

"drush self-update" to 4.4 fixes this problem.

greg.1.anderson’s picture

Please confirm against 5.x HEAD and close if fixed.

loopduplicate’s picture

#7 worked for me too.

Ubuntu 11.04.

greg.1.anderson’s picture

Status: Active » Fixed

Actually, #6 is a duplicate of #704848: Command getting run twice, which is fixed in 5.x-dev. Marking this 'fixed', as the other issue seems to be cleared up too.

Status: Fixed » Closed (fixed)

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

toulon’s picture

Status: Fixed » Needs review

Not to reopen an closed issue, it is still an issue with the Drush version 5.0-dev. I removed 5.0 and reinstalled Drush version 4.4 and the error went away.

$ drush status
PHP configuration : /etc/php.ini
Drush version : 5.0-dev
Drush configuration :
Drush alias files :
$ cd /var/www/html/joe2
joe2 $ drush dl drupal
Source directory /tmp/drush_tmp_1311085075/drupal is not readable or does not exist.[error]
Project drupal (7.4) could not be downloaded to /var/www/html/joe2/drupal. [error]
$ drush self-update
A newer version of drush, All-versions-4.x-dev (2011-Jul-18), is available. Would you like to back up your current drush, version 5.0-dev, to /root/drush-backups/drush/20110719142137 and replace it with the newer release? (y/n): y
drush backed up to /root/drush-backups/drush/20110719142137/drush [ok]
Project drush (All-versions-5.x-dev) downloaded to /usr/local/bin/drush. [success]
Drush successfully updated to version All-versions-5.x-dev. [success]
~ $ drush dl drupal
Source directory /tmp/drush_tmp_1311085313/drupal is not readable or does not exist.[error]
Project drupal (7.4) could not be downloaded to /root/drupal.
~ $ cd /usr/src/
src $ mkdir drush
src $ cd drush/
drush $ wget http://ftp.drupal.org/files/projects/drush-7.x-4.4.tar.gz;
drush $ mv /usr/local/bin/drush /usr/local/bin/drush.071911
drush $ tar -xzf drush-7.x-4.4.tar.gz
drush $ mv drush /usr/local/bin/
drush $ drush status
PHP configuration : /etc/php.ini
Drush version : 4.4
Drush configuration :
Drush alias files :

drush $ cd /var/www/html/joe2
joe2 $ drush dl drupal
Project drupal (7.4) downloaded to /var/www/html/joe2/drupal-7.4. [success]
Project drupal contains: [success]
- 3 profiles: minimal, testing, standard
- 4 themes: bartik, seven, garland, stark
- 47 modules: statistics, filter, contextual, poll, rdf, overlay, php, profile,
dblog, user, comment, color, update, tracker, book, image, openid, help, aggregator,
path, toolbar, list, options, number, field_sql_storage, text, field, node,
translation, trigger, blog, contact, block, forum, file, simpletest, locale, syslog,
shortcut, field_ui, search, menu, taxonomy, dashboard, system,
drupal_system_listing_compatible_test, drupal_system_listing_incompatible_test

joe2 $ ls
drupal-7.4

greg.1.anderson’s picture

Status: Closed (fixed) » Fixed

Follow the git instructions to get drush-5.x-dev, or drush dl drush --select. This is definitely fixed in master.

xjm’s picture

Status: Needs review » Fixed

The 5.x archive has not been updated since February; perhaps this is part of the problem?

greg.1.anderson’s picture

Yes, you are right. Following the git instructions will get you master, but drush dl drush --select will only get you published releases. You could also do drush dl drush --select --package-handler=git_drupalorg, followed by git pull from your drush directory.

waynedpj’s picture

for those who are experiencing this issue, but like me had no idea what the "git instructions" are, take a look here:

http://drupal.org/node/97249/git-instructions/master

and follow the instructions under One-Time Only to get the latest drush version via git.

thanks to the original posters for the info.

finally: any chance the HEAD package will get updated any time soon?

peace

pimok3000’s picture

Reverting back to drush 4.5 solves the problem that is still there in 5.0-dev version.

Status: Fixed » Closed (fixed)

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

RobertoGA’s picture

drush self-update fix my problem,

Drush was upgrated to v.7.x-4.5

Thanks doublejosh

selfuntitled’s picture

I was having similar problems, with a slightly different error. The solution I found: cpanel had created a symlink from www to public_html and somehow that link got copied inside my public_html folder and thus broken. For whatever reason, Drush was trying to follow the link to get to downloaded files, and, sure enough, they were not found. Deleting the symlink solved the problem.

paskainos’s picture

I was experiencing the same issue. I ran drush self-update (from 7.x-4.6 to 7.x-5.4) and the problem appears to be remedied.

marcoscano’s picture

Version: » 7.x-5.x-dev
Status: Closed (fixed) » Active

Sorry if not right place or different issue, but I just turned into the same problem with drush version 6.1.0.

When I try to use "drush make makefile.make sitename", I get:

Aborting.   [cancel]
Source directory /tmp/make_tmp_1381734131_525b96f3727e9/__build__ is not readable or does not exist.   [error]
Cannot move build into place

For reference, in another environment with drush 5.9 this error doesn't occur.

In the environment with the problem (ubuntu), drush was installed using:
apt-get install php-pear
pear channel-discover pear.drush.org
pear install drush/drush

greg.1.anderson’s picture

Please report on github: https://github.com/drush-ops/drush

There are open Make issues there; please search for duplicates, and back-link any you find to this issue. Close this issue as a duplicate if you find a dup on GitHub, or open a new one.

mariacha1’s picture

Status: Active » Closed (duplicate)

This issue is reported on Github here:
https://github.com/drush-ops/drush/issues/162

Closing this issue as a duplicate.

yaach’s picture

I was getting this same error:

Source directory /tmp/make_tmp_1424359769_54e601591e21c/__build__ is [error]
not readable or does not exist.

In my case, I was creating a make file and I found out that I was downloading a sub module from a module that was already downloaded few lines above in the make file. That is, when setting a project on make file, drush make downloads all its sub modules, so you dont have to explicitly add them on the make file.

Thought to share this in case it relates to some of the problems above.

dasginganinja’s picture

I really hate to necro an old thread but wanted to put a tip in that worked for myself.

I have a bunch of repositories hosted on BitBucket that house custom modules/themes. What I needed to do for these custom elements was declare what type they were, similar to: projects[xyz_base_install][type] = "module"

Once I did that everything worked as expected.