Posted by perusio on January 4, 2013 at 6:03pm
4 followers
Jump to:
| Project: | Drush |
| Version: | 7.x-5.x-dev |
| Component: | PM (dl, en, up ...) |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
when trying to upgrade from 1.12 to 1.13 it reads:
The commerce_kickstart directory could not be found within the modules directory at /home/appa/sites/ck1/profiles/commerce_kickstart, perhaps the project is enabled but has been deleted from disk.
Comments
#1
I don't think drush up supports distributions (+ Kickstart v1 recommends moving modules from profiles/ to sites/all, which probably makes it even worse).
Let's ask them to confirm.
#2
#3
This is a known limitation of Drush, although I can't find a duplicate issue. #1325818: Generate an upgrade makefile from an existing makefile? is an alternative. #1431136: Updating OpenPublish 3-alpha3 site with drush 4.5 destroy data in profiles/openpublish directory. is related.
I decided to label this a 'bug' instead of a 'feature request', since Drush should at least reasonably detect when profiles are in use, and inform the user that pm-update won't work.
#4
Updated the FAQ to point here.
#5
Well in an old OA (D6) I just upgraded to the most recent one without any issue. It seems to be a regression then, at first sight from D6 to D7.
#6
I guess what we need, then, is for someone to take the time to test pm-update with a few different distributions on D6 and D7, and isolate what is working and what is not.
#7
There is a discussion on this in the Drupal Commins issue queue where I also posted some information on my experience per ezra-g's request:
drush update error commons directory could not be found
Gerben