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

bojanz’s picture

bojanz commented
Project: Commerce Kickstart » Drush
Version: 7.x-1.12 » All-versions-4.x-dev
Component: Code » PM (dl, en, up ...)
Category: bug » support

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.

bojanz’s picture

bojanz commented
Title: drush up doesn't work » drush up for updating distributions
greg.1.anderson’s picture

greg.1.anderson commented
Version: All-versions-4.x-dev »
Category: support » bug

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.

greg.1.anderson’s picture

greg.1.anderson commented

Updated the FAQ to point here.

perusio’s picture

perusio commented

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.

greg.1.anderson’s picture

greg.1.anderson commented
Status: Active » Postponed (maintainer needs more info)

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.

Gerben Zaagsma’s picture

Gerben Zaagsma commented
Version: » 7.x-5.x-dev

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

greg.1.anderson’s picture

greg.1.anderson commented
Version: 7.x-5.x-dev » 8.x-6.x-dev
Status: Postponed (maintainer needs more info) » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If desired, you may copy this bug to our Github project and then post a link here to the new issue. Please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.

honza pobořil’s picture

honza pobořil commented
Issue summary: View changes

Issue on Github: https://github.com/drush-ops/drush/issues/99