Firstly, thanks for an excellent module -- just what I need.

I would like to update some of my modules to a different version than the recommended one (eg use dev). It looks like I can do this in the same way as for an install (adding -6.x-1.0-alpha1 or whatever) -- note that this is not in the help. However, this will not work for dev. eg say my current version is 6.x-1.x-dev and the recommended one is 6.x-1.8 but there is an update available for 6.x-1.x-dev. I cannot run drush pm update project-6.x-1.x-dev as it only checks the release number and so thinks they are the same. Is it possible to add a more detailed check?

Thanks.

Comments

luckysmack’s picture

luckysmack commented

I am having the same issue, though for the could we could go to the modules directory and delete the existing module folder and just tell it to get the dev version again? I think for getting -dev releases maybe there could be a check against the release date?

ar-jan’s picture

ar-jan commented

I would find this useful as well. For now I just updated from -dev to the recommended version, then to latest -dev again, which is still quite convenient compared to not having Drush ;)

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Fixed

See Examples in Help.

Status: Fixed » Closed (fixed)

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

fletchgqc’s picture

fletchgqc commented
Category: feature » support
Status: Closed (fixed) » Active

Do you mean "drush help up"? I got the following (no examples):

Display available update information and allow updating of all installed
projects to the specified version (or latest by default), followed by applying
any database updates required (as with running update.php). Note: The user is
asked to confirm before the actual update. Use the --yes option to answer yes
automatically.

Arguments:
projects Optional. A space delimited list of
installed projects (modules or
themes) to update.

Options:
--backup-dir Specify a directory to backup
packages into, defaults to a backup
directory within your Drupal root.

Aliases: up

greg.1.anderson’s picture

greg.1.anderson commented
Status: Active » Fixed

You'll find examples in drush help updatecode and drush help dl. Use update or updatecode to go to the latest recommended version. Use dl to go to a specific version.

boran’s picture

boran commented

Just to note an example to upgrade backup_migrate to v2.2:
drush pm-updatecode backup_migrate-6.x-2.2

Status: Fixed » Closed (fixed)

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