The scenario is as follows: I have an old dev version of date installed. There is now a point release which I wish to switch to, but there is also a newer dev release. So, my thinking was that I could drush upc date-6.x-2.8 to get the point release, as I have specified an exact version.

This was not the case however; the version that was fetched was the newer dev release. Firstly, I don't see this as the desired outcome, and secondly, it was unclear which version was going to be installed, the message "specified version available" is ambiguous. I see that the proposed version is -dev but that isn't the one I "specified", so I feel that this is misleading.

habanero:~/public_html$ drush upc date-6.x-2.8
Update information last refreshed: Mon, 30/01/2012 - 8:30pm

Update status information on all installed and enabled Drupal projects:
 Name                                             Installed version  Proposed version  Status
...
 Date                                             6.x-2.x-dev        6.x-2.x-dev       Specified version available
..

Code updates will be made to the following projects: Date [date-6.x-2.x-dev]

Do you really want to continue with the update process? (y/n): y
Project date was updated successfully. Installed version is now 6.x-2.x-dev.

Status:

 Drupal version         :  6.22
 Site URI               :  http://default
 Database driver        :  mysqli
 Database hostname      :  localhost
 Database username      :    ******
 Database name          :    ******
 Database               :  Connected
 Drupal bootstrap       :  Successful
 Drupal user            :  Anonymous
 Default theme          :  ******
 Administration theme   :    ******
 PHP configuration      :  /etc/php5/cli/php.ini
 Drush version          :  4.5
 Drush configuration    :
 Drush alias files      :
 Drupal root            :  /home/****/public_html
 Site path              :  sites/default
 File directory path    :  sites/default/files

Comments

greg.1.anderson’s picture

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

There are a bunch of related issues:

#502660: Upgrade control over version selection (dev to/from stable and allow minor upgrades only)
#999762: drush inconsistent about dev release selection when user specifies a partial version (e.g. views-5.x, drupal-5.x).
#1323046: How can I upgrade from Drupal Core dev to stable?

Would be good to clear these up.

niklp’s picture

niklp commented

You're right, there are, and they're all old and incomplete :/

I don't get why if I'm asking for a *specific* version I'm not getting it, or if Drush is confused, why it doesn't offer me a choice...?

gapple’s picture

gapple
he/they
Primary language English
commented

I ran into this same issue, but it seems an update to the latest drush 4.x correctly updates dev releases to the specified version

$ drush pm-update date-6.x-2.8
Refreshing update status information ...
Done.
Update information last refreshed: Tue, 2012-02-28 21:07

Update status information on all installed and enabled Drupal projects:
 Name                                   Installed version  Proposed version  Status
....
 Date                                   6.x-2.8+16-dev     6.x-2.8           Specified version available
....

Code updates will be made to the following projects: Date [date-6.x-2.8]

Note: A backup of your project will be stored to backups directory if it is not managed by a supported version control system.
Note: If you have made any modifications to any file that belongs to one of these projects, you will have to migrate those modifications after updating.
Do you really want to continue with the update process? (y/n):
moshe weitzman’s picture

moshe weitzman commented
Status: Active » Fixed

Sounds like we have fixed this. If not, please reopen.

Status: Fixed » Closed (fixed)

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