Hi,

This is the first time I've run into this issue, and I suspect that it might be related to the particular version of this module I'm trying to download being quite new, but I am having an issue where I tell Drush to download a specific version of a module and it's downloading another version.

Command: drush dl views_bulk_operations-6.x-1.10-beta3
Result: Project views_bulk_operations (6.x-1.9) downloaded to /Users/Shared/Web/pwcore/sites/all/modules/views_bulk_operations. [success]

I did also run drush pm-releases views_bulk_operations and it definitely showed the version I wanted being available.

Slightly annoying.

Cheers,
Deciphered.

Comments

greg.1.anderson’s picture

greg.1.anderson commented

Yes, that is odd. beta3 exists, and is a supported security release. Downloading it gives the wrong version, as described above. beta1 and beta2 also exist, and can be downloaded successfully.

Did not look into the code or cause.

jonhattan’s picture

jonhattan
Primary language Spanish
Location Plasencia
commented
Status: Active » Fixed

This scenario has changed since vbo 1.10 is out.

pm-releases uses the drupal api to connect to updates.d.o but `dl` grab its xml directly. Haven't seen the differences.

Omitting this asimetry, if you ask for a non-existent release drush will 'silently' switch to latest stable although. It is a log notice, but this level is only shown if --debug. Comitting this:

-            drush_log(dt("Could not locate specified project version, downloading latest stable version"), 'notice');
+            drush_log(dt("Could not locate specified project version, downloading latest stable version"), 'warning');

Status: Fixed » Closed (fixed)

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