Background

I encountered this problem while testing new releases of the OpenChurch profile. After reporting some issues to the OpenChurch queue and being told a fix was in the new release, I found I was unable to get drush make to download the latest release. It kept returning to the old, flawed release. Eventually by running drush make with the --debug option, I was able to see that drush was not downloading a new version of the release-history, but instead using the cached version which was out of date. I tried using drush cache-clear drush and drush cache-clear all with no effect. Finally I was able to download the new version by removing the entire download cache and forcing drush to build a new cache.

I think the problem may be that the release-history is improperly stored in the persistent cache, but I also wonder why the cache-clear command is not clearing the download cache. If it should be, then this is a bug, otherwise we should consider adding a new feature, drush clear-cache download.

Comments

moshe weitzman’s picture

moshe weitzman commented

Hmmm. Maybe. 'All' is basically everyone's default and it is quite unfrtunate to blow away these caches when you just want your Drupal blocks to clear or whatever ... Feedback?

dude4linux’s picture

dude4linux commented
Status: Active » Closed (works as designed)

Apparently I was premature in reporting this as a bug. After testing the problem yesterday and convincing myself it was a drush cache issue, I now find that after removing the old cache and letting drush build a new cache, I'm now seeing new updates being retrieved as they should. Looking through my old cache which I fortunately saved, I see a malformed entry which may have prevented newer versions of openchurch from being retrieved. Now that it is gone, it appears to be working correctly. I was mislead into thinking that cache-clear wasn't working by seeing the files in the download directory after the cache-clear. Obviously it doesn't work that way.

scor’s picture

scor commented
Version: » 8.x-6.x-dev

ran into a similar situation, and used the --no-cache option to avoid drush make from using drush download cache altogether.

jjones150’s picture

jjones150 commented
Issue summary: View changes

whatever the fuck comment #4 even means

dude4linux’s picture

dude4linux commented

Actually comment #4 is helpful if you've experienced the problem I described. Unfortunately I can't recreate the problem to test if the --no-cache option would have helped, but I believe it would have.

Eugene Fidelin’s picture

Eugene Fidelin commented

Comment #4 works even for Drush 5